Memory leak like behavior resolved

4cHaOS · 1st January 2012, 05:20

In case anyone else had this problem... Recently, my Winamp 5.623 (clean install) would run at 40% CPU on my quad core Xeon 2.8 box then would crash and require shutdown through the Task Manager. I removed all the plugins and did not have the problem anymore. I then put the plugins back back one by one closing and restarting Winamp until the problem occurred. The culprit was gen_orgler.dll (created December ‎09, ‎2011, ‏‎12:23:32 PM), which I have not put back in the plugins folder. Winamp works like it's supposed to now (without the My Charts functionality, which never worked for me anyway).

timewarptickers · 3rd January 2012, 07:00

I occasionally (okay, rarely, but it's really annoying when it does happen) get this problem on a computer with similar specs. Of course, Winamp's working fine right now, but I just have always wanted to say this: I KNEW it was the Orgler.

Thanks for the information!

1st January 2012, 05:20	#1
4cHaOS Junior Member Join Date: Aug 2004 Posts: 2	Memory leak like behavior resolved In case anyone else had this problem... Recently, my Winamp 5.623 (clean install) would run at 40% CPU on my quad core Xeon 2.8 box then would crash and require shutdown through the Task Manager. I removed all the plugins and did not have the problem anymore. I then put the plugins back back one by one closing and restarting Winamp until the problem occurred. The culprit was gen_orgler.dll (created December ‎09, ‎2011, ‏‎12:23:32 PM), which I have not put back in the plugins folder. Winamp works like it's supposed to now (without the My Charts functionality, which never worked for me anyway).

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

3rd January 2012, 07:00	#2
timewarptickers Junior Member Join Date: May 2011 Location: Jacksonsutt, FL Posts: 23	I occasionally (okay, rarely, but it's really annoying when it does happen) get this problem on a computer with similar specs. Of course, Winamp's working fine right now, but I just have always wanted to say this: I KNEW it was the Orgler. Thanks for the information!