-
Notifications
You must be signed in to change notification settings - Fork 2.4k
Android + PG crashes when only one input on page #3208
Comments
That is bizarre. I can't imagine what would cause this because we're only adding a few styles to the input for theming. Could you move the label inside the form, then try to test this without mobile to see if that is defintely the cause? .................................. . . . . On Dec 2, 2011, at 11:36 AM, "chipqcl" reply@reply.github.com wrote:
|
Done:
So it is related somehow to JQM. Note that it also crashes with the Android 2.1 emulator. |
Here is the logcat dump from a 2.2 emulator crash, in case it helps isolate where the problem is. D/dalvikvm( 109): GC_EXTERNAL_ALLOC freed 10925 objects / 372368 bytes in 440ms W/KeyCharacterMap( 109): No keyboard for id 0 W/KeyCharacterMap( 109): Using default keymap: /system/usr/keychars/qwerty.kcm.bin W/KeyCharacterMap( 361): No keyboard for id 0 W/KeyCharacterMap( 361): Using default keymap: /system/usr/keychars/qwerty.kcm.bin I/DEBUG ( 31): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** I/DEBUG ( 31): Build fingerprint: 'generic/sdk/generic/:2.2/FRF91/43546:eng/test-keys' I/DEBUG ( 31): pid: 361, tid: 367 >>> com.quickcatchlabs.a1 <<< I/DEBUG ( 31): signal 11 (SIGSEGV), fault addr 08e99804 I/DEBUG ( 31): r0 08e99804 r1 00000000 r2 08e99804 r3 00000001 I/DEBUG ( 31): r4 002cdd90 r5 00000001 r6 08e99800 r7 00000000 I/DEBUG ( 31): r8 46a52d80 r9 4184be3c 10 4184be24 fp 00130cd0 I/DEBUG ( 31): ip ab214468 sp 46a52c90 lr ab184584 pc af9046e4 cpsr 20000010 I/DEBUG ( 31): #00 pc 000046e4 /system/lib/libcutils.so I/DEBUG ( 31): #1 pc 00084580 /system/lib/libskia.so I/DEBUG ( 31): #2 pc 000846d4 /system/lib/libskia.so I/DEBUG ( 31): #3 pc 00086b58 /system/lib/libskia.so I/DEBUG ( 31): #4 pc 00086b98 /system/lib/libskia.so I/DEBUG ( 31): #5 pc 0008417c /system/lib/libskia.so I/DEBUG ( 31): #6 pc 000841c4 /system/lib/libskia.so I/DEBUG ( 31): #7 pc 0000c7c6 /system/lib/libwebcore.so I/DEBUG ( 31): #8 pc 00247570 /system/lib/libwebcore.so I/DEBUG ( 31): #9 pc 00247646 /system/lib/libwebcore.so I/DEBUG ( 31): #10 pc 001439d0 /system/lib/libwebcore.so I/DEBUG ( 31): #11 pc 00143a20 /system/lib/libwebcore.so I/DEBUG ( 31): #12 pc 00013974 /system/lib/libdvm.so I/DEBUG ( 31): #13 pc 0003de3c /system/lib/libdvm.so I/DEBUG ( 31): #14 pc 00037216 /system/lib/libdvm.so I/DEBUG ( 31): #15 pc 00018714 /system/lib/libdvm.so I/DEBUG ( 31): #16 pc 0001e8c4 /system/lib/libdvm.so I/DEBUG ( 31): #17 pc 0001d790 /system/lib/libdvm.so I/DEBUG ( 31): #18 pc 00053eec /system/lib/libdvm.so I/DEBUG ( 31): #19 pc 00054102 /system/lib/libdvm.so I/DEBUG ( 31): #20 pc 0004825a /system/lib/libdvm.so I/DEBUG ( 31): #21 pc 0001103c /system/lib/libc.so I/DEBUG ( 31): #22 pc 00010b20 /system/lib/libc.so I/DEBUG ( 31): I/DEBUG ( 31): code around pc: I/DEBUG ( 31): af9046c4 e2801001 e243f03f 3afffff9 e2410001 I/DEBUG ( 31): af9046d4 e8bd4010 e12fff1e e92d4010 e1a02000 I/DEBUG ( 31): af9046e4 e5920000 e3e03a0f e28fe004 e2401001 I/DEBUG ( 31): af9046f4 e243f03f 3afffff9 e2810001 e8bd4010 I/DEBUG ( 31): af904704 e12fff1e e92d4010 e1a02001 e1a04000 I/DEBUG ( 31): I/DEBUG ( 31): code around lr: I/DEBUG ( 31): ab184564 e1a07001 da00000f e3a05000 e5940008 I/DEBUG ( 31): ab184574 e7906105 e2855001 e2860004 ebfe92b7 I/DEBUG ( 31): ab184584 e3500001 1a000004 e5860004 e5961000 I/DEBUG ( 31): ab184594 e1a00006 e1a0e00f e591f004 e5942004 I/DEBUG ( 31): ab1845a4 e1520005 cafffff0 e5940008 e3500000 I/DEBUG ( 31): I/DEBUG ( 31): stack: I/DEBUG ( 31): 46a52c50 000013fc I/DEBUG ( 31): 46a52c54 000001b8 I/DEBUG ( 31): 46a52c58 46a52d80 I/DEBUG ( 31): 46a52c5c 4184be3c I/DEBUG ( 31): 46a52c60 4184be24 I/DEBUG ( 31): 46a52c64 afd0be39 /system/lib/libc.so I/DEBUG ( 31): 46a52c68 ab214410 /system/lib/libskia.so I/DEBUG ( 31): 46a52c6c afd0cd81 /system/lib/libc.so I/DEBUG ( 31): 46a52c70 0053a318 [heap] I/DEBUG ( 31): 46a52c74 ab12de08 /system/lib/libskia.so I/DEBUG ( 31): 46a52c78 00000000 I/DEBUG ( 31): 46a52c7c ab129e40 /system/lib/libskia.so I/DEBUG ( 31): 46a52c80 00000002 I/DEBUG ( 31): 46a52c84 0000001d I/DEBUG ( 31): 46a52c88 df002777 I/DEBUG ( 31): 46a52c8c e3a070ad I/DEBUG ( 31): #00 46a52c90 002cdd90 [heap] I/DEBUG ( 31): 46a52c94 ab184584 /system/lib/libskia.so I/DEBUG ( 31): #1 46a52c98 002cdd90 [heap] I/DEBUG ( 31): 46a52c9c 00000000 I/DEBUG ( 31): 46a52ca0 00000000 I/DEBUG ( 31): 46a52ca4 ab214410 /system/lib/libskia.so I/DEBUG ( 31): 46a52ca8 46a52d80 I/DEBUG ( 31): 46a52cac ab1846d8 /system/lib/libskia.so D/Zygote ( 33): Process 361 terminated by signal (11) I/WindowManager( 59): WIN DEATH: Window{450026b0 com.quickcatchlabs.a1/com.quickcatchlabs.a1.TrooplaTest paused=false} I/ActivityManager( 59): Process com.quickcatchlabs.a1 (pid 361) has died. W/WindowManager( 59): No focus window, dropping: KeyEvent{action=1 code=32 repeat=0 meta=0 scancode=32 mFlags=8} I/UsageStats( 59): Unexpected resume of com.android.launcher while already resumed in com.quickcatchlabs.a1 I/BootReceiver( 59): Copying /data/tombstones/tombstone_07 to DropBox (SYSTEM_TOMBSTONE) W/InputManagerService( 59): Got RemoteException sending setActive(false) notification to pid 361 uid 10037 D/dalvikvm( 59): GC_FOR_MALLOC freed 5659 objects / 635280 bytes in 154ms D/dalvikvm( 59): GC_FOR_MALLOC freed 446 objects / 522320 bytes in 427ms |
I've spent a bunch of time trying to isolate this, specifically by commenting out code in JQM. Most of the code related to text input or to form submission. None of it made a difference. I did find a work-around that may help identify the problem. If you add a second text input field to the form, it no longer crashes. So it looks like it may be trying some kind of auto-submit after a few characters are typed when there is only one input field. Also note that if the second input field is obscured (by using .hide() to an enclosing div, by setting that div style to display:none, or by moving that div off the page by using left-margin:-300), then it crashes. So whatever is triggering the auto-submit is very smart about what is on the visible page. |
The odd thing is there's no auto-submit logic. If you actually click on the submit button, we hijack the link to submit it by ajax, but the scripting on a normal text input is pretty much nil. |
Just ran into this as well but running under the jqtouch 1beta3 (sorry, legacy project, otherwise I use jqm) - all I need to cause the crash is to have the input element on the screen. App is single html document with many page divs. When transition to page containing input it crashes. Removing the input element no crash. On iPhone version, no crash. 2.1 emulator with PhoneGap 1.2. Not sure if this helps at all - may not be jqm issue since I am seeing it on jqtouch. UPDATE:
|
+1 on https://github.com/chipqcl. Crash on single input form. no problem on more than one input forms. Cause: the zepto or jquery, you can plug in any will make this happen. Any solutions? anyone? I have two days on this, reading changing load order of JS, whatever, to no avail. |
I have the same problem on my application. A form with just 1 input crashes on Android. I figured out that the problem is related to the time you click on the input. If you open the page that contain the forms, no problem, when you clilck the first letter and wait a while.. it crashes. If you click 1-2 letter and quickly submit the form, it works!!! Hiding a second input doesnt works as well. More than 1 input works!! Any other ideas??? |
Hi Alex, Wish I could help, but after my experience with both slow UX and Good luck! On Sun, Mar 25, 2012 at 8:01 PM, alex <
|
I closed ticket #4103 as duplicate. It has useful information in the thread though. I am also going to change the topic of this issue a little bit so it mentions the "only one input" aspect. |
I think I have same issue. My project has a html document with a
1st line |
I have run into this problem as well. It is 8 months old and seems to be a rather repeatable bug. Is there a fix? |
No solutions yet!! One year on!!! I am facing same problem on android 2.2 |
JFYI Android 2.2 x86 emulator, pceee. Crashing when transition starts (or idk when). Some times first page loaded fine but when i trying to go to the next inner page - It crashes browser. There is an oppinion that animate (or css3 transition) makes it broken. I don't really know what of these trigger memory leaks or whatever that kills browser. |
Is this two year old high priority issue still relevant? |
Im going to close this as being stale i'm going to guess its been fixed since there are no further reports in several years we can reopen if any one is still having this issue |
For anyone who still encounter this issue: |
Turning off autocomplete for the input helps in this regard. Exception stack trace : |
In a JQM/PhoneGap app running on Android 2.2, when you type three characters into a form, the app crashes (I've tested it on a Samsung Captivate and on the Android emulator, with the same results). It works fine on Android 2.3.
PhoneGap Support tells me it's an "Android webview issue" and that I should submit an issue with JQM.
Here's a mini app built to demonstrate the bug (i.e. index.html):
The text was updated successfully, but these errors were encountered: