User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0) Gecko/20100101 Firefox/4.0
Build Identifier: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0) Gecko/20100101 Firefox/4.0
It seems when selecting checkboxes on the Netapp Admin pages, seems to cause Firefox 4 to go into an infinity loop, where it refuses to respond. This also occurs in Safemode, and in a new profile in Safe Mode.
In Process Explorer, it seems to run the CPU to 100% (of at least 1 processor), and the memory will climb for a few minutes upto around 300Mb then it will drop by around 100Mb and this will repeat.
Steps to Reproduce:
1. Load Page to Manage Quotas
2. Click on Checkbox
3. Wait for a long time, it doesn't seem to crash or anything.
Locks up Firefox
It should check the box
I don't think there is anything at the moment. Though limits the usefulness
Created attachment 522757 [details]
Mini Dumpfile from Firefox
I have also seen this in the netapp communities as well
Please create a stack trace with Windbg
Does it work in Fx 3.6? Does it work in one of the past Fx4 Betas?
it did work in 3.6, but I never tried in the Betas if I recall, as I had not required to manage the device in question, while I was using the Betas
Created attachment 523045 [details]
This seems to be the loop:
This will be still difficult without a testcase and I'm really lost if it comes to select a component for this. Can you help here Boris ?
CCing some more folks.
The description doesn't sound like infinite recursion (e.g. no crash). So what's really going on?
Reporter, are you able to attach the relevant HTML to this bug?
possibly but it does have to get sanitized heavily, since it deals with production stuff. You may be able to contact netapp, and ask for their Simulator.
jason, is the concern about making the HTML completely public, or about anyone at all being able to see it?
That is, are you happier sending the HTML to me by private mail, with the promise that I would not be posting it anywhere?
Chris, do we have contacts at netapp?
it seems that there are a large number of
<label for="vol-1" /><input name="vol-13" type="hidden" value="V00067" title="vol-13" id="vol-1" />
type lines, at 10 it is very slow, at 20 it stops responding.
Created attachment 523068 [details]
html causing problems
it has been slightly santized.
Comment on attachment 523068 [details]
html causing problems
At 20 <label> tags, it stops responding while it's processing, and takes around 5 minutes or more to start responding.
Doing some tests, it looks like the following
13 - 3 seconds
14 - 6 seconds
16 - 10 seconds or so
Ah, so tons of nested labels, and then you click something inside the innermost one. I see.
In firefox 3.6 the labels do NOT nest.
They do nest in Opera and Webkit, though.
Are we ending up with something silly like activating labels exponentially many times in the depth of nesting?
Oh, http://software.hixie.ch/utilities/js/live-dom-viewer/?%3C!DOCTYPE%20html%3E%0A%3Clabel%2F%3E%0A%3Clabel%2F%3E for the testcase for parser behavior.
Actually even clicking on the first item in the list triggers this.
Created attachment 524468 [details] [diff] [review]
Actually, label elements ignore click events coming from their descendants but the code doing that go from the target of the event to the label but doesn't check siblings, only parents.
The behavior we have with this patch seems to be the same on Opera. I do not have any webkit browser on this laptop.
Created attachment 524470 [details]
If someone can give me the results when clicking on the rightest label (with various browsers): it should be 1/6.
It's 1/6 in Safari, Chrome, and Opera over here.
Nice! Thanks for checking :)
Comment on attachment 524468 [details] [diff] [review]
I don't understand why you check only previoussibling and not nextsibling.
(In reply to comment #23)
> Comment on attachment 524468 [details] [diff] [review]
> Patch v1
> I don't understand why you check only previoussibling and not nextsibling.
This code tries to prevent sending a click event to the control element if it has been sent to it already. AFAIK, this can't happen if the element is after the target element in tree order. IOW, the method reproduces how the event bubbles and make sure that the control element isn't in the bubbling path.
Created attachment 526976 [details]
With or without the patch our behavior when clicking the last checkbox is different than on Opera or Chromium
Though, actually, I didn't check that Opera or Chromium parse the testcase
the same way as gecko.
Setting "html5.parse.enable" to false seems to solve the problem. See bug 579352.
*** Bug 579352 has been marked as a duplicate of this bug. ***
is there any update for when this patch will be included?
The patch got a negative review and it will be not included in any Firefox release. When the next patch gets a positive review it will get checked into the trunk and that's currently FF7.
*** Bug 667005 has been marked as a duplicate of this bug. ***
Mounir, what is the status here?
*** Bug 668534 has been marked as a duplicate of this bug. ***
I investigated this a bit. The behaviors in various browsers are:
Engine | A bubbling click can trigger | A label-generated click can
| multiple <labels> | trigger additional labels
Gecko | Yes | Yes
Webkit | |
/ IE | No | No
Opera | No | Yes
Note that Opera and Webkit agree on Mounir's testcase if you click on the checkbox, but disagree if you click on the text, because of their differences here.
In fact, no other browser propagates a click event beyond the first label it encounters.
So the spec doesn't really say what to do here.
"The label element's exact default presentation and behavior, in particular what its activation behavior might be, if anything, should match the platform's label behavior."
As far as I know, platforms don't really have the concept of "bubbling" events ...
Olli says we should copy the WebKit/IE behavior here.
(In reply to comment #37)
> Olli says we should copy the WebKit/IE behavior here.
except that we're going to let the original click continue to bubble.
Created attachment 546668 [details] [diff] [review]
This is the first half. This patch stops a bubbling click from triggering multiple <label>s. This is enough to fix the hang.
Created attachment 546683 [details] [diff] [review]
Propagate the "I've trigger a label" flag to the synthetic click event.
I'm going to throw this whole thing at try to see if anything depends on our existing behavior.
After applying these two patches we should behave like WebKit and IE except that we will allow the original click event to continue to bubble.
Try run for e094d7112f16 is complete.
Detailed breakdown of the results available here:
Total buildrequests: 163
The behaviors that I describe in the commit message are worth documenting on MDC, I think.
Pressing my luck here, but any chance this could land in Aurora (Fx7) as well? :)
(In reply to comment #44)
> Pressing my luck here, but any chance this could land in Aurora (Fx7) as
> well? :)
Don't think so, sorry :-(
If you wanted to verify that this is fixed on Nightlies, that would be awesome :-)
The NetApp FilerView hang is indeed fixed in the 7/25 nightly build. :) :) :)
Just a note of thanks from both myself and Jake, for working on this, pushing this to the right component and getting it looked at, testing, working on patches etc.