Search Issue Tracker
Fixed in 5.4.0
Votes
0
Found in
5.4.0b5
Issue ID
769451
Regression
No
Connecting profiler rometly with different versions results in crash
To reproduce this case you are going to need:
1. Local network
2. Two PC machines
ProjectSteps:
1. Create Project on 5.3 with computer A
2. Build it as standaloneplayer with computer A
4. Run it
5. Open unity 5.4 with computer B
6. Profile computers A player
7. Crash
0x00000001415E9D40 (Unity) memcpy
0x00000001405080C1 (Unity) ReadArray<char>
0x000000014050A25D (Unity) ProfilerFrameData::Deserialize
0x000000014050B0CE (Unity) UnityProfiler::DeserializeFrameData
0x00000001404FE23B (Unity) ProfilerConnection::HandleProfilerDataMessage
0x00000001404E9E55 (Unity) GeneralConnection::Poll
0x00000001404ECE6E (Unity) EditorConnection::PollWithCustomMessage
0x0000000140BE5927 (Unity) Application::TickTimer
0x0000000140E1CA3C (Unity) FindMonoBinaryToUse
0x0000000140E1E078 (Unity) WinMain
0x00000001415FCD14 (Unity) read
0x00007FFED29E2D92 (KERNEL32) BaseThreadInitThunk
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment