Closed Bug 81152 Opened 23 years ago Closed 23 years ago

Crash tabbing through links after changing link color

Categories

(SeaMonkey :: General, defect)

x86
Windows 98
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 81860

People

(Reporter: doctor__j, Assigned: asa)

References

()

Details

(Keywords: crash)

From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9+) Gecko/20010515 BuildID: 2001051504 This is a bug I found after I tried to reproduce the bug in Bug 81099. Reproducible: Always Steps to Reproduce: 1. Go to http://www.mozilla.org/ 2. Open Pref menu. Choose Appearance -> Color -> Change colors for unvisited links. 3. Press OK to close Pref menu. 4. Press <Tab> key to cycle through the links. (I pressed and hold on <Tab> key to let it auto-repeat. Actual Results: Crash at around "Bugzilla 2.12 Released" section in Mozilla News column. Expected Results: No crash.
Keywords: crash
I crashed even before that. Using build 2001051604 on Win2k (SP2) I went to prefs to change my visited link color, change it to Red, and hit "Ok". The browser crashed immediately. here's the talkback ID: TB30524889E Jake
Tried this again and got different results more in line with the reporter. Again, I tried changing the unvisited links color to red, the clicked "Ok". Didn't crash here as I had before. However, after that, all the borders at mozilla.org were much bigger and the padding between the text and the borders was very much increased. The unvisited links did become red, though. I then started tabbing through the links, per reporters comments, and it crashed at about the same place the reporter said. The talkback ID on this crash was: TB30525289H Now for some more action. Any time I restart Mozilla and simply click inside the URL address box, Mozilla immediately crashes. This has happened every time I started Mozilla since the last crash (above). The talkback ID on this crash was: TB30525732G This one is pretty bad. I'm going to have to erase my profile in order to be able to use Mozilla now. jake
Weird stuff... I tried using Mozilla again about 1 hour after the time where I was crashing when I was simply placing my cursor into the URL box and it is now not crashing. Not sure why that is??? I tried changing the unvisited link color back to blue. That was successful, but again, I got the behavior where mozilla.org's borders became huge and so did the padding betweent borders and the text. However, after I refreshed the page, all the sizing was back to normal. I then tried the tabbing and that went fine with no crash. Jake
from talkback: xpc3250.dll + 0xa5b2 (0x60b8a5b2) js3250.dll + 0xd38d (0x60c8d38d) js3250.dll + 0xd489 (0x60c8d489) js3250.dll + 0xd31d (0x60c8d31d) xpc3250.dll + 0x1140e (0x60b9140e) xpc3250.dll + 0xf3d3 (0x60b8f3d3) xpc3250.dll + 0xf491 (0x60b8f491) xpc3250.dll + 0xe61e (0x60b8e61e) xpc3250.dll + 0x5e69 (0x60b85e69) xpc3250.dll + 0x5737 (0x60b85737) xpc3250.dll + 0xff49 (0x60b8ff49) xpc3250.dll + 0x12f3b (0x60b92f3b) js3250.dll + 0x18290 (0x60c98290) js3250.dll + 0x18555 (0x60c98555) js3250.dll + 0x243c6 (0x60ca43c6) js3250.dll + 0x1c435 (0x60c9c435) js3250.dll + 0x182ce (0x60c982ce) js3250.dll + 0x18555 (0x60c98555) js3250.dll + 0x4752 (0x60c84752) jsdom.dll + 0x317a (0x6054317a) jsdom.dll + 0x15c2f (0x60555c2f) gkcontent.dll + 0xb6dc8 (0x01e16dc8) gkcontent.dll + 0xb7e0c (0x01e17e0c) gkcontent.dll + 0xe0347 (0x01e40347) gklayout.dll + 0x1fde5 (0x6032fde5) gklayout.dll + 0x7c48e (0x6038c48e) gklayout.dll + 0x7be8b (0x6038be8b) gklayout.dll + 0x62a06 (0x60372a06) gkcontent.dll + 0x8037b (0x01de037b) gkcontent.dll + 0x80531 (0x01de0531) gkwidget.dll + 0x11665 (0x60c41665) appshell.dll + 0x63b3 (0x600a63b3) mozilla.exe + 0x11b8 (0x004011b8) mozilla.exe + 0x2b99 (0x00402b99) KERNEL32.DLL + 0x17d08 (0x77e97d08)
I am seeing the same stack trace as in bug 81860. Marking this one as a dup of that bug since it has more information and a testcase with which to easily reproduce the bug along the lines of the comments of hoju@visi.com 2001-05-16 11:27 below. *** This bug has been marked as a duplicate of 81860 ***
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.