Guppy Posted April 11, 2014 Share Posted April 11, 2014 Steps to reproduce Make sure no instance of firefox is open Press F1 (or select 'help contents' from the help menu ) Read help files Return to editor that is now completely unresponsive close firefox editor is now again Note: my default browser is chrome, if I start firefox before pressing F1 this error never happens. This is because the call "firefox <url>" hands off the url by the master firefox thread and exits gracefully, but if firefox wasn't running the call creates a master firefox thread. Easy solution is to ask the system to background the task "firefox <url> &", even better solution would be to use the users default browser System: Linux Mint 17 ( = Ubuntu 14.04 with cinnamon desktop ) Ubuntu 14.04, AMD HD 6850, i5 2500k Link to comment Share on other sites More sharing options...
Josh Posted April 12, 2014 Share Posted April 12, 2014 Ah, I have seen this before. Thanks for pointing that out. My job is to make tools you love, with the features you want, and performance you can't live without. Link to comment Share on other sites More sharing options...
Recommended Posts