Resource leak bug in Xmpeg 4.2a

[peltsi]

Hasn't anyone else encountered this or what's the problem?
Nothing seems to be done to fix this! I mean, while encoding
Xmpeg slowly eats all the system resources percent by percent,
until there are 0% resources left and system (WinME) turns
pretty unusable. System resources are freed by closing Xmpeg.
Same problem anyone? No? Unbelieveable.

Resources are slowly wasted even by changing options and
settings! Bug can't be so hidden either, because I got it
"working" on my friend's computer also (Win98SE) at first try.

Please, fix this at once. It pisses me off.

[vcespon]

I found the same problem using Xmpeg 4.2a in Windows Millennium. When you are configuring the program to do a conversion, the resources fall very fast, until you get close to 0 in user and system resources.

Once it starts compressing they fall to 0 after a few seconds and the icons, menus, comboboxes, etc aren't draw well, all the fonts return to system default font, start menu doesn't appear, etc.

This lets the computer unusable while compressing, althoug the conversion is done well and at the usual speed.

I appreciate the effort of the people that continued the work in FlaskMPEG, but it seems clear that they developed Xmpeg in Windows 2000 or XP, where the amount of resources is much greater, because in Windows Millenium the resource leak is OBVIOUS.

[Migsan76]

Strange.....


Now i use WinXP, but some time ago i used XMpeg under WinMe several times to make encodings, with other aplications open like word, excel,Acess... and the system resources never go down.

Maybe a problem of the processor or Memory? Whats yor Processor?

[vcespon]

No, It's a problem specific to Xmepg or more probably the installation of the codecs. I've been reading the rest of the posts and it seems that people are having all sorts of problems depending on which codecs you have installed and in which order.

Tonight I'm going to remove the Radium MP3 Codec and install it again, as it was the solution for many people.

Just for the record, I'm using a Tualatin 1266 with 512 Mb of SDRAM, and all other operating systems and applications run fine. I mean, it passes every test I can think of. The resources were at about 80% before starting to fiddle with Xmpeg, and about 70% after closing it.

[chipzoller]

Well first of all, you must understand that Windows ME is a toy operating system. Even Microsoft says so!

So don't be surprised when you get what you payed for.

I have spoken to the author of Xmpeg and it was developed in an NT kernal.

Win9x just isn't an optimal operating system.

Get Windows 2000 Professional. Its the best MS operating system out there.




chip

[fewtch]

Originally posted by chipzoller
Well first of all, you must understand that Windows ME is a toy operating system. Even Microsoft says so!

So don't be surprised when you get what you payed for.

I have spoken to the author of Xmpeg and it was developed in an NT kernal.

Win9x just isn't an optimal operating system.
That's hardly the point. Nobody is gonna change OS just to use a single shit-written program.

Lets face it, if an app isn't compatible with Win9x it should say so... but I doubt that's it, it sounds like a serious bug in XMpeg (it would suck up resources under Win2K or XP too, but not cause the same problems).

If they don't want to fix it that's fine, but just commenting...