Closed
Bug 312631
Opened 20 years ago
Closed 19 years ago
100% CPU usage using animated gifs in svgs with <use> element
Categories
(Core :: SVG, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: jvdvegt, Unassigned)
Details
(Keywords: testcase)
Attachments
(2 files, 1 obsolete file)
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050922 Epiphany/1.6.1 (Ubuntu) (Ubuntu package 1.0.7)
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8b5) Gecko/20051006 Firefox/1.4.1
When viewing attached SVG image, Firefox's CPU usage immediately increases to
100% and it becomes rather unresponsive. The problem does not occur in SVG
images with animated gifs but not <use> elements.
Reproducible: Always
Steps to Reproduce:
Comment 3•20 years ago
|
||
Attachment #199751 -
Attachment is obsolete: true
Comment 4•20 years ago
|
||
Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b5) Gecko/20051016
Firefox/1.4.1 ID:2005101602
WFM (no memusage ,<1%)
Comment 5•20 years ago
|
||
Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b5) Gecko/20051016
Firefox/1.4.1 ID:2005101605
WFM. Any other linux people able to test for this?
Keywords: testcase
Summary: 100% CPU usage using animated gifs in svgs sith <use> element → 100% CPU usage using animated gifs in svgs with <use> element
Updated•20 years ago
|
Assignee: nobody → general
Component: General → SVG
Product: Firefox → Core
QA Contact: general → ian
Version: unspecified → 1.8 Branch
Comment 6•20 years ago
|
||
jereon, is this an issue with Firefox 1.5?
Comment 7•19 years ago
|
||
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1) Gecko/20061023 SUSE/2.0-30 Firefox/2.0
wfm too on Linux...
Comment 8•19 years ago
|
||
Resolving WFM as per comments 4, 5 and 7.
Reporter, if you still see this bug then please reopen!
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → WORKSFORME
Issue seems solved with 2.0.0.4! Sorry for not getting back earlier.... Feel free to change the status to 'fixed', I'm not sure if I'm entitled to.
You need to log in
before you can comment on or make changes to this bug.
Description
•