Repository navigation
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Just Cause 2 (JustCause2.exe), thread 1573634430554079352: gameplay access violation reproduced on Box64 0.3.6 and 0.4.2 with BOX64_SHOWSEGV=1 BOX64_SHOWBT=1 BOX64_LOG=1. Latest report terminates at 250 seconds with wowbox64.dll+0x3BB0A0, nested exception frames and no guest address. No contemporaneous memory pressure or thermal throttling. Existing Linux signal diagnostics are not compiled into WOWBox64; the reset handler logs only its pointer at LOG_DEBUG. Add per-exe bounded logging of the original native exception, software signal origin, saved guest EIP/ESP and mapped JIT guest address plus allocation offset before reset/retry. Saved guest state is explicitly labeled as potentially stale. Keep exception policy unchanged and keep the member on Proton 11 arm64ec. This is diagnostic round 1, not a claimed crash fix. Reproduce the same area; inspect WOWBOX64-FAULT and WOWBOX64-EMIT alongside loader addresses to identify ownership and a patchable call site.