All users were logged out of Bugzilla on October 13th, 2018
From Bugzilla Helper: User-Agent: Mozilla/4.74 [en] (WinNT; U) BuildID: 20011001 Well I think the summary is pretty self explanatory. Using said build (as well as 0.94), attempting to read that email caused my X Server to crash. Checking if it was a Mail or general Mozilla problem, I visit the online archive (url provided) with Mozilla, and again, it killed the X server. Finally, to determine if it was a Mozilla problem or an X problem, I visit the asme site using Netscape 4.77 and Konqueror, and nothing went wrong with them. Reproducible: Always Steps to Reproduce: 1.Visiting http://www.geocrawler.com/lists/3/SourceForge/13897/0/6735258/ is enough for me to crash my X Server =( 2. 3. Actual Results: My X Server crashed. Expected Results: Page should be displayed (duh) This additional info may be useful: I'm using linux kernel 2.4.10-xfs, the latest CVS version of XFree86 (from the DRI project), and using KDE 2.2.1 (built from source). The mozilla's were nightly builds, and my distro is Mandrake 8.0
hmm, using 2001.10.03.08-trunk comm bits on linux, i cannot repro this. admittedly, i've a rh 6.2 system, running gnome. akkana, you have kde on a more recent linux system. d'you see this?
michael, is this still a problem for you? ->jag (or akkana), can you repro this? retriage as needed!
Assignee: pchen → jaggernaut
nup. no longer happens =)
Status: UNCONFIRMED → RESOLVED
Last Resolved: 17 years ago
Resolution: --- → WORKSFORME
mass verification of WorksForMe bugs: to find all bugspam pertaining to this, set your search string to "IfItWorksForSlappyTheSquirrelThenItWFM". if you think this particular bug is *still* an open issue, please make sure of the following before reopening: a. that it's still a problem with ***recent trunk builds*** on the all appropriate platform[s] b. provide clear steps to reproduce (unless a good test case is already in the bug report), making sure it pertains to the original problem (avoid morphing as much as possible :)
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.