Closed Bug 161212 Opened 23 years ago Closed 23 years ago

Too many IMG SRC calls will hang mozilla.

Categories

(SeaMonkey :: General, defect)

x86
Linux
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: linux, Assigned: Matti)

References

()

Details

(Keywords: hang)

Too many IMG SRC calls will cause Mozilla to crash. In order to access the URL you need an account at BBR. I was advised by a mod there to post the following instructions: 1. Someone should go to http://www.broadbandreports.com/ and setup an account titled "Bugzilla" 2. Send a private message to the moderator Kevin informing him you are from Mozilla or Bugzilla, and need access to the "Stars Watercooler" he will send you tool points. 3. Go to http://www.broadbandreports.com/prof/new and click the buttons confirming you want premium 4. You can now access the example URL. Please post the account password on this bug report. Sorry about the long process, but site rules prohibit me from setting up the account myself.
Reporter: Which Build ? Can you please use a talkback enabled build and add the talkback ID from that crash into this bug ?
Severity: normal → critical
Keywords: crash
The build is 2002071808 and is talkback enabled, however the talkback feature doesn't seem to activate when it crashes. It causes the browser to crash/freeze and then it normally has to be killed. But even when it crashes all the way, still it doesn't talkback. I double checked and it was talkback, because it has activated talkback on a different crash...
you mean a freeze/hang and no crash ? Talkback can only catch crashes. Is there a flash on that page ?
Can you provide another URL as the one above complains of not being in an active or available forum Can you try a more recent build?
Yeah its more of a freeze/hang.It'll hang, and then I will have to forcefully kill it and it'll then crash. I don't remember it sending a talkback report though. How do I check the talkback IDs in Linux? And as far as not being able to see the message, make sure to follow the instructions for getting an account in my original report. If you'd rather, I'll try to create an HTML page with tons of IMG SRC calls in order to attempt to duplicate the bug again. There was no Flash on the page at all.
you can see submitted talkback IDs by running mozilla/components/talkback/talkback > If you'd rather, I'll try to create an HTML page with tons of IMG SRC calls in > order to attempt to duplicate the bug again. yes, please.
Keywords: crashhang
Tweaking summary, orginal summary was "Too many IMG SRC calls will crash mozilla." Reporter, any idea of the number of img src calls there were? Can try and grab the page source using another browser and add it as an attachment? Is it still happening on a recent build?
Summary: Too many IMG SRC calls will crash mozilla. → Too many IMG SRC calls will hang mozilla.
I wish I could. However the moderators at the message board have put the post in an archive and have been less than helpful as far as getting access to it. Anyways I'm going to create a simple HTML page, and using my copy & paste skills see how many it takes to crash it...
Okay I've created more IMG SRC calls than any sane (and most insane) web designers would use on their page in a test page. I can't get 1.0.1 to crash. Currently using build 2002092619. Must have been a bug in that build. I currently see no reason to leave this bug open. If I encounter the same problem in the future I'll report back.
if this bug still exists on the trunk, then it still needs to be fixed. how many <img> were you testing with? I tested 100000 with trunk build 20021011 and it worked ok (took a bit to load, but didn't hang).
I know that the amount on the webpage that originally caused mozilla to hang was much less than 10,000. I know I tested around 5,000 IMG SRC calls myself and didn't crash Mozilla.
excellent. marking WORKSFORME
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.