[COMPASS-3101] Compass - continuing process "Mongo Compass" after closing client Created: 31/Aug/18  Updated: 29/Oct/23  Resolved: 26/Sep/18

Status: Closed
Project: Compass
Component/s: Compass
Affects Version/s: 1.15.0
Fix Version/s: 1.16.1

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

Windows 10 - 64x - v.1709
Processor: Intel i5-6600
RAM: 16GB


Attachments: PNG File image-2018-08-31-14-02-35-236.png    
Issue Links:
Duplicate
duplicates COMPASS-3118 Object has been destroyed after closi... Closed
Related
is related to COMPASS-3118 Object has been destroyed after closi... Closed
is related to COMPASS-3156 After compass is closed it processes ... Closed
Sprint: Iteration Mango Miso

 Description   

After restarting client I got error:

The only way to bypass the problem is close client by clicking EXIT in the drop menu.

And If already closed improperty, killing process solve the problem.

 

Conclusion:

Process continuing after closing client by clicking X button.



 Comments   
Comment by Guillermo Lopez [ 22/Nov/18 ]

Thanks Massimiliano! Do you know when is it going to be released?

Comment by Massimiliano Marcon [ 22/Nov/18 ]

Hi guillermo.lopez@portoseguro.com.uy, bug should be fixed in 1.16.1.

Comment by Guillermo Lopez [ 17/Oct/18 ]

Hi, this bug claims to be fixed in version 1.15.4 however I'm still experimenting it as originally described.

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

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