[Bug 54420] New: preloader warning "failed to reserve range" macOS Ventura
https://bugs.winehq.org/show_bug.cgi?id=54420 Bug ID: 54420 Summary: preloader warning "failed to reserve range" macOS Ventura Product: Wine Version: 8.0 Hardware: x86-64 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: gcenx83(a)gmail.com CC: bshanks(a)codeweavers.com The usual Apple made changes that affects macOS Ventura preloader: Warning: failed to reserve range 0000000000010000-0000000000110000 -- 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=54420 --- Comment #1 from Brendan Shanks <bshanks(a)codeweavers.com> --- Yep, dyld (at least on Ventura, didn't test Monterey) allocates private memory in that region very early, before any part of the preloader runs. A zero-fill section does succeed in reserving this memory, but the dyld allocations start right after, so picking the size would be tricky. Once wow64 is working upstream there will likely be other memory reservation changes needed, we can revisit this then. (We know of an EXE with an image base of 0x10000 that fails to run on Ventura, but does work when a zerofill is used to reserve it, so that's promising). ==== regions for process 61077 (non-writable and writable regions are interleaved) REGION TYPE START - END [ VSIZE RSDNT DIRTY SWAP] PRT/MAX SHRMOD PURGE REGION DETAIL dyld private memory 1000-41000 [ 256K 48K 48K 0K] rw-/rwx SM=PRV dyld private memory 41000-81000 [ 256K 16K 16K 0K] rw-/rwx SM=PRV -- 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=54420 --- Comment #2 from Gcenx <gcenx83(a)gmail.com> --- (In reply to Brendan Shanks from comment #1)
Yep, dyld (at least on Ventura, didn't test Monterey) allocates private memory in that region very early, before any part of the preloader runs.
A zero-fill section does succeed in reserving this memory, but the dyld allocations start right after, so picking the size would be tricky.
So there it could still be worked around it’s just going to be a PITA Unless something changed in a later macOS Monterey security patch preloader didn’t complain this started the moment I’d upgraded to Ventura.
Once wow64 is working upstream there will likely be other memory reservation changes needed, we can revisit this then.
Yep it’s rather unfortunate that WoW64 isn’t working at all currently not even generating a full wineprefix this will endup causing more bug reports since it’s enabled by default, I’d already created one https://bugs.winehq.org/show_bug.cgi?id=54367
(We know of an EXE with an image base of 0x10000 that fails to run on Ventura, but does work when a zerofill is used to reserve it, so that's promising).
Could you disclose what exe is affected by this? -- 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=54420 Gcenx <gcenx83(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.winehq.org/sho | |w_bug.cgi?id=54367 -- 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=54420 --- Comment #3 from Gcenx <gcenx83(a)gmail.com> --- This was resolved by the commits in https://gitlab.winehq.org/wine/wine/-/merge_requests/2329 -- 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=54420 --- Comment #4 from Jactry Zeng <jactry92(a)gmail.com> --- (In reply to Gcenx from comment #3)
This was resolved by the commits in https://gitlab.winehq.org/wine/wine/-/merge_requests/2329
So is this bug considered fixed? -- 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=54420 --- Comment #5 from Brendan Shanks <bshanks(a)codeweavers.com> --- Yes, this was fixed by cfa0dd9dd91eea0e401347ba41141b9c0c23131d (part of https://gitlab.winehq.org/wine/wine/-/merge_requests/3349) -- 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=54420 Jactry Zeng <jactry92(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED Fixed by SHA1| |cfa0dd9dd91eea0e401347ba411 | |41b9c0c23131d --- Comment #6 from Jactry Zeng <jactry92(a)gmail.com> --- Thanks. Mark as FIXED. -- 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=54420 Alexandre Julliard <julliard(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #7 from Alexandre Julliard <julliard(a)winehq.org> --- Closing bugs fixed in 8.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)
-
WineHQ Bugzilla