https://bugs.winehq.org/show_bug.cgi?id=53630
Bug ID: 53630 Summary: FoxPro for Windows 21.6a crashes at start with "insufficient memory" error Product: Wine Version: 7.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: JSladek@juno.com Distribution: ---
Created attachment 73029 --> https://bugs.winehq.org/attachment.cgi?id=73029 Startup attempt via Konsole
On startup, FPW crashes with "insufficient memory" error regardless how the app is started, e.g. Konsole with ./FOXPROW.EXE, or FOXPROW.EXE open with Wine Windows Program Loader or by Application Menu command /home/jim_pcl/.wine/drive_c/FPW26/FOXPROW.EXE.
This application worked (with the exception of previously reported bug) with the last installed wine version 7.13 - problem appeared with the update to version 7.16
https://bugs.winehq.org/show_bug.cgi?id=53630
Jim JSladek@juno.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|FoxPro for Windows 21.6a |FoxPro for Windows 2.6a |crashes at start with |crashes at start with |"insufficient memory" error |"insufficient memory" error
https://bugs.winehq.org/show_bug.cgi?id=53630
--- Comment #1 from Jim JSladek@juno.com --- Version 7.18 was just released on the PCLOS repo and it has the same problem reported for version 7.16.
This problem can be duplicated with only the executable FOXPROW.EXE
https://bugs.winehq.org/show_bug.cgi?id=53630
--- Comment #2 from Jim JSladek@juno.com --- Version 7.18 was just released on the PCLOS repo and it has the same problem reported for version 7.16.
This problem can also be duplicated using only the executable FOXPROW.EXE
https://bugs.winehq.org/show_bug.cgi?id=53630
yodelu crinteanu.cristian@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |crinteanu.cristian@gmail.co | |m
--- Comment #3 from yodelu crinteanu.cristian@gmail.com --- Created attachment 73166 --> https://bugs.winehq.org/attachment.cgi?id=73166 right_before_message_window_appear
https://bugs.winehq.org/show_bug.cgi?id=53630
--- Comment #4 from yodelu crinteanu.cristian@gmail.com --- As a note the bug started with wine 7.16 In wine 7.15 that app runs fine...
https://bugs.winehq.org/show_bug.cgi?id=53630
joaopa jeremielapuree@yahoo.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree@yahoo.fr
--- Comment #5 from joaopa jeremielapuree@yahoo.fr --- You should perform a regression test: https://wiki.winehq.org/Regression_Testing
https://bugs.winehq.org/show_bug.cgi?id=53630
Zeb Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |regression, win16 CC| |z.figura12@gmail.com
--- Comment #6 from Zeb Figura z.figura12@gmail.com --- Is the entire +relay log small enough to attach? The attached section is not very informative.
Note that compressing it will help.
https://bugs.winehq.org/show_bug.cgi?id=53630
--- Comment #7 from yodelu crinteanu.cristian@gmail.com --- well that little 16bit app gives a 3GB of log i tailed the big one - somewhere at 88% Anyway, here are the full one https://we.tl/t-t8lP5NNBi5
https://bugs.winehq.org/show_bug.cgi?id=53630
--- Comment #8 from Jim JSladek@juno.com --- Created attachment 73466 --> https://bugs.winehq.org/attachment.cgi?id=73466 Error report when starting WINE after v7.20 update
https://bugs.winehq.org/show_bug.cgi?id=53630
Fabian Maurer dark.shadow4@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- URL| |https://winworldpc.com/down | |load/c3a23335-4f6f-c2a3-11c | |3-a4c2b14b5404 Depends on| |51750 CC| |dark.shadow4@web.de Keywords| |download
--- Comment #9 from Fabian Maurer dark.shadow4@web.de --- I can't test, running into bug 51750. This only affects some systems though.
https://bugs.winehq.org/show_bug.cgi?id=53630
--- Comment #10 from Jim JSladek@juno.com --- I don't know what happened, but my other comments are not posted.
Referring to comment 8, the PCLOS repository only had wine-mono 7.3.0, so I opted to let WINE download and install the wine-mono package that was needed. After that installation, FOXPRO.EXE started running correctly. I checked the WINE installation using my scripted application and everything worked perfectly with the exception of the print function under script operation that was reported in BUG 47933.
https://bugs.winehq.org/show_bug.cgi?id=53630
--- Comment #11 from Fabian Maurer dark.shadow4@web.de --- But FoxPro can't possibly use wine-mono... This is weird.
https://bugs.winehq.org/show_bug.cgi?id=53630
--- Comment #12 from Jim JSladek@juno.com --- Concur. FoxProW was around a long time before .NET. wine-mono had been installed all the way along, but when FoxPro was brought up for the first time after the update to 7.20, the error message came up prompting the installation of wine-mono.
I think I can restore one of my systems to the configurarion before the update to wine 7.20 - I will try to do that tomorrow in konsole to see if any clue to the behavior comes out.
https://bugs.winehq.org/show_bug.cgi?id=53630
--- Comment #13 from Jim JSladek@juno.com --- I checked "wine config about" on a wine 7.19 and the "wine 7.20" installation. "About" is 7.19 on the 7.19 install, but is 7.0.1 on the 7.20 install. I'll confirm that tomorrow, but it appears that wine 7.0.1 stable was put into the repo as wine 7.20 so that it was installable with the normal procedures.
Since the installed wine-mono was 7.3.0, it may not have been compatible with wine stable so that prompted the error message on the initial processing of the "update" to wine stable.
Comments 8-12 are not valid and should be deleted if that is possible. Sorry about the confusion.
https://bugs.winehq.org/show_bug.cgi?id=53630
Fabian Maurer dark.shadow4@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Status|UNCONFIRMED |NEW
--- Comment #14 from Fabian Maurer dark.shadow4@web.de --- Since I can reproduce the issue now I can probably do a bisect (regression test) tomorrow.
Btw, can you please comment in bug 51750 what CPU you have? Still confused that this works at all on your PC.
https://bugs.winehq.org/show_bug.cgi?id=53630
Fabian Maurer dark.shadow4@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|-unknown |win32u CC| |jacek@codeweavers.com Regression SHA1| |e41c255be6ba66d1eec7affe674 | |b8cc7699226b8
--- Comment #15 from Fabian Maurer dark.shadow4@web.de --- Thanks for your info, Jim.
Bisected to
commit e41c255be6ba66d1eec7affe674b8cc7699226b8 Author: Jacek Caban jacek@codeweavers.com Date: Sun Aug 14 23:41:53 2022 +0200
win32u: Use send_message_timeout for WM_CREATE and WM_NCCREATE.
Reverting (and fixing the conflict) fixes the issue.
https://bugs.winehq.org/show_bug.cgi?id=53630
Fabian Maurer dark.shadow4@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |DUPLICATE Status|NEW |RESOLVED
--- Comment #16 from Fabian Maurer dark.shadow4@web.de --- Marking dupe of bug 53568.
*** This bug has been marked as a duplicate of bug 53568 ***
https://bugs.winehq.org/show_bug.cgi?id=53630
Gijs Vermeulen gijsvrm@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #17 from Gijs Vermeulen gijsvrm@gmail.com --- Closing DUPLICATE.