[hari ananth]

I have been developing a webapp primarily on the BlackBerry 8900 4.6.1.94 (Rogers) simulator, but when I tried opening the simulator today, I get a series of errors.

First, during startup, I get a JVM Error 104: Uncaught: ClassCastException. I then turn the debugger off (somehow, it gets turned on on startup now) to avoid an unending series of RuntimeExceptions.

After turning the debugger off, the desktop loads, icons and all, but there is an alert: Uncaught exception: java.lang.Error. The little black clock comes up every second or so, like it's doing something, but clicking the OK button does nothing to the alert (or perhaps it reloads extremely quickly).

After about 20 seconds and some alert-OKing, I get another alert: Uncaught exception: ApplicationRegistry.getOrWaitFor(long hex) owner died Thread[Thread-long number] for a couple seconds. Clicking 'OK' here, within a couple seconds, brings up the white screen: App Error 523, System process died. From here, I am forced to reset the device.

I have uninstalled/reinstalled the simulator twice now, to now avail. How in the hell do I get around this..

Also, I have four other simulators running 4.6.1/4.7 and they all startup fine. I'll be testing my webapp on those until I find a solution for this..

Thanks in advance.

[Dougsg38p]

Remove the *.dmp files in your simulator directory and retry.

[hari ananth]

That worked--thanks so much. Out of curiousity, do you have any idea what was in these files that should not have been and/or how they became corrupted?

[Dougsg38p]

The files contain the "simulated" flash storage. If the flash gets corrupted, the OS startup will fail (as you experienced).

This probably happens when you stop the simulator while the "simulated" OS is writing to the "simulated" flash, or when the "simualted" OS is performing garbage collection on the flash to recover unreferenced objects.