Closed
Bug 199807
Opened 21 years ago
Closed 21 years ago
crashes while moving along some pages (during find or scroll down)
Categories
(SeaMonkey :: UI Design, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: dparsons, Assigned: bugzilla)
References
()
Details
(Keywords: crash)
Attachments
(2 files)
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030319 Debian/1.3-3 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030319 Debian/1.3-3 I get the same problem on the the builg logs listed at http://buildd.debian.org/build.php?pkg=xprint-xprintorg (at least the recent ones dated March 29). I'm tying to find what's gone wrong with building xpawhelloworld. I open up the Find dialog with Ctrl-F, type in xpawhello. The first few entries, relating to setting up the Makefile etc, are OK. But when I'm about to get to the actual build entry (gcc -o xpawhelloworld ...), Mozilla (1.3) just crashes, just like that. It also crashes if I start the search from the bottom of the page, searching backwards. I could previously read the older buildlogs OK, but I've since upgraded to Mozilla 1.3, so I wonder if it's new 1.3 code causing the problems. I'm running on an older laptop (Pentium II, 233MHz) with only 96MB RAM, I don't know if that's relevant. Reproducible: Always Steps to Reproduce: 1. load http://buildd.debian.org/build.php?&pkg=xprint-xprintorg&ver=0.0.8.cvs20030328-1&arch=alpha&file=log 2. Open Find dialog with Ctrl-F 3. Search for xpawhello 4. Keep searching till you would otherwise reach the "gcc =o xpawhelloworld" line, at which point Mozilla completely crashes. Actual Results: Mozilla blinks out of existence, it crashes. Expected Results: Should display the line starting with "gcc -o xpawhelloworld".
Comment 1•21 years ago
|
||
I can't reproduce this crash using 20030302809/win98. This might be related to Bug 174972 (although that seems to happen on the find dialog creation) Reporter, is it possible for you to try this on a mozilla.org nightly from the past few days (ftp.mozilla.org/pub/nightly/)? If you can still reproduce it, this should be in the 'Search' component and have the 'crash' and 'stackwanted' keywords.
Comment 2•21 years ago
|
||
1. load http://buildd.debian.org/build.php?&pkg=xprint-xprintorg&ver=0.0.8.cvs20030328-1&arch=alpha&file=log should be 1. load http://buildd.debian.org/fetch.php?&pkg=xprint-xprintorg&ver=0.0.8.cvs20030328-1&arch=hppa&stamp=1048960092&file=log&as=raw right? the link you gave is a short page.
Keywords: crash
Comment 3•21 years ago
|
||
worksforme with linux trunk 20030328 and 1.3 release. you might try a clean profile. if you don't try out a .mozilla.org build, you'll need to provide a stacktrace with gdb (preferably from a build with symbols) ==> XP Apps/GUI ("Search" is for "Search button, the Search Results Sidebar panel, and Advanced Search")
Assignee: asa → blaker
Component: Browser-General → XP Apps: GUI Features
QA Contact: asa → paw
Comment 4•21 years ago
|
||
>("Search" is for "Search button, the Search Results Sidebar panel, and Advanced
Search")
Oops. Sorry, I suck. I made the mistake of trusting that other similar bugs has
been filed correctly.
I'll try this on linux later on.
Reporter | ||
Comment 5•21 years ago
|
||
Yes, I meant http://buildd.debian.org/fetch.php?&pkg=xprint-xprintorg&ver=0.0.8.cvs20030328-1&arch=alpha&stamp=1048959725&file=log&as=raw for the the test page, sorry for the mess-up. I'll let you know if I'm able to generate a stack trace or if cleaning my profile works. Currently I'm working with the Debian build (1.3-3).
Reporter | ||
Comment 6•21 years ago
|
||
I've since noticed the crashes happen not only during a Ctrl-F search, but also simply by scrolling down other pages, for instance http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=186959. I presume it's the same bug. I've changed the title of this bug report accordingly. It's worth mentioning that other users have reported mozilla1.3 crashes on the Debian Bug Tracking System. I presume again these are related to the bug I'm experiencing. Suggestions there are that the problem is related to fonts (using the libxft2 engine). I couldn't say if it's a C++ ABI problem due to Debian's recent switch to gcc3.2. The Debian bug reports include: #185582: mozilla-browser: mozilla crashes / eats cpu (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=185582) #185952: mozilla-browser: New mozilla crashes reproducibly (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=185952) #185878: mozilla crashes randomly (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=185878) #186126: mozilla random crashes follow up (#185878) (pages, but also simply by scrolling down other pages, for instance http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=186959. I presume it's the same bug. I've changed the title of this bug report accordingly. It's worth mentioning that other users have reported mozilla1.3 crashes on the Debian Bug Tracking System. I presume again these are related to the bug I'm experiencing. Suggestions there are that the problem is related to fonts (using the libxft2 engine). I couldn't say if it's a C++ ABI problem due to Debian's recent switch to gcc3.2. The Debian bug reports include: #185582: mozilla-browser: mozilla crashes / eats cpu (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=185582) #185952: mozilla-browser: New mozilla crashes reproducibly (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=185952) #185878: mozilla crashes randomly (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=185878) #186126: mozilla random crashes follow up (#185878) (pages, but also simply by scrolling down other pages, for instance http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=186959. I presume it's the same bug. I've changed the title of this bug report accordingly. It's worth mentioning that other users have reported mozilla1.3 crashes on the Debian Bug Tracking System. I presume again these are related to the bug I'm experiencing. Suggestions there are that the problem is related to fonts (using the libxft2 engine). I couldn't say if it's a C++ ABI problem due to Debian's recent switch to gcc3.2. The Debian bug reports include: #185582: mozilla-browser: mozilla crashes / eats cpu (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=185582) #185952: mozilla-browser: New mozilla crashes reproducibly (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=185952) #185878: mozilla crashes randomly (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=185878) #186126: mozilla random crashes follow up (#185878) (pages, but also simply by scrolling down other pages, for instance http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=186959. I presume it's the same bug. I've changed the title of this bug report accordingly. It's worth mentioning that other users have reported mozilla1.3 crashes on the Debian Bug Tracking System. I presume again these are related to the bug I'm experiencing. Suggestions there are that the problem is related to fonts (using the libxft2 engine). I couldn't say if it's a C++ ABI problem due to Debian's recent switch to gcc3.2. The Debian bug reports include: #185582: mozilla-browser: mozilla crashes / eats cpu (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=185582) #185952: mozilla-browser: New mozilla crashes reproducibly (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=185952) #185878: mozilla crashes randomly (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=185878) #186126: mozilla random crashes follow up (#185878) (pages, but also simply by scrolling down other pages, for instance http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=186959. I presume it's the same bug. I've changed the title of this bug report accordingly. It's worth mentioning that other users have reported mozilla1.3 crashes on the Debian Bug Tracking System. I presume again these are related to the bug I'm experiencing. Suggestions there are that the problem is related to fonts (using the libxft2 engine). I couldn't say if it's a C++ ABI problem due to Debian's recent switch to gcc3.2. The Debian bug reports include: #185582: mozilla-browser: mozilla crashes / eats cpu (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=185582) #185952: mozilla-browser: New mozilla crashes reproducibly (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=185952) #185878: mozilla crashes randomly (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=185878) #186126: mozilla random crashes follow up (#185878) (pages, but also simply by scrolling down other pages, for instance http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=186959. I presume it's the same bug. I've changed the title of this bug report accordingly. It's worth mentioning that other users have reported mozilla1.3 crashes on the Debian Bug Tracking System. I presume again these are related to the bug I'm experiencing. Suggestions there are that the problem is related to fonts (using the libxft2 engine). I couldn't say if it's a C++ ABI problem due to Debian's recent switch to gcc3.2. The Debian bug reports include: #185582: mozilla-browser: mozilla crashes / eats cpu (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=185582) #185952: mozilla-browser: New mozilla crashes reproducibly (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=185952) #185878: mozilla crashes randomly (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=185878) #186126: mozilla random crashes follow up (#185878) (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=186126) (The full list of Debian bug reports for mozilla is at http://bugs.debian.org/cgi-bin/pkgreport.cgi?which=pkg&data=mozilla-browser&archive=no ) I'll also attach the relevant part of an strace here. Will that be sufficient, or should I strictly give a gdb trace?
Summary: crashes while doing find search on large parge → crashes while moving along some pages (during find or scroll down)
Reporter | ||
Comment 7•21 years ago
|
||
This is the strace output from accessing http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=186959 and trying to scroll down. I've just included the relevant portion leading up to the crash, starting from where the page is accessed. p.s. My apologies for the repeated paragraphs in the preceding comment, I don't know where they came from!
Comment 8•21 years ago
|
||
worksforme with linux trunk/CVS/gtk2/xft the strace only shows a truetype fonts being read and maybe an X Error. stack trace (with mozilla --sync) would be more useful. this could easily be a dupe of 173204
Blocks: xft_triage
Reporter | ||
Comment 9•21 years ago
|
||
Here's the strace output for "mozilla --sync". I've only included the last part of the strace, relating to the crashing page, and gzipped it to save space. --sync also says: The program '<unknown>' received an X Window System error. This probably reflects a bug in the program. The error was 'BadRequest (invalid request code or no such operation)'. (Details: serial 32341 error_code 1 request_code 252 minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.)
Reporter | ||
Comment 10•21 years ago
|
||
I tried running mozilla from a new user (hence, with a freshclean profile), but it crashes in the same way.
Comment 11•21 years ago
|
||
stack trace == from gdb and would show what Mozilla is trying to do system trace == from strace
Reporter | ||
Comment 12•21 years ago
|
||
The default Debian build (now 1.3-4) does not have debugging symbols included, so I can't use gdb right now. I'll report back when I can get a debugging or recent CVS version.
Reporter | ||
Comment 13•21 years ago
|
||
I've now tried the nightly build (2003041322). It does not crash on either of the two urls I've given. On the other hand, the nightly build is made against GTK+1.2, not GTK+2. If the problem is in libxft2 font handling, then it won't occur until the nightly build is made against GTK+2. So the positive test of the nightly build is inconclusive. Are there any other GTK+2/libxft2 builds of recent mozillas, apart from Debian's (which has debugging symbols stripped), that I could test?
Comment 14•21 years ago
|
||
there are RPM builds with gtk2/xft here, but I don't know if you can use the RPMs with Debian. http://download.mozilla.com/pub/mozilla/nightly/experimental/gtk2/ the stack from the Debian won't be incredibly useful, but there are a few known crashes (none of them Mozilla's fault) and the stack (even without symbols) might show itself to be one of those crashes. Other things to look at is if you have any MS .fon fonts or if any of your truetype fonts are not readable.
Comment 15•21 years ago
|
||
ftp://ftp.mozilla.org/pub/mozilla/nightly/experimental/gtk2 has some gtk2 builds, but I don't think that they're debug builds. They also appear to be rpms. There are also xft builds in ftp://ftp.mozilla.org/pub/mozilla/nightly/experimental/xft with the same restrictions. Therefore, my best suggestion is to grab the source and build Mozilla with the correct options set.
Comment 16•21 years ago
|
||
the RPM builds don't have symbols stripped, so a useful (if not detailed) stack can be obtained.
Reporter | ||
Comment 17•21 years ago
|
||
The 20030418 GTK+2 rpm from http://ftp.mozilla.org/pub/mozilla/nightly/experimental/gtk2 does not crash. I guess that implies the bug has been fixed. I'd like to leave the bug open until I can confirm the upcoming Debian builds also work. If they don't, we'll know it's some Debian library problem, not a mozilla problem.
Reporter | ||
Comment 18•21 years ago
|
||
The Debian build of mozilla 1.4 is no longer crashing, so I think this bug can be closed now.
Comment 19•21 years ago
|
||
marking WORKSFORME
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → WORKSFORME
Updated•20 years ago
|
Product: Core → Mozilla Application Suite
You need to log in
before you can comment on or make changes to this bug.
Description
•