Open
Bug 1499537
Opened 7 years ago
Updated 1 year ago
When WebRender allocates too much texture memory the whole OS can go down
Categories
(Core :: Graphics: WebRender, enhancement, P3)
Core
Graphics: WebRender
Tracking
()
NEW
People
(Reporter: nical, Unassigned)
References
(Blocks 1 open bug)
Details
See the associated issue at https://github.com/servo/webrender/issues/3207 for a more detailed description of the problem.
In gecko allocating too much memory usually either results in an OOM crash or partially rendered content. In WebRender some bad cases can freeze the computer completely. On the hardware that I have handy the only thing to do is force reboot the computer, we should at least crash before we get to this type of situation.
There are already bugs about reducing memory usage (without compromising on the experience), in this bug I propose we pursue failing more gracefully if all else fails.
Updated•7 years ago
|
Blocks: stage-wr-trains
Priority: -- → P3
Comment 1•7 years ago
|
||
We should aspire to do better here (perhaps making sure we're able to track memory gpu better), but it doesn't need to block.
Updated•3 years ago
|
Severity: normal → S3
Updated•1 year ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•