Details
-
Bug
-
Resolution: Duplicate
-
Major - P3
-
None
-
None
-
Not Needed
Description
We have seen instances where the `autoUpdater` is doing work after the cleanup procedure of compass, which may cause unintended behavior (ie. logging on closed files).
MongoDB Compass Beta has encountered an unexpected error
|
Error [ERR_STREAM_WRITE_AFTER_END]: write after end
|
at process.<anonymous> (/Applications/MongoDB Compass Beta.app/Contents/Resources/app.asar/build/252.js:1:19006) |
at f (/Applications/MongoDB Compass Beta.app/Contents/Resources/app.asar/build/main.js:1:271) |
at Object.write (/Applications/MongoDB Compass Beta.app/Contents/Resources/app.asar/build/main.js:1:335) |
at p._write (/Applications/MongoDB Compass Beta.app/Contents/Resources/app.asar/build/main.js:1:79764) |
at p.info (/Applications/MongoDB Compass Beta.app/Contents/Resources/app.asar/build/main.js:1:79970) |
at AutoUpdater.<anonymous> (/Applications/MongoDB Compass Beta.app/Contents/Resources/app.asar/build/113.js:1:2915) |
We should involve the autoUpdater in the cleanup by detaching all the events attatched on the autoupdater instance.
Attachments
Issue Links
- clones
-
COMPASS-5882 Properly detach events and intervals for auto-updates
-
- Closed
-