Closed
Bug 902542
Opened 12 years ago
Closed 4 years ago
many big canvas elements → quick use/eat up of RAM/memory (→ browser or system crash)
Categories
(Core :: JavaScript: GC, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: Aleksej, Unassigned)
Details
(Keywords: crash, testcase, Whiteboard: DUPEME?)
Attachments
(2 files)
ohmed posted at http://habrahabr.ru/post/188864/: "…while writing my project, I have accidentally created many, many big canvas elements. Had to restart my OS as the result."
Reproduced with 2013-08-04-03-02-07-mozilla-central-firefox-25.0a1.en-US.linux-x86_64
Comments say the page causes RAM overuse or at least tab crash or hang with Opera 12, and Chrome and Chromium 28, and Safari on iOS.
| Reporter | ||
Updated•12 years ago
|
Component: Untriaged → Canvas: 2D
Product: Firefox → Core
| Reporter | ||
Comment 1•12 years ago
|
||
Unlike bug 721229 and bug 881644, there seem to be no gradients. I haven't tried without HWA (bug 790896).
Whiteboard: DUPEME?
| Reporter | ||
Updated•12 years ago
|
Summary: many big canvas elements → quick use up of RAM/memory → many big canvas elements → quick use up of RAM/memory (→ browser or system crash)
| Reporter | ||
Updated•12 years ago
|
Attachment #787017 -
Attachment description: page from http://ec2-54-229-117-209.eu-west-1.compute.amazonaws.com/party.html (Google ad/analytics removed) → (DANGEROUS) page from http://ec2-54-229-117-209.eu-west-1.compute.amazonaws.com/party.html (Google ad/analytics removed)
Attachment #787017 -
Attachment mime type: text/html → text/plain
| Reporter | ||
Updated•12 years ago
|
Summary: many big canvas elements → quick use up of RAM/memory (→ browser or system crash) → many big canvas elements → quick use/eat up of RAM/memory (→ browser or system crash)
Updated•12 years ago
|
Sounds like a straightforward resource consumption issue -- especially with a 64-bit build, we can keep allocating lots and lots of memory. Eventually, your OS will start complaining or having issues, but I don't think there's anything we can (or should) do.
Aleksej, do you still see this behaviour with current 64-bit builds?
Flags: needinfo?(deletesoftware+moz)
| Reporter | ||
Comment 4•9 years ago
|
||
Still happens with 2016-07-08-03-02-16-mozilla-central-firefox-50.0a1.ru.linux-x86_64.
Flags: needinfo?(deletesoftware+moz)
I checked this locally. In Firefox Nightly 50.0a1 I get ~77% CPU usage and ever-increasing memory until it eventually OOMs. In Chrome I get over 100% CPU usage and memory usage hovering between 200 and 500MB. Looking at a Performance profile in Nightly I can see we're doing a lot of GC calls. If we're failing to manage these GC calls properly I suppose that could explain the memory usage pattern. Based on this however I am not convinced it's a graphics bug.
Comment 6•4 years ago
|
||
Closing this one as incomplete since the reporter is no longer available but we can reopen this issue in case it starts to reoccur.
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•