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
[Bug]: PlayCover "Nightly#66" Genshin Impact Crash #358
Comments
Translated Report (Full Report Below)Process: GenshinImpact [2717] Date/Time: 2022-09-18 16:06:47.3053 +0800 Time Awake Since Boot: 10000 seconds System Integrity Protection: enabled Crashed Thread: 0 Dispatch queue: com.apple.main-thread Exception Type: EXC_BAD_ACCESS (SIGSEGV) VM Region Info: 0x100000002 is not in any region. Bytes before following region: 72056830 Thread 0 Crashed:: Dispatch queue: com.apple.main-thread Thread 1:: NIO-ELT-0-#0 Thread 2:: ShaderLoadManagerT Thread 3:: com.apple.uikit.eventfetch-thread Thread 4:: com.apple.NSEventThread Thread 5:: com.apple.NSURLConnectionLoader Thread 6:: GC Finalizer Thread 7:: BatchDeleteObjects Thread 8:: AsyncReadManager Thread 9:: com.apple.coreaudio.AQClient Thread 10:: AMCP Logging Spool Thread 11: Thread 12:: AQConverterThread Thread 13:: UnityGfxDeviceWorker Thread 14:: Worker Thread Thread 15:: Worker Thread Thread 16:: Worker Thread Thread 17:: Worker Thread Thread 18:: Worker Thread Thread 19:: Worker Thread Thread 20:: Worker Thread Thread 21:: Worker Thread Thread 22:: Worker Thread Thread 23:: BackgroundWorker Thread 24:: BackgroundWorker Thread 25:: BackgroundWorker Thread 26:: BackgroundWorker Thread 27:: UnitySubstanceThread Thread 28:: com.apple.CoreMotion.MotionThread Thread 29:: UnityPreload Thread 30:: Worker Thread Thread 31: Thread 32: Thread 33: Thread 34: Thread 35:: UnityMultiRenderingThread Thread 36:: com.apple.audio.IOThread.client Thread 37: Thread 38: Thread 39:: com.apple.CFSocket.private Thread 40: Thread 41:: Timer-Scheduler Thread 42: Thread 43:: MIHOYO_NETWORK Thread 44: Thread 45: Thread 46: Thread 47: Thread 48: Thread 49: Thread 50: Thread 51: Thread 0 crashed with ARM Thread State (64-bit): Binary Images: External Modification Summary: VM Region Summary:
REGION TYPE SIZE COUNT (non-coalesced) Full Report{"app_name":"GenshinImpact","timestamp":"2022-09-18 16:07:02.00 +0800","app_version":"3.0.0","slice_uuid":"7954f6a8-9c16-3d05-9600-70b51cc06fe5","build_version":"426","platform":6,"bundleID":"com.miHoYo.GenshinImpact","share_with_app_devs":0,"is_first_party":0,"bug_type":"309","os_version":"macOS 12.6 (21G115)","incident_id":"C7B77F4F-C751-4634-BE10-7E052BC4CBCC","name":"GenshinImpact"}
], ] Model: MacBookPro18,4, BootROM 7459.141.1, proc 10:8:2 processors, 32 GB, SMC |
How often does this happen? Is there a stable (or probable) way to trigger this? |
It is not a stable way to trigger it, but it is related to "keymapping", and it is related to operating the keyboard & mouse at the same time. When operating the keyboard and rotating the screen with the mouse & clicking the mouse at the same time, there is a greater chance of a delay, which will make the sliding Mouse rotation reduces the response, or causes the app to crash |
I played quite a few hours with Nightly 66, and managed to crash the game this time. It doesn't happen as often here though. |
Please try nightly 85 and see if this issue persists |
nightly 85 This version cannot use the mouse to rotate the screen for 3~4 seconds when the mouse "option key" is switched to the application |
But the game does not crash, correct? If so this specific issue is resolved, that mouse switching issue should be presented in a separate issue. |
Describe the bug
Crash unexpectedly when using the mouse to rotate the app & keyboard operation
Steps to reproduce
Crash unexpectedly when using the mouse to rotate the app & keyboard operation
Expected behaviour
Please fix the mouse rotation delay issue or fix the crash at the same time
Crash log
No response
What version of PlayCover are you using?
Nightly/beta
What version of macOS are you using?
Monterey (macOS 12)
Issue Language
The text was updated successfully, but these errors were encountered: