Search Issue Tracker
Fixed in 2018.3.X
Votes
4
Found in
5.5.4p1
Issue ID
951016
Regression
Yes
Player built on Unity 5.5 crashes when connecting with a profiler from Unity 5.6.0b1 or later versions
How to reproduce:
1. Create a new Unity project with Unity 5.5
2. Go to File --> Build Settings, check Development Build and Autoconnect Profiler
3. Build & Run Player, leave the player running
4. Exit Unity 5.5 and open Unity 5.6.0b1 or any later version (2017.1.0b9 for example)
Expected result: Player should connected to Profiler that is opened with the newer editor version
Actual result: Crash occurs on:
========== OUTPUTING STACK TRACE ==================
ERROR: SymGetSymFromAddr64, GetLastError: 'Attempt to access invalid address.' (Address: 00A0FF36)
0x00A0FF36 (1)
ERROR: SymGetSymFromAddr64, GetLastError: 'Attempt to access invalid address.' (Address: 00A07C2A)
0x00A07C2A (1)
ERROR: SymGetSymFromAddr64, GetLastError: 'Attempt to access invalid address.' (Address: 00A09294)
0x00A09294 (1)
ERROR: SymGetSymFromAddr64, GetLastError: 'Attempt to access invalid address.' (Address: 00A09822)
0x00A09822 (1)
Regression introduced in - 5.6.0b1
Reproducible with 5.5.0a6/5.5.4p3 Built Player while connecting it to Profiler from 5.6.0b1 or later versions
Not reproducible with 5.5.0a6//5.5.4p3 Built Player while connecting it to Profiler from 5.6.0a6
Notes:
1. Reproducible with Standalone (x86) and PS4 development builds, crash did not reproduce with Standalone (x86_64) build
2. Issue only seems to reproduce only on 5.5 built players, could not reproduce with other variations of versions (see "OTHER TESTS" in the Edit notes)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Incorrect Shader keyword activation for Shadows when no Light is present in URP
- Editor freezes when loading a specific AssetBundle
- WebGPU builds with Multithreading enabled crash on Safari
- Set as Value in UI Builder doesn't work across all properties.
- Reorderable ListView inside a ScrollView has a glitchy behavior when trying to reorder items
Add comment