kwhinnery/NavigationController — Issue #1: home function sporadically gives EXC_BAD_ACCESS in 1.8.201111xx
Author: pegli
Created: 2011-11-06 22:48:03+00:00
State: open

This is probably an issue with the 1.8.x SDK, but I thought I'd bring it up here as well to see if you had any insights. I've found that the home() function in NavigationController will eventually crash with a bad access exception under recent nightly builds of 1.8.

To reproduce:

1. Profile the sample app in Instruments. Select the "Zombies" instrument to catch deallocation problems.
2. Add three or four windows, then press the Home button.
3. Repeat as necessary until the crash happens. It usually takes me two or three iterations to see the crash.

Result: EXC_BAD_ACCESS exception with a message being sent to a deallocated object. The problem occurs in -[TiModule createProxy:forName:context:] (TiModule.m:155):

return [[[resultClass alloc] _initWithPageContext:context args:args] autorelease];

I've been poking around TiModule.m a bit, and the one thing that I've discovered so far is that the resultClass variable in that method is coming from the classNameLookup dictionary, not from the code in the if() block. I've tried forcing creation of resultClass on each call, but I still see the same error.

If I come up with any other info, I'll add it to this issue.