Open Bug 1480432 Opened Last year Updated 8 months ago
Crash in libstdc++.so@0x2fcf
This bug was filed from the Socorro interface and is report bp-f87bbb4f-7661-41ac-9d93-34d150180801. ============================================================= All of these crashes occurred with phones running Kit Kat: https://bit.ly/2O7WVeX Although present in 61, this is rising as we go through Beta 62 cycle so I am adding a bug for it. The comments are not particularly useful. No particular pattern in the URLs either - facebook, youtube and google searches seem to predominate the URL list. Top 10 frames of crashing thread: 0 libc.so libc.so@0x24c79 1 libc.so libc.so@0xa7eaf 2 libc.so libc.so@0xabd36 3 libstdc++.so libstdc++.so@0x2fcf 4 libdvm.so libdvm.so@0x8bb80 5 libcrypto.so libcrypto.so@0x169e73 6 libcrypto.so libcrypto.so@0xc3ed0 7 libcrypto.so libcrypto.so@0x74536 8 libcrypto.so libcrypto.so@0x761ad 9 libcrypto.so libcrypto.so@0x9eae0 =============================================================
These are all x86 users, mostly tablets.
Comment 1 is correct, tablets running API 18 and 19. In b13 there were 41 crashes/40 installs.
Susheel, is there someone that can look at this? It's been happening going back a lot of releases, thanks.
Marcia, is this still a crasher you think we should spend time on? We have no STR and also may require someone with c++ expertise to fix.
Note: 0xdeadbaad in Android means (usually) heap corruption (native abort() in libc)
(In reply to :sdaswani only needinfo from comment #4) > Marcia, is this still a crasher you think we should spend time on? We have > no STR and also may require someone with c++ expertise to fix. 62 just came out - I guess we can wait to see what kind of volume it amasses in that release and whether we get any other useful information.
Marcia how is the volume looking now?
(In reply to :sdaswani only needinfo from comment #7) > Marcia how is the volume looking now? 62.0.1 has 419 crashes, which isn't particularly high.
Too late to fix in 62 since we are releasing 63 very soon. Crash volume in 63 looks fairly moderate as well - 26 crashes in 63.0b11 in the last week.
Device specific, not very high crash volume. Stalled unless we get new information.
Tagging as [geckoview:p3] since this native code crash probably affects GV in addition to Fennec.
You need to log in before you can comment on or make changes to this bug.