Yes, this looks like that issue. You're test case does show this problem. My test case was taken from a test where I was stressing firefox and my webserver. I experience some 10053 winsock errors after writing large amounts of images to the winsocket. Still don't know why that happens, but when stress testing I saw this behaviour in the netpanel.
The idea of my test is that every image requests 10 frames per second (adjustable). After 100 request, it pauses for 2 seconds and adds another img element. Then it starts requesting at a rate of 10 images per second for the two img elements. This repeates. The test outputs the total average frame rate per number of img elements. You can see a drop in it when adding more img elements. When checking the browser memory status (windows XP), I see a huge increase in firefox. IE and chrome seems to stay more stable. After running the test for a while (on my system with localhost server, somewhere around 10 img elements), all browsers will eventually stop responding and have to be terminated. On 2 feb, 13:35, "Honza (Jan Odvarko)" <[email protected]> wrote: > I think I have simplified the test case to the following: > > <button id="testButton" onclick="onExecuteTest(30)">Execute Test</ > button> > > <div id="content"> > <img id="image1" width="75px"/> > <img id="image2" width="75px"/> > <img id="image3" width="75px"/> > </div> > > <script type="text/javascript"> > function onExecuteTest(counter) > { > if (counter == 0) > return; > > var image = document.getElementById("image" + ((counter %3) + 1)); > image.src = "issue2710.php?noCache=" + new Date().getTime(); > > onExecuteTest(--counter);} > > </script> > > The src attribute is set, but before the request can complete it's > changed again. > > Is that roughly what is happening at:http://mootools.net/shell/wtHtd/4/ > ? > > I think this is related tohttp://code.google.com/p/fbug/issues/detail?id=2710 > > Online here:http://www.janodvarko.cz/firebug/tests/2710/issue2710.html > > Honza > > On Feb 2, 12:49 pm, "Honza (Jan Odvarko)" <[email protected]> wrote: > > > > For examle:http://mootools.net/shell/wtHtd/4/, hit the 'start' > > > button. This loads a lot of images. > > > Yes, I can reproduce it. > > > The problem is that HTTP-ON-EXAMINE-RESPONSE is not fired sometimes > > (looks like a Firefox problem). > > > I don't understand the test case, what is actually happening on the > > page? > > I have noticed that <img> elements are created and the src attribut is > > modified, which executes all the requests. But if I try to simplify > > the test > > I can't reproduce that again. > > > Is that something special about how the images are handled? > > Honza > > > On Feb 1, 9:33 am, woomla <[email protected]> wrote: > > > > When a webpage requests a lot of images, the netpanel shows all > > > requests with spinners. After stopping to request the images, the last > > > line in netpanel will actually show the resulting image. Using > > > fiddler2 at the same time, I see a succes for every request, not only > > > the last one. All images are requested with an unique noCache > > > attribute, so the images are not taken from cache. > > > > Why are the results not shown in the netpanel (why are the lines keep > > > showing the spinner)? > > > > For examle:http://mootools.net/shell/wtHtd/4/, hit the 'start' > > > button. This loads a lot of images. -- You received this message because you are subscribed to the Google Groups "Firebug" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/firebug?hl=en.
