I reported earlier that I was getting a lot of error messages out of Wine running Family Tree Maker. As requested I updated to the beta version of Wine, but since doing so nobody has responded with any followup. I now find that after running FTM for a long period of time that Wine hangs up. This suggests to me that there is a memory leak in the beta version. When I terminate the application, by clicking on the window's shutdown icon and instructing the window manager to force the application down, I can no longer start Wine applications. So far the only solution to being able to restart my application is to reboot Linux, which suggests to me that there is some lock that is not being released by the forced termination of the app. Furthermore since upgrading to the beta version of Wine I have lost one significant piece of functionality from FTM: it no longer is able to save text auto-completion information into the database, although all other changes to the database are successful. This aggravates the previous problem because the only way I can retain the auto-completion information is to not shut down FTM for as long as possible. I would request some advice from the Wine gurus as to further steps I can take to collect documentation of these problems. The error log from one run (admittedly not a run that resulted in a hang) is available at www.jamescobban.net/winerrors.txt
On Sat, Sep 5, 2009 at 23:16, jcobban<wineforum-user at winehq.org> wrote:> I now find that after running FTM for a long period of time that Wine hangs up. ?This suggests to me that there is a memory leak in the beta version. ?When I terminate the application, by clicking on the window's shutdown icon and instructing the window manager to force the application down, I can no longer start Wine applications. ?So far the only solution to being able to restart my application is to reboot Linux, which suggests to me that there is some lock that is not being released by the forced termination of the app. >For that part, try wineserver -k on the terminal. Not so sure about the other things.> The error log from one run (admittedly not a run that resulted in a hang) is available at www.jamescobban.net/winerrors.txt >Correct URL: http://www.jamescobban.net/wineerrors.txt
On Sat, Sep 5, 2009 at 23:16, jcobban<wineforum-user at winehq.org> wrote:> Furthermore since upgrading to the beta version of Wine I have lost one significant piece of functionality from FTM: ?it no longer is able to save text auto-completion information into the database, although all other changes to the database are successful. ?This aggravates the previous problem because the only way I can retain the auto-completion information is to not shut down FTM for as long as possible. >My guess would be that the storage related errors shown in the log is related to that.... You shoudl try changing to the program's directory before running it...
On Sat, 2009-09-05 at 16:16 -0500, jcobban wrote:> I now find that after running FTM for a long period of time that Wine > hangs up. This suggests to me that there is a memory leak in the beta > version. When I terminate the application, by clicking on the > window's shutdown icon and instructing the window manager to force the > application down, I can no longer start Wine applications. So far the > only solution to being able to restart my application is to reboot > Linux, which suggests to me that there is some lock that is not being > released by the forced termination of the app. >You may learn something by starting another terminal window and running "top" in it. When that's running, start FTM as usual: if you start it from the console, open a second window and run it there. When top is running, hit 'q' to exit, 'h' for online help or 'u' and type your user name to limit it to showing just your processes. If you are suffering from a memory leak there's a good chance that top will let you see which process is responsible: its memory allocation should grow steadily. Martin