Closed
Bug 1448106
Opened 6 years ago
Closed 6 years ago
Crash in PR_LoadLibraryWithFlags | mozilla::gl::GLLibraryLoader::OpenLibrary
Categories
(Core :: Graphics, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 1447607
Tracking | Status | |
---|---|---|
firefox-esr52 | --- | unaffected |
firefox59 | --- | unaffected |
firefox60 | --- | unaffected |
firefox61 | + | fixed |
People
(Reporter: marcia, Unassigned)
References
Details
(Keywords: crash, regression, Whiteboard: [gfx-noted])
Crash Data
This bug was filed from the Socorro interface and is report bp-6608fac5-3b22-4754-bc8c-241420180322. ============================================================= Seen while looking at nightly android crash stats: https://bit.ly/2FV88zI. Crashes started using Build 20180321040529. 242 crashes/158 installs so far. Possible regression range based on Build ID: https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=bfb7edfd0436db388bb9e103b8ad817fc50bfdcf&tochange=e636edf00e6fbdc3206c9df4a1548ae38b3d13fa Top 10 frames of crashing thread: 0 libc.so libc.so@0x18aee 1 libnss3.so PR_LoadLibraryWithFlags nsprpub/pr/src/linking/prlink.c:941 2 libxul.so mozilla::gl::GLLibraryLoader::OpenLibrary gfx/gl/GLLibraryLoader.cpp:23 3 libxul.so mozilla::gl::GLContextEGL::Init gfx/gl/GLContextProviderEGL.cpp:270 4 libxul.so mozilla::gl::GLContextEGL::~GLContextEGL 5 libxul.so mozilla::gl::GLContextEGL::CreateGLContext gfx/gl/GLContextProviderEGL.cpp:539 6 libEGL.so libEGL.so@0xc687 7 libxul.so mozilla::gl::GLContextEGLFactory::Create gfx/gl/GLContextProviderEGL.cpp:208 8 libart.so libart.so@0x98c7e 9 libart.so libart.so@0x406141 =============================================================
Comment 1•6 years ago
|
||
Anything stand out in that regression to you, snorp or esawin?
status-firefox59:
--- → unaffected
status-firefox60:
--- → unaffected
status-firefox-esr52:
--- → unaffected
tracking-firefox61:
--- → +
Flags: needinfo?(snorp)
Flags: needinfo?(esawin)
I don't see anything obvious at all. That nspr code hasn't changed in 10 years (seriously!).
Flags: needinfo?(snorp)
Reporter | ||
Comment 3•6 years ago
|
||
Comments: *Crash occurred after last night's update when I tried to open the browser by clicking an email link. *clicked a link in an email that automatically opens the browser and instead it crashed *it's been crashing since last night everytime I unlock the phone and whenever I open an external link
(In reply to Marcia Knous [:marcia - needinfo? me] from comment #3) > Comments: > > *Crash occurred after last night's update when I tried to open the browser > by clicking an email link. > *clicked a link in an email that automatically opens the browser and instead > it crashed > *it's been crashing since last night everytime I unlock the phone and > whenever I open an external link So it hasn't ever successfully started since the update? This sounds like another case of "apk corruption", and would also explain why we have such weird-ass crash reports associated with this. Can you try uninstalling Nightly, then reinstalling? Eugen, for some reason I wonder if the update handler could be causing this somehow. What do you say to disabling it on Nightly for a while?
Flags: needinfo?(mozillamarcia.knous)
Reporter | ||
Comment 5•6 years ago
|
||
(In reply to James Willcox (:snorp) (jwillcox@mozilla.com) from comment #4) > (In reply to Marcia Knous [:marcia - needinfo? me] from comment #3) > > Comments: > > > > *Crash occurred after last night's update when I tried to open the browser > > by clicking an email link. > > *clicked a link in an email that automatically opens the browser and instead > > it crashed > > *it's been crashing since last night everytime I unlock the phone and > > whenever I open an external link > > So it hasn't ever successfully started since the update? This sounds like > another case of "apk corruption", and would also explain why we have such > weird-ass crash reports associated with this. Can you try uninstalling > Nightly, then reinstalling? > > Eugen, for some reason I wonder if the update handler could be causing this > somehow. What do you say to disabling it on Nightly for a while? I actually haven't experienced this crash, these are just user comments I have seen in Socorro. ni on Ioana to see if she can reproduce - there is a very wide spectrum of devices affected. I will try with my nexus 6, but so far I haven't been able to repro this particular crash.
Flags: needinfo?(mozillamarcia.knous) → needinfo?(ioana.chiorean)
Comment 6•6 years ago
|
||
I get this every time I click a bugzilla link in my gmail app and it tries to open a nightly geckoview.
Updated•6 years ago
|
Whiteboard: [gfx-noted]
Comment 8•6 years ago
|
||
Devices used for test: - Google Pixel(Android 8.1.0) - Pixel XL (Android 8.1.0) - Huawei P9 Lite(Android 6.0) - HTC Desire 820 (Android 6.0.1) - Samsung Galaxy S8 (Android 7.0) - HTC 10 (Android 8.0) - Huawei m3 Lite 10 (Android 7.0). We couldn't reproduce the crash following the steps from comment 3 on Nightly build (03/28).
Flags: needinfo?(sorina.florean)
Reporter | ||
Comment 9•6 years ago
|
||
ONEPLUS A3003 has the highest number of crashes, followed by the Nexus 5X. Other comments: *open url from Telegram X and dump happens *opening a link from Gmail on phone. *Opening a hyperlink on reddit will crash it every time
Pretty sure this is the same as bug 1447607
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → DUPLICATE
Updated•6 years ago
|
Flags: needinfo?(esawin)
Comment 11•6 years ago
|
||
Crash is gone, looks like bug 1447607 worked \m/
Flags: needinfo?(ioana.chiorean)
You need to log in
before you can comment on or make changes to this bug.
Description
•