Closed
Bug 183021
Opened 22 years ago
Closed 22 years ago
Thrashing (hammering away on) HD when closing window (Ctrl+W)
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
VERIFIED
DUPLICATE
of bug 182842
People
(Reporter: krh, Assigned: asa)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826
Build Identifier: Mozilla 1.2 (uninstalled because of bug)
When I press Ctrl+W to close the current Mozilla window, it starts thrashing
(accesses wildly) the HD wildly for 4-5 seconds and becomes unresponsive during
that time.
Reproducible: Always
Steps to Reproduce:
1. Start up Mozilla on any page with links
2. Right-click on a link and select "Open in new window"
3. Click on "x" to close window, or press Ctrl+W to close it
Actual Results:
Mozilla starts thrashing the HD and becomes unresponsive for 4-5 seconds.
Expected Results:
Just closed the window and continued without any delay, like v1.1 does
I have tried it on 3 different Win2000 machines, and on two of them, the problem
is 100% reproducable. I have tried re-installing v1.1 and confirming that the
problem is gone, then re-installing v1.2 and verified that the problem returns
(on one of the problem machines). The two machines where the problem is have
similar software installed (my home and work development machine), the third one
is a more or less clean Win2000 machine (my test machine).
Both of the machines with the problem has a 900K BOOKMARK file. When I copied
the 900K BOOKMARK file to the machine where the bug wasn't present, it started
exhibiting the same problem.
Comment 1•22 years ago
|
||
*** This bug has been marked as a duplicate of 182842 ***
Severity: blocker → major
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
Comment 2•22 years ago
|
||
v
blocker ? Why should this block development of mozilla ?
Status: RESOLVED → VERIFIED
This can't be bug 101319, which is a year older than the 1.1 release.
But it can't be bug 182842 either, which acclaimedly is NOT on the 1.2 branch:
The cause for bug 182842 is the checking for bug 180423. That fix was checked in
on the trunk on Nov. 21st. At that point the tree was closed for 1.2.
The patch in bug 180423 has no approval for checkin to the branch. And I can't
see anything indicating it was checked in on the branch either? Or was it?
Three other users reported similar bugs with 1.2 however. I dup'ed them against
101319, but i think that's wrong now. The 1.2 bugs are bug 182619, bug 182472,
bug 182435
Reporter | ||
Comment 4•22 years ago
|
||
> blocker ? Why should this block development of mozilla ?
It shouldn't, but it prevents me from testing it (which was one of the two
possible options on the selection I chose), since I use "Open in New Window" a
lot, and it is unacceptable (for me) to be forced to wait 4-5 seconds each time
I close a window. I had to re-install v1.1 to be able to use Mozilla.
Comment 3 is correct. This bug is NOT a dupe of bug 182842 but a dupe of bug
182373. The latter is the disk thrashing bug for the 1.2 branch as reported.
For the cause see this comment
http://bugzilla.mozilla.org/show_bug.cgi?id=182373#c23
Please redupe someone this bug against the correct one.
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•