100% browser CPU.

[John J. Barton]

The page
https://developer.mozilla.org/en/dom/document.getelementsbyclassname
does not document the method call return types, so I thought I would
just check the link at the bottom of that page:
http://whatwg.org/specs/web-apps/current-work/#getelementsbyclassname
Unfortunately my CPU pegged 100%. Naturally I thought Firebug has jammed
things up, but I saw no trace outputs. In fact, I could get almost
nothing out of Firebug/Chromebug because the CPU was pegged. Eventually
I tried in a clean profile and the CPU is still pegged. While looking
through bugzilla on another firefox instance, the page did finally stop
burning CPU, so it's not hung. I did not find in bugs under "HTML5
whatwg" related to performance. (I tried FF 3.5.5 and FF 3.6 nightly).

Evidently this is not Javascript if the dialog for too much time does
not come up?

What should happen here? I'd say not what I experienced.

jjb

[Mike Beltzner]

On 2009-12-06, at 1:26 PM, John J. Barton wrote:

> What should happen here? I'd say not what I experienced.

No, that's the desired behaviour, obviously. :p

Did you file a bug on the performance issue?

cheers,
mike

[Martijn]

See https://bugzilla.mozilla.org/show_bug.cgi?id=481131

Regards,
Martijn

> _______________________________________________
> dev-platform mailing list
> dev-pl...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-platform
>

--
Martijn Wargers - Help Mozilla!
http://quality.mozilla.org/
http://wiki.mozilla.org/Mozilla_QA_Community
irc://irc.mozilla.org/qa - /nick mw22

[Boris Zbarsky]

On 12/6/09 10:26 AM, John J. Barton wrote:
> What should happen here?

We should finish up 1.9.2rc1, and then reopen m-c, and then roc will
land the patches that make this problem go away.

-Boris