[COMPASS-3118] Object has been destroyed after closing connect window during startup Created: 07/Sep/18  Updated: 29/Oct/23  Resolved: 26/Sep/18

Status: Closed
Project: Compass
Component/s: None
Affects Version/s: 1.15.1
Fix Version/s: 1.16.0-beta.7, 1.15.4

Type: Bug Priority: Critical - P2
Reporter: Brian Blevins Assignee: Lucas Hrabovsky (Inactive)
Resolution: Fixed Votes: 3
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Windows, Linux, MacOSX


Attachments: PNG File beta8.png     PNG File image-2018-09-07-18-10-11-245.png    
Issue Links:
Duplicate
is duplicated by COMPASS-3101 Compass - continuing process "Mongo C... Closed
is duplicated by COMPASS-3124 Compass 1.15 Keeps Crashing Closed
Related
related to COMPASS-3101 Compass - continuing process "Mongo C... Closed
related to COMPASS-3124 Compass 1.15 Keeps Crashing Closed
is related to NODE-1165 Compass - JavaScript error at startup... Closed
Sprint: Iteration Mango Miso

 Description   

If the Compass user closes the connection window during startup (before the input fields render) using the OS window "X" or red dot, the Compass server process is left running. This prevents subsequent Compass launch attempts due to IPC issues.

The problem has been reported on all three platforms. On MacOSX, the dialog contains the following text.

A JavaScript error occurred in the main process

Uncaught Exception:
 Error: Object has been destroyed
 at ipc.respondTo (/Applications/MongoDB Compass.app/Contents/Resources/app.asar/src/main/window-manager.js:154:20)
 at EventEmitter.ipcMain.on.args (/Applications/MongoDB Compass.app/Contents/Resources/app.asar/node_modules/hadron-ipc/lib/main.js:43:17)
 at emitOne (events.js:121:20)
 at EventEmitter.emit (events.js:211:7)
 at WebContents.<anonymous> (/Applications/MongoDB Compass.app/Contents/Resources/electron.asar/browser/api/web-contents.js:286:13)
 at emitTwo (events.js:126:13)
 at WebContents.emit (events.js:214:7)



 Comments   
Comment by Massimiliano Marcon [ 14/Jan/19 ]

Hey MikeTheKID,

The fix should be in 1.16. Can you try 1.16.3 (download from here) and see if you can still reproduce the issue?

Comment by Michael Black [X] [ 08/Nov/18 ]

Still experiencing this issue in v1.15.4

Comment by Githook User [ 20/Sep/18 ]

Author:

{'name': 'Lucas Hrabovsky', 'email': 'hrabovsky.lucas@gmail.com', 'username': 'imlucas'}

