Crash in [@ OOM | large | mozalloc_abort | moz_xmalloc | mozilla::gfx::SourceSurfaceRawData::GuaranteePersistance]
Categories
(Core :: Graphics, defect, P2)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr78 | --- | unaffected |
firefox84 | --- | wontfix |
firefox85 | + | fixed |
firefox86 | --- | fixed |
People
(Reporter: aryx, Assigned: aosmond)
Details
(Keywords: crash)
Crash Data
Attachments
(1 file)
48 bytes,
text/x-phabricator-request
|
RyanVM
:
approval-mozilla-beta+
|
Details | Review |
This looks like bug 1604535 resurrected, including mostly hitting during Facebook visits. The signature was active before but got more frequent starting with the Firefox 85 betas.
Crash report: https://crash-stats.mozilla.org/report/index/645260f9-68d4-4af7-9a17-a311d0201220
MOZ_CRASH Reason: MOZ_CRASH()
Top 10 frames of crashing thread:
0 mozglue.dll mozalloc_abort memory/mozalloc/mozalloc_abort.cpp:33
1 mozglue.dll mozalloc_handle_oom memory/mozalloc/mozalloc_oom.cpp:51
2 mozglue.dll moz_xmalloc memory/mozalloc/mozalloc.cpp:54
3 xul.dll mozilla::gfx::SourceSurfaceRawData::GuaranteePersistance gfx/2d/SourceSurfaceRawData.cpp:39
4 xul.dll mozilla::gfx::DrawTargetTiled::FillRect gfx/2d/DrawTargetTiled.cpp:229
5 xul.dll mozilla::layers::FillRectWithMask gfx/layers/basic/BasicLayersImpl.cpp:129
6 xul.dll mozilla::layers::FillRectWithMask gfx/layers/basic/BasicLayersImpl.cpp:151
7 xul.dll mozilla::layers::BasicImageLayer::Paint gfx/layers/basic/BasicImageLayer.cpp:80
8 xul.dll mozilla::layers::BasicLayerManager::PaintSelfOrChildren gfx/layers/basic/BasicLayerManager.cpp:701
9 xul.dll mozilla::layers::BasicLayerManager::PaintLayer gfx/layers/basic/BasicLayerManager.cpp:871
Reporter | ||
Updated•3 years ago
|
Assignee | ||
Comment 1•3 years ago
|
||
This is probably not an image -- none of the surfaces from imagelib would trigger a copy during GuaranteePersistance. This is most likely a video or canvas.
Updated•3 years ago
|
Comment 2•3 years ago
|
||
Andrew can you look into this or redirect to media folks? The OOM increase between 84 and 85 is a bit worrying.
Assignee | ||
Comment 3•3 years ago
|
||
I'll disable OMTP for more cases. We already disable it for users with < 2 GB physical memory, and the majority of these crashes are for users with > 2 GB memory but < 2 GB virtual memory (most 32-bit Firefox on 32-bit Windows users I imagine fall into this bucket). It will take too long to debug this and this sort of allocation will not happen very often with WebRender.
Assignee | ||
Updated•3 years ago
|
Assignee | ||
Comment 4•3 years ago
|
||
Pushed by aosmond@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/65e409aa846d Disable OMTP for users with less than 2 GB of virtual memory. r=jrmuizel
Comment 6•3 years ago
•
|
||
Backed out for causing reftest failures.
Backout link: https://hg.mozilla.org/integration/autoland/rev/b9f7f8d17f62f51076bfca3cff8f0986fa091ff1
Failure log: https://treeherder.mozilla.org/logviewer?job_id=326104679&repo=autoland&lineNumber=25944
https://treeherder.mozilla.org/logviewer?job_id=326104679&repo=autoland&lineNumber=25944
Pushed by aosmond@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/d4d31680d3ce Disable OMTP for users with less than 2 GB of virtual memory. r=jrmuizel
Reporter | ||
Comment 9•3 years ago
|
||
bugherder |
Assignee | ||
Comment 10•3 years ago
|
||
Comment on attachment 9195915 [details]
Bug 1683653 - Disable OMTP for users with less than 2 GB of virtual memory.
Beta/Release Uplift Approval Request
- User impact if declined: OTMP users with low powered hardware may experience more frequent OOMs
- Is this code covered by automated tests?: Yes
- Has the fix been verified in Nightly?: Yes
- Needs manual test from QE?: No
- If yes, steps to reproduce:
- List of other uplifts needed: None
- Risk to taking this patch: Low
- Why is the change risky/not risky? (and alternatives if risky): This is just an expansion of a previous patch to disable OMTP for some users. Very simple criteria. Covered by Windows 7 automated tests. Worst case we disable OMTP for more users than we expect but as we continue to migrate more users to WebRender (which doesn't rely on OMTP) this should become less of an issue.
- String changes made/needed:
Assignee | ||
Comment 11•3 years ago
|
||
I don't think we can truly verify in nightly just because this doesn't solve the crashes, it just removes the users most likely to be affected and benefit the least from OMTP. The crash rate isn't high enough in nightly to confirm this.
Comment 12•3 years ago
|
||
Comment on attachment 9195915 [details]
Bug 1683653 - Disable OMTP for users with less than 2 GB of virtual memory.
Approved for 85.0rc1.
Comment 13•3 years ago
|
||
bugherder uplift |
Updated•3 years ago
|
Reporter | ||
Comment 14•3 years ago
|
||
Should a new bug be created for the crash reports with 86+ or shall this one be reopened?
Assignee | ||
Comment 15•3 years ago
|
||
We disabled OMTP in bug 1694248 so they should go away in 88.
Comment 16•3 years ago
|
||
memory-leak key word?
Description
•