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
- Popup windows spawn on the incorrect monitor when the Editor is placed near the boundary of scaled monitor next to a monitor with different scaling
- Hidden Tabs do not shift into empty space after closing visible Tabs
- [Android] Application not deployed on a device when "activity-alias" is used in the AndroidManifest
- Shader compile process adds shader ID to the constant buffer name when the word "Globals" is being used in Vulkan
- Audio Mixer Snapshot link to the documentation isn’t working
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.