Closed
Bug 57982
Opened 24 years ago
Closed 24 years ago
[crash] dragging thumb in scrollbar causes X crash
Categories
(Core :: XUL, defect, P2)
Tracking
()
RESOLVED
WORKSFORME
mozilla0.8
People
(Reporter: sarnold, Assigned: eric)
References
Details
(Keywords: crash, helpwanted)
Attachments
(1 file)
4.83 KB,
text/plain
|
Details |
Greetings. I am using Debian's Mozilla m18, with Branden's XFree86 4.0.1 .debs on a dual-celeron Linux 2.4.0-test7 computer, with a G400Max dual-head display running Matrox's mga_drv.o to enable the two monitors. Normally the whole system is rock-solid. However, there is one problem. Dragging the scroll thumb with my mouse in mozilla will occasionally cause X to die a horrible death. It is extremely quiet about errors. I *think* the only error message is along the lines of "xinit: connection to server unexpectedly lost". Using the scroll wheel or using the keyboard to scroll has yet to crash X. Dragging scroll bars in other applications has not caused problems -- including aterm and pan (which uses gtk and gdk version 1.2). Thus, I am reporting the bug here. Do you have suggestions on how I can get better output from mozilla when this is happened for further tracing? Since all of X dies pretty quickly, my options are rather limited... :) BTW -- this has happened on many pages, but the most recent can be located here: http://lists.debian.org/debian-devel-announce-0010/msg00007.html Thanks! :)
Comment 1•24 years ago
|
||
sarnold@willamette.edu, thanks for the report and your testing of Mozilla. I have not experienced any crashes like this in recent history but there are a couple fo things that you can do which may help us track down th eproblem. The first is to get a current build http://ftp.mozilla.org/pub/mozilla/nightly/ (look in the MTrunk directories, not the MN6 directories) You'd be surprised at how much has changed since M18. The second thing that might help is to use a Talkback enabled build. Talkback builds generate a report on most crashes and send that report to a server I can access. The report will contain a stack trace that should help us isolate the problem. There are two builds available with Talkback. The first is in the form of mozilla-i686-pc-linux-gnu-installer.tar.gz and the second is mozilla-i686-pc-linux-gnu-sea.tar.gz . The installer-tar.gz is a small download (about 60K). If you use this one then you tar -zxvf it, step into the mozilla-installer directory it creates, ./mozilla-installer and it will launch an installer that allows you to specify the packages that it will grab and install from the webserver. Select Complete or Custom (if you use custom, make sure the TalkBack package is selected). If you use the second option, you get the installer and all of the packages in one download so the process is the same but it doesn't fetch the packages during install. Hopefully the talkback build will catch the crash and give you the option to send in a report. If you post the email address you included in the report or the incidentID of the report I can retrieve a stack trace and attach it to this bug.
After spending much time trying to cause the Oct 25 8:30am build to crash by dragging the main scrollthumb, mozilla finally crashed (signal 11 in the X server) -- by using the scroll thumb in the "browse" window of the "Create new attachment". It crashed pretty hard, and no talkback dialogs came up. Is that the only way a report would be sent back to you guys?
Comment 3•24 years ago
|
||
Over to Toolkit.
Assignee: asa → trudelle
Component: Browser-General → XP Toolkit/Widgets
QA Contact: doronr → jrgm
Comment 4•24 years ago
|
||
->evaughan/future
Assignee: trudelle → evaughan
Target Milestone: --- → Future
Reporting the same thing with 2000112909 linux Steps to reproduce: 1. Go to www.mozillazine.org 2. Click on the Read More link in the build bar 3. Click on the link for bug 61334 4. Drag the thumb down to scroll It crashes. I get no talkback screens. Setting severity to critical as it is a crash Adding me to CC
Severity: normal → critical
Comment 7•24 years ago
|
||
I crash on win32 build 2000112908 when scrolling the following URL: http://www.greyhound.com/scripts/ticketcenter/step2.asp and bug 61334. Changing OS to all
OS: Linux → All
Comment 8•24 years ago
|
||
interesting. the trace is practically identical to what i got in bug 60905 [different steps, and didn't kill X for me while on linux]. also noticed bug 59782, with similar trace [the beginning at least].
Comment 10•24 years ago
|
||
Trudelle: Can you offer a different milestone? Nominating mostfreq, we're getting dupes.
Keywords: mostfreq
Comment 11•24 years ago
|
||
*** Bug 61533 has been marked as a duplicate of this bug. ***
Comment 12•24 years ago
|
||
Note: the stacktrace on this bug occurs in code that was added after this bug was originally reported. However, the crash may be addressed by a patch on bug 61519.
Comment 13•24 years ago
|
||
*** Bug 61534 has been marked as a duplicate of this bug. ***
Comment 14•24 years ago
|
||
*** Bug 61535 has been marked as a duplicate of this bug. ***
Comment 15•24 years ago
|
||
retargeting to moz0.8, whenever that is, and priority P2
Comment 16•24 years ago
|
||
X servers are trusted code and should not crash. If anyone reproduces the X crash (ie your GUI and all apps vanish, the machine locks up or you are left at the login prompt) please report it to XFree or whoever wrote your server. If you are using proprietary drivers (as the reporter was) report it to the vendor. No user application (like Mozilla) should be able to cause this. Still, there does seem to be a Mozilla bug here worth fixing on all platforms.
Comment 17•24 years ago
|
||
*** Bug 61603 has been marked as a duplicate of this bug. ***
Comment 18•24 years ago
|
||
*** Bug 61610 has been marked as a duplicate of this bug. ***
Comment 19•24 years ago
|
||
I don't see this any more with 2000113021 on Linux. Could it have been fixed by the checking to bug 61519?
Assignee | ||
Comment 20•24 years ago
|
||
If this got fixed and someone confirm and close it out?
Comment 21•24 years ago
|
||
suggest this be checked with the following URLs of dupe bugs: http://www.nintendonation.com/main.shtml bug 61533 http://www.xdrive.com/ 61535
Comment 22•24 years ago
|
||
This was fixed by bug 61519, I do believe. (But reopen if this is still happening).
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
Comment 23•24 years ago
|
||
When you say it works for me... does that go for the following two bugs aswell? bug 61533 bug 61535
Updated•24 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•