Issue 242494 in chromium: Svg filter causing high memory/cpu usage.

[chro...@googlecode.com]

Status: Unconfirmed
Owner: ----
Labels: Type-Bug Pri-2

New issue 242494 by shop...@gmail.com: Svg filter causing high memory/cpu
usage.
http://code.google.com/p/chromium/issues/detail?id=242494

Chrome Version : Version 27.0.1423.0 (184404)

What steps will reproduce the problem?
1. Open test.htm
2. show Developer Tools From Tools

What is the expected result?
- Show "This tab has become unresponsive" wait/kill prompter.
- Show Loading indicator when the page is loading.
- Allow users to close "Developer Tools".

What happens instead?
- The Tab consumes 100% CPU Usage.
- Right click on webpage Body doesn't open Context menu.

Please provide any additional information below. Attach a screenshot if
possible.

- After reloading the page, the loading indicator appears.
- No problem on Safari 5.1.7 and Opera 12.15.

Attachments:
test.htm 142 bytes

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[chro...@googlecode.com]

Updates:
Labels: Cr-Blink-SVG

Comment #1 on issue 242494 by tk...@chromium.org: Svg filter causing high
memory/cpu usage.
http://code.google.com/p/chromium/issues/detail?id=242494

(No comment was entered for this change.)

[chro...@googlecode.com]

Updates:
Status: Available
Cc: senorbla...@chromium.org

Comment #2 on issue 242494 by p...@chromium.org: Svg filter causing high

[chro...@googlecode.com]

Updates:
Labels: Cr-Internals-Skia

Comment #3 on issue 242494 by schen...@chromium.org: Svg filter causing

high memory/cpu usage.
http://code.google.com/p/chromium/issues/detail?id=242494

Using numOctaves=99 means performing an outrageous amount of work for no
visual benefit. It's not surprising it's slow. There is no point in using
any more than log_2(size) octaves. In this case about 8.

I would mark this as WontFix, but in practice we should probably add
something to cut off the octave iteration at the visible resolution.

[chro...@googlecode.com]

Comment #7 on issue 242494 by f...@opera.com: Svg filter causing high
memory/cpu usage.
http://code.google.com/p/chromium/issues/detail?id=242494

Presto (ref. Opera 12.15 above) had this ('numOctaves') clamped to 9 (based
on similar reasoning as in #3 - but adding 1 for rounding.) Probably best
left to the generator implementations though (SkPerlinNoiseShader etc.)