Search Issue Tracker

Fixed in 2021.1.X

Fixed in 2020.2.X, 2020.3.X



Found in



Issue ID




[macOS] BugReporter doesn't get invoked when the project crashes

Progressive Lightmapper


The fix requires building OpenRL from source on Mac. It's a bigger task and is tracked here:


How to reproduce:
1. Download the tester-attached script(Crasher.cs)
2. Create a new Unity project
3. Import the downloaded script
4. Select the Do > Crash option from the menu bar

Expected result: the Editor crashes, Bug Reporter window appears
Actual result: the Editor crashes, Bug Reporter window does not appear

Reproducible with: 2019.3.0b2, 2019.3.1f1, 2020.1.0a2, 2020.1.0a24
Not reproducible with: 2019.3.0b1, 2019.3.2f1, 2020.1.0a1
Could not test with: 2017.4.37f1(script used for testing is incompatible), 2018.4.17f1(BugReporter does not pop-up at all, regardless of whether it is a new or existing project)

Opening the same project and repeating step 4 will not cause this issue and the Bug Reporter will pop-up
If a new project is created, the script is imported, the project is exited, then opened again and step 4 is repeated, no bug reporter will pop-up

  1. Resolution Note (fix version 2021.1):

    Fixed in 2021.2.0a5

  2. Resolution Note (fix version 2021.1):

    Fixed in 2021.1.0b9

  3. Resolution Note (fix version 2020.3):

    Fixed in 2020.3.27f1

  4. Resolution Note (fix version 2020.2):

    Fixed in 2020.2.7f1

Comments (5)

  1. bfoddy

    Nov 10, 2020 16:00

    If it turns out to be really hard to fix, as is implied by the broken jira link above, then you should disable the line of code that launches the debugger on MacOS until it is fixed. Otherwise you're just making life miserable for thousands of mac developers for no reason.

  2. MagicMiikka

    Sep 11, 2020 05:56

    Workaround: when "Unity" is asking for permission to open debugging tools (asks password) force close the app.

    This way the unity can be force quitted and you do not need to restart the computer.
    I have not checked if there is something on the bg still running but at least the app is quitted visually.

  3. bfoddy

    Jul 09, 2020 01:05

    Now July and still broken. It's ok though, I just switched to developing on Windows, now the issue is resolved for me

  4. bfoddy

    May 07, 2020 02:12

    Now 13 versions layer, still listed under “known issues”. Really? It’s a regression!

  5. bfoddy

    Apr 11, 2020 00:52

    This one should be considered urgent because it prevents the Unity process from ever being killed. You can't force-quit it, you can't kill it from Finder, and it prevents new instances of Unity from being opened. So you have to reboot the damned computer.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.