[Bug 53075] Spitfire Audio App 3.3.23: crashes/freezes after login

WineHQ Bugzilla wine-bugs at winehq.org
Mon Jul 25 13:12:59 CDT 2022


https://bugs.winehq.org/show_bug.cgi?id=53075

--- Comment #6 from sam <nonamedboy at 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.



More information about the wine-bugs mailing list