search

latter-bolden / port

A ship runner and manager for Urbit OS
180 stars 12 forks source link

Windows JavaScript error on close #208

Closed tastem-pacper closed 2 years ago

tastem-pacper commented 2 years ago

Bug Description

A JavaScript error occurred in the main process
Uncaught Exception:
TypeError: Object has been destroyed
    at EventEmitter.<anonymous>
(C:\Users\[redacted]\port\app-1.9.0\resources\app\.webpack\main\inde....132027)
    at EventEmitter.emit (note:events:390:28)

To Reproduce Steps to reproduce the behavior:

  1. Open Port
  2. Use it for a while. In my case, I clicked "Check Error" and "Retry" on my local planet. None of my other ships were running.
  3. Close Port
  4. See error. It doesn't pop up every time.

Expected Behavior Port closes without an error popup.

Environment:

Additional context I've seen the popup three times now. Since the first time, my local planet has been Errored, but that might be unrelated (Terminal output below just in case; I've opened a ticket at support@urbit.org). The second and third times were while I was trying to figure out what was going on with my ship.

Terminal output ``` 12:56:43 ~ urbit 1.9 boot: home is C:\[redacted]\Port\piers\planet_tastem-pacper loom: mapped 2048MB lite: arvo formula 11a9e7fe lite: core 38d4ad4d lite: final state 38d4ad4d 12:56:43 loom: mapped 2048MB 12:56:45 boot: protected loom live: loaded: GB/1.578.123.264 12:56:45 boot: installed 351 jets 12:56:45 ---------------- playback starting ---------------- pier: replaying events 2235127-2236186 12:56:45 eyre: canceling ~[//http-server/0vg.2gcuv/76/2] 12:56:45 [%e %authenticated-without-cookie] 12:56:45 [%e %authenticated-without-cookie] 12:56:45 [%e %authenticated-without-cookie] 12:56:45 [%e %authenticated-without-cookie] 12:56:45 [%e %authenticated-without-cookie] 12:56:45 [%e %authenticated-without-cookie] 12:56:45 [%e %authenticated-without-cookie] 12:56:45 [%e %authenticated-without-cookie] 12:56:45 [%e %authenticated-without-cookie] 12:56:46 [%e %authenticated-without-cookie] 12:56:46 [%e %authenticated-without-cookie] 12:56:46 [%e %authenticated-without-cookie] 12:56:46 [%e %authenticated-without-cookie] 12:56:46 [%e %authenticated-without-cookie] 12:56:46 [%e %authenticated-without-cookie] 12:56:46 [%e %authenticated-without-cookie] 12:56:46 [%e %authenticated-without-cookie] 12:56:46 [%e %authenticated-without-cookie] 12:56:46 [%e %authenticated-without-cookie] 12:56:46 [%e %authenticated-without-cookie] 12:56:46 [%e %authenticated-without-cookie] 12:56:46 [%e %authenticated-without-cookie] 12:56:46 [%e %authenticated-without-cookie] 12:56:46 [%e %authenticated-without-cookie] 12:56:46 [%e %authenticated-without-cookie] 12:56:46 [%e %authenticated-without-cookie] 12:56:46 [%e %authenticated-without-cookie] 12:56:46 [%e %authenticated-without-cookie] 12:56:50 pier: serf unexpectedly shut down 12:56:50 newt: write failed end of file ```
latter-bolden commented 2 years ago

Thanks for reporting! We'll have this resolved for the next patch release.

latter-bolden commented 2 years ago

The 1.9.1 update catches a lot of these cases. Let me know if you're still experiencing this after upgrading.