Closed Bug 899790 Opened 7 years ago Closed 4 years ago
crash in libm
.so@0x12014 | cast Native
This bug was filed from the Socorro interface and is report bp-07a9d3b4-be3e-43d7-8437-5b36d2130730 . ============================================================= Build ID : 20130531232151 1.0.1 Ikura Frame Module Signature Source 0 libm.so libm.so@0x12014 1 libxul.so castNative android/gecko/js/xpconnect/src/XPCQuickStubs.cpp More crashes : https://crash-stats.mozilla.com/report/list?product=B2G&signature=libm.so%400x12014 This particular crash was in homescreen.
I am also seeing : https://crash-stats.mozilla.com/report/index/45c0c6a1-373b-4de4-8706-d959c2130730 Frame Module Signature Source 0 libm.so libm.so@0x12014 1 libmozsqlite3.so pagerSyncHotJournal /data/jenkins/jobs/build-unagi/workspace/gecko/db/sqlite3/src/sqlite3.c 2 libxul.so castNative /home/zhangchun/P752D04_TME/PRE_2/android/gecko/js/xpconnect/src/XPCQuickStubs.cpp I think this might be an automation crash? It would explain all the dups.
Neither of these match automation - the build, device and seconds since install. Finally we don't automatically submit crash reports from automation. It does however look like something automated is filing them all.
We're seeing this quite a lot on 1.0.1 on ZTE Open, see the "more crashes" link in comment #0 and https://crash-analysis.mozilla.com/rkaiser/2013-07-31/2013-07-31.b2g.topcrashes.weekly.html#b2g-22.214.171.124-prerelease (not yet marking topcrash as we seem to get a lot of dupes, most of those sent to us at pretty much the same time). Note that there's an interesting pattern of addresses there, each batch of closely-together-submitted crashes altering randomly between at least two of those: 0x4007c014 and 0x400a4014 (Jul 30) 0x400a1014 and 0x40040014 (Jul 28) 0x40016014, 0x4013a014, 0x400ad014, 0x40128014, 0x400c7014, 0x40097014 (Jul 26) etc. It's always 0x40xx014.
(In reply to Robert Kaiser (:firstname.lastname@example.org) from comment #3) > most of those sent to us at pretty much the same time See bug 895246 comment 4 for a possible explanation.
Mass update: Resolve wontfix all issues with legacy homescreens. As of 2.6 we have a new homescreen and having these issues open is confusing. All issues will block bug 1231115 so we can use that to re-visit any of these if needed.
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.