I have a windows application run in a very old machine Pentium 133Mhz 32 Mb RAM (believes this still exist)
The application running fine, but after some hours (3 or 4) the memory and swap are full and the machine run very slowly. I Close the wine and all back to normal
I dont know what are happen with system, but is a very hard trouble to me.
Anybody have any idea to apply in this case
Thanks
Marcelo Welter
"Marcelo" == Marcelo Welter pouback@sysmo.com.br writes:
Marcelo> I have a windows application run in a very old machine Pentium Marcelo> 133Mhz 32 Mb RAM (believes this still exist)
Marcelo> The application running fine, but after some hours (3 or 4) the Marcelo> memory and swap are full and the machine run very slowly. I Marcelo> Close the wine and all back to normal
Marcelo> I dont know what are happen with system, but is a very hard Marcelo> trouble to me.
Marcelo> Anybody have any idea to apply in this case
There is some resource leaking in wine or your program. Does the program run for ours on a sililar machine when running under windows?
The easiest workaround is to close and restart the application from time to time. Is that an option for you?
But also try to find out what resource is leaking, if wine is the culprit.
Bye
A are running "top" to see a estimative of process and i see wine only in this case. (If you have other please speak to me)
Close and reopen is a better idea at this time I thinking in this too but are very strange too final users
thanks for
Em Qui 25 Abr 2002 15:16, Uwe Bonnes escreveu:
"Marcelo" == Marcelo Welter pouback@sysmo.com.br writes:
Marcelo> I have a windows application run in a very old machine
Pentium Marcelo> 133Mhz 32 Mb RAM (believes this still exist)
Marcelo> The application running fine, but after some hours (3 or 4)
the Marcelo> memory and swap are full and the machine run very slowly. I Marcelo> Close the wine and all back to normal
Marcelo> I dont know what are happen with system, but is a very hard Marcelo> trouble to me. Marcelo> Anybody have any idea to apply in this case
There is some resource leaking in wine or your program. Does the program run for ours on a sililar machine when running under windows?
The easiest workaround is to close and restart the application from time to time. Is that an option for you?
But also try to find out what resource is leaking, if wine is the culprit.
Bye
Marcelo, check if this happens due to bug 590: http://bugs.codeweavers.com/show_bug.cgi?id=590
I believe issue 590 happens only when you move mouse arount and does not happen when you don't touch the application.
Andriy Palamarchuk
__________________________________________________ Do You Yahoo!? Yahoo! Games - play chess, backgammon, pool and more http://games.yahoo.com/
In my case i dont use any window managers i call my programs from console with:
xinit wine myapp.exe -- :0
and my mouse is not conected in machine
in the program have a function to remove pointer of screen (set pointer to nul)
well i proceed qith my tests...
Thanks
Marcelo
Em Qui 25 Abr 2002 16:15, vocĂȘ escreceu:
Marcelo, check if this happens due to bug 590: http://bugs.codeweavers.com/show_bug.cgi?id=590
I believe issue 590 happens only when you move mouse arount and does not happen when you don't touch the application.
Andriy Palamarchuk
Do You Yahoo!? Yahoo! Games - play chess, backgammon, pool and more http://games.yahoo.com/
On Thu, Apr 25, 2002 at 06:04:07PM -0300, Marcelo Welter wrote:
In my case i dont use any window managers i call my programs from console with:
xinit wine myapp.exe -- :0
Don't you think you might want to use ttydrv instead ? ;)
BTW, RTFMing helps a lot sometimes...
On Thu, Apr 25, 2002 at 03:03:41PM -0300, Marcelo Welter wrote:
I have a windows application run in a very old machine Pentium 133Mhz 32 Mb RAM (believes this still exist)
The application running fine, but after some hours (3 or 4) the memory and swap are full and the machine run very slowly. I Close the wine and all back to normal
I dont know what are happen with system, but is a very hard trouble to me.
Anybody have any idea to apply in this case
Ah, classical memory leak problem :-)
Unfortunately those are not too easy to find. Try running with something like --debugmsg +relay,+local,+global,+heap,+virtual in order to find out which part of memory gets allocated but not freed any more.
Again, finding such a problem is a bit difficult.
Does that also happen if you don't do anything with that program for 3 or 4 hours ? Or maybe it only happens if you do specific actions in your program ? Try to narrow it down as closely as possible to some specific part.