studio.exe brings computer to a near halt

earthsound · 13th December 2002, 22:32

WinXP, version 5.1 (Build 2600.xpclnt_qfe.010827-1803)
129,328 KB memory
Winamp3, build 488

Note: I have read the Winamp3 FAQs, searched Bugzilla, searched the forums and still haven't found anything related to my problem:

While I was listening to one of the streams I ran across on shoutcast, I was browsing through the results that came up in the listing for genre Pop/Rock->Classic. I accidentally clicked on the link for http://www.madawg.net/ a couple of times instead of the "Tune In!" link, and the computer came to a crawl. I closed the other apps I was running (IE & M$ Access), but it was still crawling. Task Manager took a few *minutes* to come up. I closed Winamp3, but it was still crawling. Under the Task Manager, it showed that Studio.exe was eating up all available CPU cycles. I changed the priority to Low (as low as XP will allow w/o ending it) and the computer became *much* more responsive. Now, when I look @ the Applications tab in Task Manager, I don't see Winamp3 running, but under the Processes tab, Studio.exe is still going, though at "Low" priority. Even at low priority, Studio.exe is eating up 90%+ CPU time even though it is currently using only 608K of memory and only has 4 threads running. Task Manager is showing peak memory usage of 21,292K.

I'm wondering 1) why Studio.exe is acting like such a hog, 2)why Winamp3 has been closed, but Studio.exe is still running & 3)what could be the cause.

I know these questions may not be answered swiftly and exhaustively, but any ideas are most welcome!

sincerely,
david

Neksus · 14th December 2002, 12:51

Maybe more Memory would help you don't have a lot of and also what size is you CPU, if that very small this could happen as well! Also update Windows XP and all drivers always fix a lot of things!
Are you using default options or have you changed something!
The list could be endless!
If nothing of this works please post your total specs so I better can judge you system!!

Dazog · 15th December 2002, 07:00

there has been many memory optomizations made to winamp3 in builds past 488.

Try 491 or wait for the NEXT PUBLIC release.

Since 491 is a internal build..

a preview to see what people think of what's happening inside the
llama

in build 492 minimized to the system Tray winamp uses 5 megs for me in XP.

So thats a big improvement

13th December 2002, 22:32	#1
earthsound Junior Member Join Date: Dec 2000 Location: Southeast US Posts: 15	studio.exe brings computer to a near halt WinXP, version 5.1 (Build 2600.xpclnt_qfe.010827-1803) 129,328 KB memory Winamp3, build 488 Note: I have read the Winamp3 FAQs, searched Bugzilla, searched the forums and still haven't found anything related to my problem: While I was listening to one of the streams I ran across on shoutcast, I was browsing through the results that came up in the listing for genre Pop/Rock->Classic. I accidentally clicked on the link for http://www.madawg.net/ a couple of times instead of the "Tune In!" link, and the computer came to a crawl. I closed the other apps I was running (IE & M$ Access), but it was still crawling. Task Manager took a few minutes to come up. I closed Winamp3, but it was still crawling. Under the Task Manager, it showed that Studio.exe was eating up all available CPU cycles. I changed the priority to Low (as low as XP will allow w/o ending it) and the computer became much more responsive. Now, when I look @ the Applications tab in Task Manager, I don't see Winamp3 running, but under the Processes tab, Studio.exe is still going, though at "Low" priority. Even at low priority, Studio.exe is eating up 90%+ CPU time even though it is currently using only 608K of memory and only has 4 threads running. Task Manager is showing peak memory usage of 21,292K. I'm wondering 1) why Studio.exe is acting like such a hog, 2)why Winamp3 has been closed, but Studio.exe is still running & 3)what could be the cause. I know these questions may not be answered swiftly and exhaustively, but any ideas are most welcome! sincerely, david

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Switch to Linear Mode Hybrid Mode Switch to Threaded Mode

14th December 2002, 12:51	#2
Neksus Senior Member Join Date: Aug 2002 Location: Denmark Posts: 250	Maybe more Memory would help you don't have a lot of and also what size is you CPU, if that very small this could happen as well! Also update Windows XP and all drivers always fix a lot of things! Are you using default options or have you changed something! The list could be endless! If nothing of this works please post your total specs so I better can judge you system!!

15th December 2002, 07:00	#3
Dazog Moderator Alumni Join Date: Jun 2002 Posts: 418	there has been many memory optomizations made to winamp3 in builds past 488. Try 491 or wait for the NEXT PUBLIC release. Since 491 is a internal build.. a preview to see what people think of what's happening inside the llama in build 492 minimized to the system Tray winamp uses 5 megs for me in XP. So thats a big improvement