WildCelt
3rd July 2004, 17:03
Hi all,
I have been having a problem with 3.0, and was wondering if anyone else is experiencing it. When I encode something (anything) in 3.0 and shut it down, the program doesn't remove itself from RAM. Sometimes it takes up well over 100MB, and just sits there. If I open up a new instance of the program and encode, it takes up another 100MB chunk. I have to open the task manager and kill them manually.
I wrote Pegasys support for this problem and was given some goofy story about the program being optimized for Intel processors. I am running an Athlon xp 2600+. I can understand optimization, but IMO a program not exiting from RAM when it should is a little more than an "optimization" problem.
Is anyone else experiencing this? Here's the rundown of my PC:
AMD Athlon XP 2600+
512MB PC3200 DDR
Windows XP pro SP2 RC2
I have been having a problem with 3.0, and was wondering if anyone else is experiencing it. When I encode something (anything) in 3.0 and shut it down, the program doesn't remove itself from RAM. Sometimes it takes up well over 100MB, and just sits there. If I open up a new instance of the program and encode, it takes up another 100MB chunk. I have to open the task manager and kill them manually.
I wrote Pegasys support for this problem and was given some goofy story about the program being optimized for Intel processors. I am running an Athlon xp 2600+. I can understand optimization, but IMO a program not exiting from RAM when it should is a little more than an "optimization" problem.
Is anyone else experiencing this? Here's the rundown of my PC:
AMD Athlon XP 2600+
512MB PC3200 DDR
Windows XP pro SP2 RC2