Closed
Bug 892930
Opened 11 years ago
Closed 10 years ago
WebGL crash due to "Trying to allocate an infallible array that's too big" [@mozilla::WebGLTexture::EnsureMaxLevelWithCustomImagesAtLeast]
Categories
(Core :: Graphics: CanvasWebGL, defect)
Tracking
()
RESOLVED
WORKSFORME
Tracking | Status | |
---|---|---|
firefox23 | --- | unaffected |
firefox24 | --- | affected |
firefox25 | --- | affected |
People
(Reporter: posidron, Assigned: wlitwinczyk)
References
Details
(Keywords: crash, regression, testcase)
Crash Data
Attachments
(2 files)
Reporter | ||
Comment 1•11 years ago
|
||
Updated•11 years ago
|
Blocks: 819633
Crash Signature: [@ mozalloc_abort(char const* const) | nsTArrayInfallibleAllocator::SizeTooBig() ]
Comment 2•11 years ago
|
||
This appears to be a crash when copyTexImage2d'ing with x,y,width,height at comically large values. Since x,y is out of bounds of the FB, we allocate a buffer to make sure the resulting texture is zero'd properly. This is where it appears to be failing.
Updated•11 years ago
|
status-firefox23:
--- → unaffected
status-firefox24:
--- → affected
status-firefox25:
--- → affected
Keywords: regression
OS: Mac OS X → All
Hardware: x86_64 → All
Version: Trunk → 24 Branch
Assignee | ||
Updated•10 years ago
|
Assignee: nobody → wlitwinczyk
Assignee | ||
Comment 3•10 years ago
|
||
Can no longer get this to crash. The code has since been changed to more rigorously verify that the function has been passed acceptable parameters prior to doing anything meaningful with them.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•