Search Issue Tracker
Not Reproducible
Votes
0
Found in
2018.3.0b7
2018.3.0f2
Issue ID
1112189
Regression
Yes
[2018.3] Crash on RemapPPtrFromCachedOffsets when entering Play mode after "Invalid cached offset" error is thrown
How to reproduce:
1. Open the attached project
2. Open the "Main.unity" scene
3. Enter Play mode
4. Exit Play mode
5. Repeat steps 3-4
Actual result: Unity crashes.
Reproducible with: 2018.3.2f1, 2018.3.0b10, 2018.3.0b7.
Regression introduced in: 2018.3.0b7.
Not reproducible with: 2019.2.0a1, 2019.1.0a14, 2019.1.0a1, 2018.3.0b6.
Notes:
Error "Invalid cached offset" is getting thrown before Editor crashes.
Comments (1)
Add comment
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
BoxxyBrown
Jan 16, 2019 14:08
Even though this appears to have been closed, I want to note that I'm also getting this and really struggling to figure out what's causing it. Sometimes a scene will crash, sometimes it doesn't; also something interesting is, if I open another scene - and then try to open the scene that crashes, sometimes it won't crash when opening. I assume it's a prefab that's located in both scenes, but for some reason one of the scenes won't crash when opening.