Closed Bug 22630 Opened 26 years ago Closed 26 years ago

CPU usage shoots to 100% when URL is entered

Categories

(SeaMonkey :: General, defect, P3)

x86
Windows NT

Tracking

(Not tracked)

VERIFIED WORKSFORME

People

(Reporter: biswapesh_chatterjee, Unassigned)

Details

(Keywords: perf)

System: Build 1999122308 on WinNT4 (SP 5) PII 400 with 64 MB RAM. Overview: CPU usage shoots to 100% for around 30 secs or so when you click on the URL bar and press <Enter> after entering a new URL after starting up mozilla for the first time. Test Case: Open Mozilla. Click on URL bar. Type a URL and press <Enter>. Actual Result: CPU usage shoots to 100% and stays there for about 30 secs. The icon on the right freezes as well. No message on the console. Expected Result: The URL should be loaded immediately. Other Info: This only happens with the first URL. Subsequent URLs get loaded OK.
Does it matter what URL you use? Could you get a stack trace for what mozilla is doing while it's at 100% CPU? This sounds similar to a Linux bug relating to font loading - do you have any unusually large fonts installed on your system?
I don't have a development build - nor VC++. So I can't get a stack trace unless the program crashes. I tried to attach the standard NT debugger to the program and it crashed immediately without generating any stack trace. Can you tell me how to get a stack trace - sorry if I sound too ignorant. And no, I don't have any non-standard fonts installed in my system.
Summary: [PERFORMANCE] CPU usage shoots to 100% when URL is entered → [PERF] CPU usage shoots to 100% when URL is entered
Changing [PERFORMANCE] to [PERF].
Keywords: perf
Summary: [PERF] CPU usage shoots to 100% when URL is entered → CPU usage shoots to 100% when URL is entered
is this still happening? i'm certainly not seeing it...
Status: NEW → RESOLVED
Closed: 26 years ago
Resolution: --- → WORKSFORME
Nops, it went away after I deleted by profile and mozregistry.dat - checked in yesterday's build. Marking this VERIFIED.
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.