Closed Bug 190296 Opened 22 years ago Closed 22 years ago

Crash while viewing webpage with errors (width"500")

Categories

(SeaMonkey :: General, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 190079

People

(Reporter: mcchambers, Assigned: asa)

References

()

Details

(Keywords: crash, stackwanted)

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3b) Gecko/20030122 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3b) Gecko/20030122 I was in my xhtml design class developing webpages, and viewing them with Mozilla. After making a revision to the code, I noticed that for some reason Mozilla crashed everytime I tried to view it. It took me while to figure out, but I made an error in my code (img width to be 500, left out the = assignment) This error in the code was the cause of the crash. Reproducible: Always Steps to Reproduce: 1. Attempt to view the webpage Actual Results: Crash Expected Results: View webpage and some how try to render the image Since then, I have corrected the error and now Mozilla works beautifully. I just thought I send this bug to you guys to see if you want to find a way to fix it or just leave it as is.
wfm with a 5h old cvs trunk. Have you changed your page ? if yes: Can you change it back with the broken image src ?
can you also post Talkback ID for this crash ? "mozilla/bin/components/talkback/talkback.exe"
Keywords: crash, stackwanted
Looks like a dup of bug 190079
Just tried it at home using Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3b) Gecko/20030120 and everything seems to work. Guess it was just a build bug. But I'm not too sure if its dupe of 190079, because I have no clue what that means ;) You decide to mark as WFM or Dupe
This should be fixed in today's build, if not, please reopen this bug report. *** This bug has been marked as a duplicate of 190079 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.