Midi files causes CPU to slow; mozilla process goes to 97% CPU




16 years ago
16 years ago


(Reporter: Brad K., Assigned: rubydoo123)


Windows XP

Firefox Tracking Flags

(Not tracked)





16 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2b) Gecko/20020919
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2b) Gecko/20020919

I experienced a severe loading of my CPU, gradually increasing the load to
saturation, over a period of 2-4 minutes. 

My PC is a 1.6 GHz HP 7955, with 256 MByte memory and 7 GB free of 32 GBytes.


Reproducible: Always

Steps to Reproduce:
1.  Open a new tab; load this *annoying* midi file (Please don't ask why I
grabbed it).  http://www.draftresource.com/midis/getme.mid
2.  Hit the || pause button on the displayed midi tool, or just wait while the
MIDI file plays to the end.

The system slowdown takes a minute or two longer if I don't hit pause, just let
the file play to completion.   

The slowdown resolves immediately when I 'x' delete the tab I opened the MIDI
file in, or just enter a new URL and wait for the system to eventually respond
by loading the new URL.

Actual Results:  
After a minute or two I notice that computer and Mozilla response gets jerky. 
By about 4 minutes the system is next thing to unusable.  The processes list
shows mozilla pulling ~97% CPU.

Expected Results:  
No change in response to mouse, or any slowdown of other applications or
processes, including system response to <ctrl>+<alt>+<del> to invoke the Windows
Task Manager.

I am using the QuickTime 6.0 plugins, npqtplugin2.dll

Comment 1

16 years ago
This may be related to bug 162651, "CPU overloads and does not play MIDI". My
MIDI file played.

Comment 2

16 years ago
using stand alone QuickTime 6.0 on w2k I've got the same result ~100% load, I've
tried several *.mid files,
so this is QT6.0 problem not mozilla.

Comment 3

16 years ago
marking invalid, then
Last Resolved: 16 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.