Closed
Bug 207964
Opened 22 years ago
Closed 22 years ago
Moving a folder in Bookmarks Manager hangs Firebird
Categories
(Firefox :: Bookmarks & History, defect)
Tracking
()
VERIFIED
DUPLICATE
of bug 207908
People
(Reporter: sipaq, Assigned: p_ch)
References
Details
(Keywords: hang)
Build ID: Mozilla Firebird build from 20030601 running under Windows 2000
Using the current FB nightly after doing a fresh install, Firebird hangs with
100% cpu utilization after trying to move a newly created folder. This has also
been confirmed on Windows NT 4.0 by Axel Schaefer <terraerde@gmx.net> in the
newsgroup de.comm.software.mozilla.browser
Steps to reproduce:
1. Start Firebird
2. Open Bookmarks Manager
3. Create a new empty folder
4. Try dragging that folder
Actual Results:
Firebird becomes unresponsive and has to be killed in the task manager.
Expected Results:
Move the folder
Setting OS -> ALL (since this appears on two different windows platforms),
severity -> critical and adding "hang"-keyword. Putting Erik in CC. Erik can you
please test this.
Comment 1•22 years ago
|
||
*** Bug 207970 has been marked as a duplicate of this bug. ***
Comment 2•22 years ago
|
||
I am seeing this identical behaviour in Mozilla/5.0 (Windows; U; Windows NT 5.1;
en-US; rv:1.5a) Gecko/20030602 under WinXP.
Affects both mozilla and phoenix/mozilla firebird
*** This bug has been marked as a duplicate of 207908 ***
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
Reporter | ||
Comment 4•22 years ago
|
||
Ok, thanks for the dupe. I'm awaiting a fix for bug 207908 and then we'll see
whether this fixes this also on Firebird. I'm a bit sceptical about that, since
Firebird's bookmark code is a complete fork from the seamonkey bookmark code.
Comment 5•22 years ago
|
||
Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4b) Gecko/20030601 Mozilla
Firebird/0.6
I still see this behavior when using the nightly from June 3rd, 2003.
Reporter | ||
Comment 6•22 years ago
|
||
Terry, you are still using the build from 06/01 (take a look at your build ID).
Using the 20030603 build, the problem does no longer occur. So the checkin to
bug 207908 seems to have fixed this.
Marking Verified.
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•