Closed Bug 322232 Opened 20 years ago Closed 20 years ago

Uses all available processor power after it has been running a while

Categories

(Camino Graveyard :: Plug-ins, defect)

PowerPC
macOS
defect
Not set
major

Tracking

(Not tracked)

VERIFIED WORKSFORME

People

(Reporter: knobsturner, Assigned: mikepinkerton)

Details

(Keywords: perf, Whiteboard: [CLOSEME - 1/29])

User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8) Gecko/20051229 Camino/1.0b2 Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8) Gecko/20051229 Camino/1.0b2 When I first start it and go to a few web pages, it runs fast, but after a while, it bogs down. I am a programmer. I ran Sampler on it. It is taking all its time in plugin servicing. This slow behavoir keeps up even when I close all windows cept 1 and have just plain html in that one window. Here is the stack... 1971 Thread_4237 1971 start 1971 start 1971 NSApplicationMain 1971 -[NSApplication run] 1971 dyld_stub_GetPreviousWindow 1968 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] 1968 _DPSNextEvent 1968 BlockUntilNextEventMatchingListInMode 1968 ReceiveNextEventCommon 1963 RunCurrentEventLoopInMode 1963 CFRunLoopRunSpecific 1961 __CFRunLoopRun 1911 __CFRunLoopDoSources0 1911 PL_ProcessPendingEvents 1909 PL_HandleEvent 1909 handleTimerEvent(TimerEventType*) 1885 nsTimerImpl::Fire() 1867 nsPluginInstanceOwner::Notify(nsITimer*) 1845 ns4xPluginInstance::HandleEvent(nsPluginEvent*, int*) 1845 0x7307be0 1845 0x730827c 1835 0x7314430 999 0x73a5a80 831 0x7399a64 828 0x739a2d4 827 0x739999c 826 0x736bc60 545 0x736bfb4 535 0x730e10c 535 0x737db78 534 0x737db78 530 0x737db78 379 0x737db78 357 0x737db78 298 0x737db78 202 0x737db78 152 0x737db78 114 0x737da5c 104 0x737fae8 48 0x73834f4 Reproducible: Always Steps to Reproduce: 1.Run camino on os x 10.4.3 G4 1GB Ram, nothing else running. I have all patches applied as of Jan 3 2006 2. 3. Actual Results: It uses 90% of a G4 with 1 GB of RAM with one page open. Expected Results: It should idle nicely.
Which plugins were on the page? If the page contained a lot of Flash, this is a known bug and is covered in (many) other bugs. If it was Java, it'd be worth having smichaud look at it. Can you direct us to which page (or pages) were causing this?