[Bug 36207] New: Steel Beasts v1.19 demo installer crashes on exit
http://bugs.winehq.org/show_bug.cgi?id=36207 Bug ID: 36207 Summary: Steel Beasts v1.19 demo installer crashes on exit Product: Wine Version: 1.7.5 Hardware: x86 URL: http://www.fileplanet.com/45253/40000/fileinfo/Steel-B easts-Demo-v1.19 OS: Linux Status: NEW Keywords: download, regression Severity: minor Priority: P2 Component: shell32 Assignee: wine-bugs(a)winehq.org Reporter: gyebro69(a)gmail.com CC: julliard(a)winehq.org Regression SHA1: 116e33d50a3435a539bcf7e9b93ab4adbfbecef9 Created attachment 48328 --> http://bugs.winehq.org/attachment.cgi?id=48328 terminal output At the end of the installation when you close the Wine Explorer window showing the installed shortcuts there is a crash, preceded by an
err:heap:validate_block_pointer Heap 0x110000: bad flags 00000001 for in-use arena 0x13b400 error.
Despite of the crash the game is installed correctly. This is the commit that introduced the crash: 116e33d50a3435a539bcf7e9b93ab4adbfbecef9 is the first bad commit commit 116e33d50a3435a539bcf7e9b93ab4adbfbecef9 Author: Alexandre Julliard <julliard(a)winehq.org> Date: Thu Oct 17 18:01:04 2013 +0200 shell32: Delay initialization of the icon cache until needed. :040000 040000 ef0d7553dec7d91788b2ea39482f823f3a1975aa 522d7157e3be8944bb65d8768e2d2883d8f242de M dlls The previous commit (4c6e039aa153aaf3576d52a4106e97bd4d0b1159) results a different backtrace at the end of installation so I couldn't decide which one is the real culprit. Still present in wine-1.7.17-148-g2e5cb7a -- 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=36207 Alexandre Julliard <julliard(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords|regression | Regression SHA1|116e33d50a3435a539bcf7e9b93 | |ab4adbfbecef9 | --- Comment #1 from Alexandre Julliard <julliard(a)winehq.org> --- I can't reproduce it, but it may be fixed by 1dd04884d754427723377a2fed5b58e5ebb6d3b2. Technically not a regression. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=36207 Béla Gyebrószki <gyebro69(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Fixed by SHA1| |1dd04884d754427723377a2fed5 | |b58e5ebb6d3b2 Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #2 from Béla Gyebrószki <gyebro69(a)gmail.com> --- (In reply to Alexandre Julliard from comment #1)
I can't reproduce it, but it may be fixed by 1dd04884d754427723377a2fed5b58e5ebb6d3b2. Technically not a regression.
Now I know what you mean by can't reproduce the bug: it's not always happening, for example rebooting my computer and starting with a new wineprefix sometimes helps avoiding the crash. After some time the bug somehow reappears. I can confirm that latest git version wine-1.7.17-175-gc1bf61e doesn't have the problem, so it is indeed fixed, thank you. -- 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=36207 Alexandre Julliard <julliard(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #3 from Alexandre Julliard <julliard(a)winehq.org> --- Closing bugs fixed in 1.7.18. -- 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 (1)
-
wine-bugs@winehq.org