mirror of
https://github.com/PlayCover/PlayCover.git
synced 2026-04-26 16:25:54 +03:00
[GH-ISSUE #580] [Bug]: Genshin Impact crashing #280
Labels
No labels
UI
app-support
bug
bug
documentation
duplicate
enhancement
game-support
good first issue
help wanted / caution
inactive
invalid
macos-beta
pull-request
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/PlayCover#280
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @FlyMeToTheMoonAndLetMePlayAmongTheStars on GitHub (Dec 16, 2022).
Original GitHub issue: https://github.com/PlayCover/PlayCover/issues/580
Describe the bug
Ventura 13.1 (22C65)
Playcover 2.0.0 (177)
Genshin Impact crashes occasionally, can happen during combat or while walking, sometimes even crashes for no apparent reason when my character is standing still in a city and not pressing anything. Hopefully the crash log can help pinpoint the issue?
Steps to reproduce
Hard to reproduce these random crashes, but there is one kind of crash that happens often, which is when I close the game and a crash message pops up immediately after.
Expected behaviour
Not crashing lol
Crash log
click here for full crash log
What version of PlayCover are you using?
2.0.1/build (185)
What version of macOS are you using?
Ventura (macOS 13.1)
Issue Language
@FlyMeToTheMoonAndLetMePlayAmongTheStars commented on GitHub (Dec 19, 2022):
crash log from the game crashing immediately after closing
@FlyMeToTheMoonAndLetMePlayAmongTheStars commented on GitHub (Jan 31, 2023):
crash log from game crashing randomly during open world exploration
@XuYicong commented on GitHub (Jan 31, 2023):
The first crash should be fixed by https://github.com/PlayCover/PlayTools/pull/69. There was some contention in faketouch that wasn't handled correctly.
@TheMoonThatRises commented on GitHub (Feb 22, 2023):
Should be fixed in the nightly builds.