01-28-2013 04:23 AM
I'm getting the error (see subject) fairly consistenly on the 9810 (device), and very intermittently on the 9900 (device).
Note NOT on any simulator (naturually).
I have follows some other threads here, with similiar problems - their "solutions" were very much in line with mine, and also not exactly conclusive (for everybody it sorta looked like the problem went away, but nobody was 100% certain of the why's and wherefores, thus could not state with certainty that it was solved.)
Can any RIM engineer maybe just list the (exhaustive if possible) potential causes of this very annoying situation?
The app does utilize threads (as we must since there is network IO involved), and there are some one shot Timer objects in use.
The mentioned threads (3 threads total) are used in a classic producer-consumer situation.
Could there maybe be some deadlock situation arising from waiting on the producer queue object, causing the OS to detect the app as still active?
Looking forward to some illumination....
01-28-2013 04:59 AM
01-28-2013 05:59 AM - edited 01-28-2013 06:01 AM
The only system-level listener I'm using is a FileSystemJournalListener.
This is in order to use the native camera app in order to integrate photo's into my app.
I verified that I make pretty **bleep** sure the listener is removed after using the camera app (and added again just before the camera app is activated).
So by working a bit roughly with the app (activating camera app, exiting app very quickly after taking a photo), I got the BB to throw "net_rim_bb_camerarevious instace still active bla bla you know the rest". FYI, I'm also pretty sure the listener was done procecessing the image, since I got the scaled thumbnail in the image ribbon.
Is it possible that "UiApplication.getUiApplication().removeFileSystem