Closed Bug 218990 Opened 22 years ago Closed 22 years ago

Selecting Boomarks -> File Bookmark... leads to 100% cpu usage and non-responsive browser.

Categories

(SeaMonkey :: Bookmarks & History, defect)

x86
Linux
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: jblanford2, Assigned: p_ch)

References

()

Details

(Keywords: hang)

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5b) Gecko/20030910 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5b) Gecko/20030910 This looks a lot like bug 91782. I still have a mozilla built on 20030903 that doesn't have this problem. I first noticed it on 20030909 with a gtk2 build and tried again on 20030910 with the old reliable gtk-1.2. It also happens with Bookmarks -> Manage Bookmarks... with a slight difference. With File Bookmarks I see only the window title of the bookmark manager. With Manage Bookmarks I see the title and frame, but not the contents. This could be a bad interaction with my window manager. Comparable key sequences work the same as the menu selections. Reproducible: Always Steps to Reproduce: 1. Go to any page, local or remote 2. Select Bookmarks -> File Bookmark... Actual Results: The title bar of the bookmark manager appears, but not the content of the bookmark manager, cpu usage goes to 100% and mozilla stops reponding. Expected Results: The bookmark manager should appear and allow me to select a folder to file the bookmark in. The two builds I have noticed this on were just before and after the 1.5 release branch. My build is very minimal - a browser with xft and crypto. I tested with a new default profile and no extensions or themes.
please try a clean profile. can you grab a stacktrace from gdb? (preferably with symbols)
Severity: normal → critical
Keywords: hang
Sorry, it's a compiler issue. The problem appears only when I use gcc-3.3.2-0pre3, released about Sep 8, 2003 by Debian. With earlier versions of 3.3 or 3.2 this problem does not occur. With the aforementioned gcc-3.3, I can't even build a mozilla with debugging symbols. The compile hangs at libgklayout.so. If you have anything you want me to try, well - mention it and I'll try. I suppose it could be a bug in mozilla exposed by the gcc project's continuing efforts to enforce standards, but I think it's a compiler bug.
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
reopening. FIXED is reserved for bugs fixed by Mozilla patches.
Status: RESOLVED → UNCONFIRMED
Resolution: FIXED → ---
marking INVALID -- this is not a Mozilla bug. gcc hanging trying to link libgklayout.so is definitely a gcc bug.
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago22 years ago
Resolution: --- → INVALID
OK, the problem compiling a debug version was my fault. Once I did get a debug version, the problem went away. So I recompiled readding this line to .mozconfig: ac_add_options --disable-debug and changing nothing else. I rebuilt mozilla and the problem recurred. Here's what I got from gdb: Program received signal SIGINT, Interrupt. [Switching to Thread 65541 (LWP 3306)] 0x400c32b6 in nanosleep () from /lib/libpthread.so.0 (gdb) bt #0 0x400c32b6 in nanosleep () from /lib/libpthread.so.0 #1 0x00000001 in ?? () #2 0x400bf27e in __pthread_timedsuspend_new () from /lib/libpthread.so.0 #3 0x400bbeb2 in pthread_cond_timedwait_relative () from /lib/libpthread.so.0 #4 0x400a02d6 in PR_Unlock () from /usr/src/moz/mozilla/dist/bin/libnspr4.so #5 0x400a0471 in PR_WaitCondVar () from /usr/src/moz/mozilla/dist/bin/libnspr4.so #6 0x4064c4da in TimerThread::Run() () from /usr/src/moz/mozilla/dist/bin/libxpcom.so #7 0x40649640 in nsThread::Main(void*) () from /usr/src/moz/mozilla/dist/bin/libxpcom.so #8 0x400a454e in PR_Select () from /usr/src/moz/mozilla/dist/bin/libnspr4.so #9 0x400bcbf0 in pthread_start_thread () from /lib/libpthread.so.0 #10 0x400bcc6f in pthread_start_thread_event () from /lib/libpthread.so.0 #11 0x40506b07 in clone () from /lib/libc.so.6 I still only get the problem with the most recent Debian gcc-3.3.
Status: RESOLVED → UNCONFIRMED
Resolution: INVALID → ---
We can put this one to rest. It appears to be Debian BTS #210848 in the g++ compiler. At any rate, the problem has disappeared when the exact same source is compiled with g++-3.3.2-0pre4.
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago22 years ago
Resolution: --- → INVALID
I have the same problem: I select Bookmarks -> Manage Bookmarks.. and it hangs and goes to 100% CPU usage. gcc version 3.3.2 20030924 No matter whether I use --disable-debug or not, only --enable-optimize makes a difference for me. If I do not build with -enable-optimize it works, if I do build with -enable-optimize it does not work.
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.