Search Issue Tracker
Not Reproducible
Votes
1
Found in
3.0
Issue ID
441156
Regression
No
Crashes on some Macs in GetCurrentResolution when manipulating monitors
Low frequency issue on mac that has been seen since 3.0 when adding or removing projectors, monitors, going out of sleep and similar transitions.
Call stack shows that the crashes occur at all stages of execution, TickTimer->PlayerLoop, InitializeProject, TickPackageImport.
All of the currently known cases are on Mac.
It should be noted that I've seen this call stack as old crashes on mac's as well. Where the user simply opted not to report the crash, but then makes a manual request, such giving us the call stack.
PS: I've seen many other PC issues that uses the word sleep mode, however the PC is not equally nice to crash in one place. But it raises concern that we're prone to see some sort of regression when this is fixed.
That's why I marked it priority 1, so we get a few beta and RC cycles to verify that there is no regressions.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment