Closed Bug 27812 Opened 25 years ago Closed 25 years ago

Entering cookie manager sends CPU load to 100%

Categories

(Core :: Networking: Cookies, defect, P3)

x86
Windows NT
defect

Tracking

()

VERIFIED WORKSFORME

People

(Reporter: jhreingold, Assigned: morse)

References

()

Details

When I enter the cookie manager, the CPU load goes to 100%. If I'm able to hit the "cancel" button, the CPU load then returns to normal, but sometimes the CPU is so busy that I can't even do that, so I have to kill the application from the NT task manager. To recreate, Select Advanced/Cookies from the Preferences dialog, then click "View stored cookies". The CPU usage should immediately hit 100%.
Created on Windows NT, Mozilla build 2000020708. Haven't tested it on other platforms.
I'm unable to reproduce. Using a tree from February 13 (because the menus don't work in the tree that I pulled at 5AM this morning) this is working fine. CPU usage was hovering around 1% to 2% before bringing up the cookie viewer and stayed in that same range after I brought up the viewer. Of course there was a spike in cpu usage while the viewer was coming up but that was to be expected. tever, are you seeing this problem?
Status: NEW → ASSIGNED
Target Milestone: M14
Closing this out as works-for-me. Tever, if you are able to reproduce, please reopen the bug. Also, jhreingold, could you verify what you did and make sure you are not misinterpreting some result. I am not seeing such a hogging of resources. If you are pretty sure that what you are seeing is correct, then try to give me some more information and reopen the report.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → WORKSFORME
Re-tested this in the 2000021516 build, and it works fine. Mehaps the 2/7 build was just flakey; that's what I get for running build-of-the-night, I guess (but then I had to do it to verify another bug I'd written up; sigh...) -- Jersey
sorry Steve, I must have missed this one Anyways, worksforme too marking verified: NT 2000022208
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.