Search Issue Tracker
By Design
Votes
0
Found in
2018.2.1f1
Issue ID
1102950
Regression
No
[General] UnityEngine.Application.logMessageReceived is not being raised after exiting play mode
How to reproduce:
1. Open attached project "New Unity Project.zip"
2. In Project window, double-click on "Initializer" script
3. In Scripting Editor(tested with Rider and VS) start debugging and then select line13 as a breakpoint
4. In Unity menu select "Repro" -> "Window" and click on "Button" (Scripting Editor opens up highlighting the line13 breakpoint)
5. In Scripting Editor resume the code (on Rider -> "Run To Statement", on Visual Studio -> "Step Over" )
6. In Unity, observe Console window ("Button clicked" is printed)
7. In Unity, enter and leave Play mode
8. Repeat step 4
Expected result: Scripting Editor opens up highlighting the line13 breakpoint
Actual result: while in Edit mode, Scripting Editor does not open up and "Button clicked" is printed immediately (when in Play mode everything works as it should)
Reproducible with: 2017.4.16f1, 2018.2.6f1, 2019.1.0a9
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
- Editor crashes on StoredGraphicsBuffer::GetGfxBufferID when VFX Graph property is modified during Play Mode and Application.targetFrameRate is used to limit FPS
- Crash on NVAPI_Thunk when changing Player resolution while HDR display is used and Direct3D12 is set as the graphics API
- Only one out of multiple cameras is shown in the Play Mode while HDR display is used and Direct3D12 is set as the graphics API
- The "Paste Component as New" option is incorrectly displayed as active despite the action being prohibited
- "TLS Allocator ALLOC_TEMP_TLS" errors are thrown when unsuccessfully importing an FBX file
Resolution Note (2019.1.X):
We can't change this behavior, since Users can depend or added some logic for work around this.
The documentation will get updated to reflect this behavior.