Problem summary Multiple instances of Modo only launch one crash reporter process. After the first crash, any subsequent crashes on actively running Modo sessions will not generate a crash report.
Customer reported version modo.13.2v1
Customer reported platform ubuntu
Steps to reproduce 1) Open Modo. 2) Open a second instance of Modo. 3) In the command bar, run the following command: debug.crash 4) That session should then crash and present the crash reporter. Select "Don't send." 5) Enter the same command in the other running instance of Modo. Result: Modo will hang, then close without presenting the crash reporter.
Expected behaviour The crash reporter should work for all running instances of Modo, even if one or more of those instances crash.
Actual behaviour The crash reporter will only work for the first crash; any subsequent crashes on an instance that was running prior to the crash will not generate a crash report.
Workaround Unknown.
Reproduced by support This bug has been reproduced in: 13.2v1 - Windows 10, OSX 10.14.6 13.1v1 - Windows 10 13.0v1 - Windows 10 12.2v2 - Windows 10 12.2v1 - Windows 10 12.1v2 - Windows 10 12.0v1 - Windows 10 11.2v3 - Windows 10 11.2v1 - Windows 10 11.1v1 - Windows 10 11.0v3 - Windows 10 10.2v4 - Windows 10, OSX 10.14.6
Earliest version tested 10.2v4 - Windows 10, OSX 10.14.6 - This issue appears to be in all versions of the product