Closed Bug 784757 Opened 12 years ago Closed 12 years ago

Kyocera Echo - Crash on startup (Cannot load library: alloc_mem_region[889]: OOPS: 68 cannot map library 'libEGL_adreno200.so'. no vspace available)

Categories

(Firefox for Android Graveyard :: General, defect)

Product:
Firefox for Android Graveyard
Component:
General
Platform:
ARM
Android
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

(firefox14 unaffected, firefox15+ disabled, firefox16 unaffected, firefox17 unaffected, fennec+)

Status:
RESOLVED WORKSFORME
Tracking Flags:
Tracking Status
firefox14 --- unaffected
firefox15 + disabled
firefox16 --- unaffected
firefox17 --- unaffected
fennec + ---

People

(Reporter: aaronmt, Unassigned)

References

(
URL
)

Details

(Keywords: crash, relnote, Whiteboard: [native-crash][15.0b6][startupcrash])

load_driver(/system/lib/egl/libEGL_adreno200.so): Cannot load library: alloc_mem_region[889]: OOPS: 68 cannot map library 'libEGL_adreno200.so'. no vspace available. http://www.appthwack.com/public/4kxyti28dl/jobrun/470947
Whiteboard: [native-crash] → [native-crash][15.0b6]
Perhaps we want to block this device and relnote the incompatibility.
Whiteboard: [native-crash][15.0b6] → [native-crash][15.0b6][startupcrash]
This seems to be only the Kyocera Echo. Checked the HTC Desire which has the same GPU, Adreno 200.
The current Aurora and Nightly builds do not crash.
status-firefox16: --- → unaffected
status-firefox17: --- → unaffected
tracking-firefox15: --- → ?
Does Firefox 14(.0.1) crash on startup when using a Kyocera Echo?
(In reply to Alex Keybl [:akeybl] from comment #4) > Does Firefox 14(.0.1) crash on startup when using a Kyocera Echo? This run (http://www.appthwack.com/public/ZfzSJqr1Nd ) does not indicate so. Kevin can try his device in hand tomorrow.
status-firefox14: --- → unaffected
tracking-fennec: --- → ?
let's rel note and block this phone in the market
Keywords: relnote
(In reply to Brad Lassey [:blassey] from comment #6) > let's rel note and block this phone in the market I agree, but we definitely need to figure out what's going on in case this may affect other devices. Blocking a single phone may not do the trick. Let's find the regressing bug.
tracking-firefox15: ? → +
Keywords: regressionwindow-wanted
Depends on: 785152
Blocks: 785152
No longer depends on: 785152
tracking-fennec: ? → +
Marking "disabled" since we did block the phone in bug 785152 and noted it in release notes http://www.mozilla.org/en-US/mobile/15.0/releasenotes/
status-firefox15: affected → disabled
QA triage note - will probably just let this ride out into 16 as it's fixed there
Works for me with the release of Fx 16 tomorrow.
Status: NEW → RESOLVED
Closed: 12 years ago
Keywords: regressionwindow-wanted
Resolution: --- → WORKSFORME
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.