If i launch the autorouter in local mode, the terminal shows the connection open, route and close: \-\-\-\-\-\-\-\-\-\-\-\-\-Connection established\-\-\-\-\-\-\-\-\-\-\- Start routing... Routing \-\-\-\-\-\-\-\-\-\-\-\-\-Connection closed\-\-\-\-\-\-\-\-\-\-\-\-\-\-\- In the browser, the router updates 1 or two lines (if live display is on), then stops doing anything.  The progress window remains at 0% indefinitely.  The problem occurs even on a new pcb with only 5 linear traces. If you press "stop router" and run the route again, it will do exactly the same thing - frozen at 0%. However, this is interesting 1\. if you skip the gnd net\, it will route \- most of the time\.  Of course\, then you have no ground net\. 2\. If you hit "cancel"\, or close the progress window or just run the autorouter again while it is still running\, the autoroute will complete and beneath the completion window will be the error that you "cannot start again before previous activity is stopped" 3\. roughly 1 out of 5 times if you do \#2\, some of the traces will not be visible\.  If you save and reload they appear\. My wildly uninformed theory: Perhaps the connection between chrome and the local autorouter is bunged, and when you run it the second time the routing information that was sitting and waiting actually gets collected by the browser. osx mojave, chrome 79.0.3945.130 (Official Build) (64-bit), autorouter .8.10. I don't know if there is a connection, but i recently upgraded osx, chrome and the autorouter. (chrome and the autorouter to try to fix the problem)