Message: Backport COMPASS-3118: Fix orphaned windows (#1550)

  • :zap: Make travis use latest npm
  • Try rebuilding entire package-lock for travis
  • Shouldn't need to flush npm cache anymore
  • debugging travis
  • COMPASS-3113: Use xvfb-maybe instead of travis before_script
  • Make travis use `npm ci` which is faster than `npm install` for actual CI
  • Now that we're on `npm@6`, we can take advantage of https://docs.npmjs.com/cli/ci
  • Remove `ci` run script as it conflicts with this new feature (I was ahead of my time...)
  • Remove `mongodb-js-fmt` as everyone now uses prettier in their editor's
  • debugging travis
  • :zap: Cache npm build cache
  • Revert "COMPASS-3113: Use xvfb-maybe instead of travis before_script"

This reverts commit d39c6cbd877f502f575c157a19f1054adce6df9f.

  • Fix databases test
  • Debugging test failures
Comment by Githook User [ 20/Sep/18 ]

Author:

{'name': 'Lucas Hrabovsky', 'email': 'hrabovsky.lucas@gmail.com', 'username': 'imlucas'}

Message: Backport: COMPASS-3118: Fix orphaned windows (#1550)

  • :zap: Make travis use latest npm
  • Try rebuilding entire package-lock for travis
  • Shouldn't need to flush npm cache anymore
  • debugging travis
  • COMPASS-3113: Use xvfb-maybe instead of travis before_script
  • Make travis use `npm ci` which is faster than `npm install` for actual CI
  • Now that we're on `npm@6`, we can take advantage of https://docs.npmjs.com/cli/ci
  • Remove `ci` run script as it conflicts with this new feature (I was ahead of my time...)
  • Remove `mongodb-js-fmt` as everyone now uses prettier in their editor's
  • debugging travis
  • :zap: Cache npm build cache
  • Revert "COMPASS-3113: Use xvfb-maybe instead of travis before_script"

This reverts commit d39c6cbd877f502f575c157a19f1054adce6df9f.

  • Fix databases test
  • Debugging test failures
Comment by Githook User [ 20/Sep/18 ]

Author:

{'name': 'Lucas Hrabovsky', 'email': 'hrabovsky.lucas@gmail.com', 'username': 'imlucas'}

Message: Backport COMPASS-3118: Fix orphaned windows (#1550)

  • :zap: Make travis use latest npm
  • Try rebuilding entire package-lock for travis
  • Shouldn't need to flush npm cache anymore
  • debugging travis
  • COMPASS-3113: Use xvfb-maybe instead of travis before_script
  • Make travis use `npm ci` which is faster than `npm install` for actual CI
  • Now that we're on `npm@6`, we can take advantage of https://docs.npmjs.com/cli/ci
  • Remove `ci` run script as it conflicts with this new feature (I was ahead of my time...)
  • Remove `mongodb-js-fmt` as everyone now uses prettier in their editor's
  • debugging travis
  • :zap: Cache npm build cache
  • Revert "COMPASS-3113: Use xvfb-maybe instead of travis before_script"

This reverts commit d39c6cbd877f502f575c157a19f1054adce6df9f.

  • Fix databases test
  • Debugging test failures
Comment by Githook User [ 20/Sep/18 ]

Author:

{'name': 'Lucas Hrabovsky', 'email': 'hrabovsky.lucas@gmail.com', 'username': 'imlucas'}

Message: Backport: COMPASS-3118: Fix orphaned windows (#1550)

  • :zap: Make travis use latest npm
  • Try rebuilding entire package-lock for travis
  • Shouldn't need to flush npm cache anymore
  • debugging travis
  • COMPASS-3113: Use xvfb-maybe instead of travis before_script
  • Make travis use `npm ci` which is faster than `npm install` for actual CI
  • Now that we're on `npm@6`, we can take advantage of https://docs.npmjs.com/cli/ci
  • Remove `ci` run script as it conflicts with this new feature (I was ahead of my time...)
  • Remove `mongodb-js-fmt` as everyone now uses prettier in their editor's
  • debugging travis
  • :zap: Cache npm build cache
  • Revert "COMPASS-3113: Use xvfb-maybe instead of travis before_script"

This reverts commit d39c6cbd877f502f575c157a19f1054adce6df9f.

  • Fix databases test
  • Debugging test failures
Comment by Githook User [ 19/Sep/18 ]

Author:

{'name': 'Lucas Hrabovsky', 'email': 'hrabovsky.lucas@gmail.com', 'username': 'imlucas'}

Message: COMPASS-3118: Fix orphaned windows (#1550)

  • :zap: Make travis use latest npm
  • Try rebuilding entire package-lock for travis
  • Shouldn't need to flush npm cache anymore
  • debugging travis
  • COMPASS-3113: Use xvfb-maybe instead of travis before_script
  • Make travis use `npm ci` which is faster than `npm install` for actual CI
  • Now that we're on `npm@6`, we can take advantage of https://docs.npmjs.com/cli/ci
  • Remove `ci` run script as it conflicts with this new feature (I was ahead of my time...)
  • Remove `mongodb-js-fmt` as everyone now uses prettier in their editor's
  • debugging travis
  • :zap: Cache npm build cache
  • Revert "COMPASS-3113: Use xvfb-maybe instead of travis before_script"

This reverts commit d39c6cbd877f502f575c157a19f1054adce6df9f.

  • Fix databases test
  • Debugging test failures
Comment by Githook User [ 19/Sep/18 ]

Author:

{'name': 'Lucas Hrabovsky', 'email': 'hrabovsky.lucas@gmail.com', 'username': 'imlucas'}

Message: COMPASS-3118: Handle potential race of COMPASS-3101
Branch: COMPASS-3118
https://github.com/10gen/compass/commit/a84ba8c8afb9478fb3768a1b957494e7872238f5

Comment by Githook User [ 19/Sep/18 ]

Author:

{'name': 'Lucas Hrabovsky', 'email': 'hrabovsky.lucas@gmail.com', 'username': 'imlucas'}

Message: COMPASS-3118: Can no longer repro exception
Branch: COMPASS-3118
https://github.com/10gen/compass/commit/8759717f75d5bd33b2c942b826cb652ee456c33e

Comment by Githook User [ 18/Sep/18 ]

Author:

{'name': 'Lucas Hrabovsky', 'email': 'hrabovsky.lucas@gmail.com', 'username': 'imlucas'}

Message: COMPASS-3118: Fix orphaned windows
Branch: COMPASS-3118
https://github.com/10gen/compass/commit/d5c6b11702595429845a5cfcfe68d994370ccdad

Comment by Michael Black [X] [ 13/Sep/18 ]

Reinstalling the compass application also resolves the issue as a temporary work around if you don't wish to reboot your computer.

Comment by Craig Homa [ 13/Sep/18 ]

This issue is actively being worked on by the Compass team.

Comment by Brian Blevins [ 07/Sep/18 ]

Workaround

Rebooting one's desktop is likely the most straight-forward workaround. If that is not readily available, terminating all of the Compass background processes will allow Compass to restart successfully.

Comment by Brian Blevins [ 07/Sep/18 ]

This Node driver ticket was opened before the Compass jira project was publicly accessible. The IPC version of the error message seems to be a bug in Compass.

Generated at Wed Feb 07 22:32:12 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.