[Bug 53075] New: Spitfire Audio App 3.3.23: crashes/freezes after login
https://bugs.winehq.org/show_bug.cgi?id=53075 Bug ID: 53075 Summary: Spitfire Audio App 3.3.23: crashes/freezes after login Product: Wine Version: 7.9 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: nonamedboy(a)outlook.com Distribution: --- Created attachment 72495 --> https://bugs.winehq.org/attachment.cgi?id=72495 Archive containing logs and a screenshot System information ------------------ Distribution : Kubuntu 22.04 LTS Kernel : 5.15.0-30-generic Architecture : x86_64 CPU : Intel Core i7-12700F Wine version : wine-7.9 / 7.9~jammy-1 Wine package name : wine-devel Wine package source : https://dl.winehq.org/wine-builds/ubuntu/dists/jammy/winehq-jammy.sources Installed programs : * Microsoft Visual C++ 2015-2019 Redistributable (x64) - 14.29.30139 [installed by Spitfire Audio] * Spitfire Audio version 3.3.23 * Wine Mono Runtime 7.2.0 * Wine Mono Windows Support 7.2.0 Changed Settings : Wine Windows version (7, 8, 8.1, 10) Application information ----------------------- Application : Spitfire Audio App Application version : 3.3.23 Official URL : https://www.spitfireaudio.com/library-manager/download/win/ Archive.org URL : https://web.archive.org/web/20220524211003/https://d1t3zg51rvnesz.cloudfront... AppDB URL : https://appdb.winehq.org/objectManager.php?sClass=application&iId=19759 Installation path : "~/.wine/drive_c/Program Files/Spitfire Audio/" Installer file name : SpitfireAudio-Win-3.3.23.exe Installer SHA1 : cf91f0ff1a60a3b0584b8587b78105100eb0b4d0 Executable file name: Spitfire Audio.exe Executable SHA1 : b5370fb6fbf3926d48dfee23817e043ff35a4f72 Bug information --------------- Type of bug : crash/freeze; could be regression - AppDB indicates a silver rating with 7.2-staging Symptom : the application does either crash or not respond (seems to be random) and has to be terminated forcefully Condition : during startup, after login Last error message : 01b4:err:sync:RtlpWaitForCriticalSection section 00000000002300C8 "dlls/ntdll/heap.c: main process heap section" wait timed out in thread 01b4, blocked by 0100, retrying (60 sec) Steps to reproduce the bug -------------------------- 0. Reset the default wine prefix 1. Install the Spitfire Audio App in the default wine prefix 2. Open Terminal here: "~/.wine/drive_c/Program\ Files/Spitfire\ Audio/" 3. Run Spitfire Audio.exe: "wine Spitfire\ Audio.exe" 4. Click on "DECLINE" when asked about data collection 5. Enter username and password (free account needed) 6. Click on "LOGIN" 7. You will see the loading screen (circle shaped bar) fill to about 50%-100%, then the application will either crash or not respond Attachments ----------- wine_bug_report_spitfire.zip: - app_log.txt : contains the logs created by Spitfire Audio App - bug_info.txt : contains this description - Screenshot_20220524_225202.png: a screenshot of the frozen Spitfire Audio App - wine_log.txt : contains the logs created by wine Checklist --------- - bug writing guidelines : checked - most frequently reported bugs : no match found - known issues : may be related to https://bugs.winehq.org/show_bug.cgi?id=31882 - regression test : N/A -- 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=53075 Ken Sharp <imwellcushtymelike(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- URL| |https://www.spitfireaudio.c | |om/library-manager/download | |/win/ Keywords| |download Distribution|--- |Ubuntu -- 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=53075 --- Comment #1 from sam <nonamedboy(a)outlook.com> --- UPDATE: bug is present in wine-7.10 -- 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=53075 --- Comment #2 from sam <nonamedboy(a)outlook.com> --- UPDATE: bug is present using wine-7.11 and wine-7.12 It appears that if you try to run the application often enough there will be a small chance of it eventually starting up and running normally. You are then able to install any library from within the application. The installed VST should work without major problems afterwards. If you want to uninstall, reinstall, update or remove an existing library or install a new library at a later point (i.e. after the application has been closed or the system has been rebooted) you need to get lucky again. -- 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=53075 George Hilliard <thirtythreeforty(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |thirtythreeforty(a)gmail.com --- Comment #3 from George Hilliard <thirtythreeforty(a)gmail.com> --- Also experiencing this on Wine 7.12. -- 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=53075 sam <nonamedboy(a)outlook.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |NOTOURBUG --- Comment #4 from sam <nonamedboy(a)outlook.com> --- UPDATE: after updating the app to the recently released version 3.3.25 the issue seems to be resolved It seems that the update changed the behavior of the app in a way that does not trigger deadlocks or crashes with wine anymore (wine-7.12 and wine-7.13 working well now). Unfortunately, neither does Spitfire provide any change logs nor is it possible to use an outdated version of the app; no further testing with version 3.3.23 can be done. The root cause of this bug may be still existing within wine (it may have been the apps fault all along although version 3.3.23 worked fine on my Windows machine) but without a way to perform further tests I have to mark this bug as resolved for now. As the issue has been resolved by updating the app I will update the status to "RESOLVED, NOTOURBUG". -- 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=53075 --- Comment #5 from George Hilliard <thirtythreeforty(a)gmail.com> --- (In reply to sam from comment #4)
UPDATE: after updating the app to the recently released version 3.3.25 the issue seems to be resolved
Thanks for looking. In my case, version 3.3.25 appears to still have the issue. Is there a way I can help you reproduce it? -- 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=53075 --- Comment #6 from sam <nonamedboy(a)outlook.com> --- (In reply to George Hilliard from comment #5)
(In reply to sam from comment #4)
UPDATE: after updating the app to the recently released version 3.3.25 the issue seems to be resolved
Thanks for looking. In my case, version 3.3.25 appears to still have the issue. Is there a way I can help you reproduce it?
In that case I don't know what to do. The app does not let you use it without internet connection and with connection it will prompt you to update if you are not on the latest version. Without reverse engineering or debugging (which I currently do not have time for) I don't think one will be able to force the app on an outdated version to start up. Even if I managed to get version 3.3.23 running again to reproduce the error, I'm afraid, there is probably not much at this time I could do about solving the issue. I could re-open the bug but I could not do tests anymore as the problem disappeared on my system with version 3.3.25. You could create another bug for version 3.3.25 although it would be ridiculous to create new bug for each new version of the app. Did you check your logs/stdout/stderr and made sure that you get the same error as I did? Reading the log I uploaded I assume that a stack overflow occurs in thread 0100 (the main thread, probably in a critical section) which basically causes all other threads to deadlock as they wait for thread 0100 to release the critical section. This in turn causes the whole app to freeze. Usually the stack size of the main thread is handled by the OS API (in this case WINE) as the process gets created. If my assumption is correct, one should be able to "fix" this by increasing the stack size, although I have no clue how to go about this. And if this is in fact the cause I still don't know why this is only a problem using WINE and not Windows (except maybe WINE not using the same default stack size as Windows or WINE using the stack too extensively during API calls). Or why it suddenly works on my system but not on yours. -- 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)
-
WineHQ Bugzilla