[Bug 46237] New: Far 3.0 x86 crashes starting from build 5288
https://bugs.winehq.org/show_bug.cgi?id=46237 Bug ID: 46237 Summary: Far 3.0 x86 crashes starting from build 5288 Product: Wine Version: 3.21 Hardware: x86-64 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mail(a)chatty.de Created attachment 62934 --> https://bugs.winehq.org/attachment.cgi?id=62934 Build 5287 runs fine. Starting from build 5288 Far 3.0 x86 crashes at startup. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=46237 --- Comment #1 from Chatty <mail(a)chatty.de> --- Created attachment 62935 --> https://bugs.winehq.org/attachment.cgi?id=62935 Starting with build 5288 Far 3.0 x86 crashes. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=46237 Chatty <mail(a)chatty.de> changed: What |Removed |Added ---------------------------------------------------------------------------- URL| |https://farmanager.com/nigh | |tly/Far30b5288.x86.20181021 | |.7z See Also| |https://bugs.winehq.org/sho | |w_bug.cgi?id=46236 --- Comment #2 from Chatty <mail(a)chatty.de> --- https://farmanager.com/nightly/Far30b5287.x86.20181020.7z https://farmanager.com/nightly/Far30b5288.x86.20181021.7z -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=46237 --- Comment #3 from Ken Thomases <ken(a)codeweavers.com> --- I'm not familiar with how the Far Manager folks do things, but nightly builds are typically not even beta quality. They're expected to be unstable. Perhaps it even crashes on Windows. Have you reported the issue to them? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=46237 --- Comment #4 from Chatty <mail(a)chatty.de> --- It does not crash under Windows so it's not up to them. They had a stable build after that (5300) which also fails with the same error. I actually pinpointed the problem to find out where it started. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=46237 --- Comment #5 from Chatty <mail(a)chatty.de> --- I guess the first two commits led to 5288: https://github.com/FarGroup/FarManager/commits/master?after=14ec294518231462... -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=46237 --- Comment #6 from Chatty <mail(a)chatty.de> --- Alex Alabuzhev (author of Far) deducted from the logs the crash comes from "reading / writing /scrolling console buffers" and he's right. Starting "Far.exe /w-" to disable WindowMode not only solves the problem and enables even the latest build (5333) to run, it also makes the UI much more stable - instability spiked when opening the menu (press F9). -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=46237 --- Comment #7 from Chatty <mail(a)chatty.de> --- Still the same behavior with Wine-4.0-rc1. Crash without "/w-", running fine with "/w-". -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=46237 --- Comment #8 from Artem S. Tashkinov <aros(a)gmx.com> --- I guess either this bug or its x86-64 brother (bug 46236) should be marks as a duplicate. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=46237 --- Comment #9 from Artem S. Tashkinov <aros(a)gmx.com> --- (In reply to Ken Thomases from comment #3)
I'm not familiar with how the Far Manager folks do things, but nightly builds are typically not even beta quality. They're expected to be unstable. Perhaps it even crashes on Windows.
Have you reported the issue to them?
Stable builds Far Manager v3.0 build 5300 x86 (2018-10-29) Far Manager v3.0 build 5300 x64 (2018-10-29) also crash. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=46237 --- Comment #10 from Chatty <mail(a)chatty.de> --- Again, this bug is not a duplicate! This bug is due to a code change in Far from build 5287 to 5288 - there are only two commits behind this (see above). A workaround is to start Far with "/w-" - but it ain't the solution. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=46237 --- Comment #11 from Chatty <mail(a)chatty.de> --- I forgot to mention (again), this bug only happens with x86 version. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=46237 --- Comment #12 from Chatty <mail(a)chatty.de> --- Still the same behavior with Wine-4.0-rc4. Crash without "/w-", running fine with "/w-". -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=46237 --- Comment #13 from Artem S. Tashkinov <aros(a)gmx.com> --- (In reply to Chatty from comment #12)
Still the same behavior with Wine-4.0-rc4. Crash without "/w-", running fine with "/w-".
So crashing and not crashing with the same flag? ;-) -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=46237 --- Comment #14 from Chatty <mail(a)chatty.de> --- "wineconsole Far.exe /w-" runs fine. "wineconsole Far.exe" crashes. That's the literal meaning of "with" and "without". -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=46237 --- Comment #15 from Chatty <mail(a)chatty.de> --- No change with 4.0-rc6 -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=46237 --- Comment #16 from Chatty <mail(a)chatty.de> --- This bug is no longer x86 only since evaluating #46236! This bug is due analyzation of https://github.com/FarGroup/FarManager/pull/86 -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=46237 --- Comment #17 from Artem S. Tashkinov <aros(a)gmx.com> --- I can't reproduce this bug in Wine 4.18 and Far Manager Far30b5454.x86.20190823.msi Please retest. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=46237 --- Comment #18 from Artem S. Tashkinov <aros(a)gmx.com> --- Since the original reporter is missing, I guess this bug report might be closed. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=46237 --- Comment #19 from Chatty <mail(a)chatty.de> --- I don't own the affected hardware at the moment. If you want to close it, go ahead. I'll file a new bug if I happen to retest it in the future. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=46237 --- Comment #20 from Artem S. Tashkinov <aros(a)gmx.com> --- This bug has been long solved. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=46237 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #21 from Austin English <austinenglish(a)gmail.com> --- (In reply to Artem S. Tashkinov from comment #20)
This bug has been long solved.
Fixed. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=46237 Alexandre Julliard <julliard(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #22 from Alexandre Julliard <julliard(a)winehq.org> --- Closing bugs fixed in 6.0-rc1. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
participants (2)
-
wine-bugs＠winehq.org -
WineHQ Bugzilla