Skip to main content

Fatal Crash on All PhoneME MIDP Releases

7 replies [Last post]
mara_fenske
Offline
Joined: 2008-08-01
Points: 0

Hi,

I have found a consistently reproducible fatal crash on all PhoneME MIDP releases on all tested OS's. This includes PhoneME Feature and PhoneME Advanced Dual Stack. This has been reproduced on the Windows Mobile builds, Windows CE builds, the Windows XP compile of PhoneME Feature MR2 and the Java SDK 3.0 emulators.

Basically, if you have a standard J2ME MIDP command menu with more than two options, as usual the rest of the options appear in the "Menu" option available via the right soft-key. If you open/expand the menu, the options will be displayed as a list above the bottom bar. If you use a touchscreen to select an option, but instead of touching the option well, accidentally touch right around the line in between the bottom blue bar (the soft key bar) and the menu list, it will hard crash the application.

In the Windows XP PhoneME MR2 build and the Java SDK 3.0 emulators, the application will crash and exit back to the midlet list. In the cases of Windows Mobile and CE, the application screen will freeze forever with the menu list shown. The Windows Mobile/CE crash is even worse because most users do not know how to kill the application manually and re-open. Plus, all unsaved data inside the J2ME application will be lost.

Has anyone seen this before? It is doing a number on my application and causing serious user dissatisfaction. The link below is to an image with the pink highlight showing where on the screen the touchscreen press can cause the crash when the menu is open.

http://img142.imageshack.us/img142/4107/phonemecrash.gif

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
mara_fenske
Offline
Joined: 2008-08-01
Points: 0

FYI - this is the error stack from causing the crash in the 3.0 SDK:

java.lang.ArrayIndexOutOfBoundsException: 0
- com.sun.midp.chameleon.layers.MenuLayer.showSubMenu(), bci=7
- com.sun.midp.chameleon.layers.MenuLayer.pointerInput(), bci=132
- com.sun.midp.chameleon.CWindow.pointerInput(), bci=76
- javax.microedition.lcdui.Display$DisplayEventConsumerImpl.handlePointerEvent(), bci=19
- com.sun.midp.lcdui.DisplayEventListener.process(), bci=296
- com.sun.midp.events.EventQueue.run(), bci=179
- java.lang.Thread.run(), bci=11
27425 - CORE - CRITICAL - 3 - handleFatalError: uncaught exception in isolate 3 event processing thread

davyp
Offline
Joined: 2007-01-03
Points: 0

I can reproduce the problem and get the same error stack trace too. I am not sure what is going
on, but I guess the array menuCmds[] in showSubMenu() is not properly initialized.

Davy

mara_fenske
Offline
Joined: 2008-08-01
Points: 0

I'm glad I'm not the only one that can replicate the issue. Does anyone think this is an easy fix? Should I address this somewhere else to make it a bug ticket?

Thanks

davyp
Offline
Joined: 2007-01-03
Points: 0

I added a sanity check to my Windows Mobile MIDP builds to prevent the crash from happening. If you
like, you can check with the latest builds on my website if you can reproduce the crash. I have also
sent the patch to the phoneME project leads.

Davy

davyp
Offline
Joined: 2007-01-03
Points: 0

And as of revision 19059 the bug is fixed in subversion as well. Thanks sergio_n for committing
the patch in svn (and fixing similar bugs elsewhere)

Davy

ashish_nagpur
Offline
Joined: 2010-04-27
Points: 0

HI All,

Currently i am facing this issue very badly..

i must need to solve this..

I didnt found any workaround to solve this issue..

I check the latest version from svn.. and i am still stuck with the same issue..

Can any one tell me how to solve this..

I am using j2me lwuit..

Thanks

Ashish..

davyp
Offline
Joined: 2007-01-03
Points: 0

The issue that was reported above has already been fixed in svn truck a while ago and not related
to LWUIT. I think your issue is probably related to something else. If it is a Java exception, it could
be an issue with the LWUIT/application. But it it is a fatal crash of the VM, I don't think LWUIT
is causing it. Could you give a few more details of what errors you get and how you reproduce
them?

Davy