Open
Bug 1349875
Opened 9 years ago
Updated 2 years ago
Assertion failure: aThebesContext->CurrentOp() == CompositionOp::OP_OVER, at PresShell.cpp:4735
Categories
(Core :: Graphics, defect, P3)
Core
Graphics
Tracking
()
NEW
People
(Reporter: cbook, Assigned: bas.schouten)
References
()
Details
(Keywords: assertion, Whiteboard: [gfx-noted])
Attachments
(1 file)
|
195.02 KB,
text/plain
|
Details |
Found via topsite Tests on beta to trunk debug builds and reproduced on latest m-c trunk debug build on windows 7
Steps to reproduce:
-> Load http://www.internetretailer.com
---> Assertion failure after a few seconds
[GFX3-]: Surface size too large (exceeds allocation limit)!
[GFX3-]: Surface size too large (exceeds extent limit)!
Crash Annotation GraphicsCriticalError: |[C0][GFX1-]: Failed to allocate a surface due to invalid size (CDT) Size(7121,21185) (t=68.635) [GFX1-]: Failed to allocate a sur
[GFX3-]: Surface size too large (exceeds allocation limit)!
[GFX3-]: Surface size too large (exceeds extent limit)!
Crash Annotation GraphicsCriticalError: |[C0][GFX1-]: Failed to allocate a surface due to invalid size (CDT) Size(7121,21185) (t=68.635) |[C1][GFX1-]: Failed to allocate
ze(7121,21185)
Assertion failure: aThebesContext->CurrentOp() == CompositionOp::OP_OVER, at c:/builds/moz2_slave/m-cen-w32-d-000000000000000000/build/src/layout/base/PresShell.cpp:4735
| Reporter | ||
Comment 1•9 years ago
|
||
Michael, could you take a look at this assertion failure ? Seems its gfx (not sure about it) so maybe you know who could take a look ?
Flags: needinfo?(cleu)
Comment 2•9 years ago
|
||
I can reproduce this crash, it seems to be another oversized memory allocation issue.
Since the crash point is related to SVG, I think CJ will know who can take a look into it.
Hi CJ, any thought about this one?
Flags: needinfo?(cleu) → needinfo?(cku)
I guess this is because we setop at this line
http://searchfox.org/mozilla-central/source/gfx/thebes/gfxUtils.cpp#341
I don't have a window build on hand to verify.
Michael, can you try to remove this line and see whether we will still hit this assertion.
Flags: needinfo?(cku)
Nono...I just said that is why we hit this assertion.
When you hit an assertion, you have several choices. You can either correct the assertion or correct the code which hit that assertion. You may provide a solution and discuss with the developer who check-in relative code.
Flags: needinfo?(cku)
| Assignee | ||
Comment 6•9 years ago
|
||
I suspect this is due to a patch I landed a long time ago.
Assignee: nobody → bas
Priority: -- → P3
Whiteboard: [gfx-noted]
| Comment hidden (Intermittent Failures Robot) |
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•