-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Logos crash with System.AccessViolationException #107
Comments
Notes and ideas (from someone quite new to .NET, so not everything might be correct):
The backtrace indicates that there might be heap corruption going on, but I could not verify this so far via Ideas for further exploration:
|
I do this on GitHub while I gather enough info to open a bug at WineHQ. I was doing that with this issue: ferion11/LogosLinuxInstaller#105 until @jg00dman told me the issue was in wine 64bit having yet to implement error catching. My assumption was that in time Wine devs would fix it. I never found the PR or discussion associated with it. Have you checked Wine's stuff to see if it's known or is that why you are thinking to test the corrupted DB on Windows, to rule things out? Also, here's a link to our reported bugs: https://appdb.winehq.org/objectManager.php?sClass=version&iId=41116 |
See also the attachment at: |
Thanks @thw26 for the pointers! I searched generically for the backtrace, but did not yet look at the Wine bug database in particular. I think that's worth doing. I wanted to test the DBs on Windows to narrow down the problem space (since right now I only know that the exception causes the program to stop, but the real error (i.e. memory corruption) could have been much earlier). This could be very tricky to narrow down without the source code of the program, but I'll try at least :) I think better understanding what the app is trying to load when the exception hits would be a good first step, but I'll need to get to know .NET debuggers first (having never debugged a .NET program before). Regarding database corruption: most databases in Logos seem to be standard sqlite databases, so general file structure of |
Note: this bug is not specific to the installer, but this seems the best place to track it and collect infos on it.
Sometimes Logos can get into a situation where it reproducibly crashes with the following backtrace:
The bug has been present for quite a while (see e.g. the report at https://community.logos.com/forums/t/121.aspx?PageIndex=67 from 2022). I could reproduce it with Logos v10.34 below Wine 9.9 devel and .NET 8 on Ubuntu 22.04.
This bug should be fixed.
The text was updated successfully, but these errors were encountered: