Idle Crash in Development Mode

[bmartin1134]

Idle Crash in Development Mode
Meteor Version: release/METEOR@3.0-rc.0
OSX Sonoma 14.3.2

Expected: Dont Crash during idle
Actual: Crashes during idle.

Not sure of production mode as not willing to push yet.

Repo: Just use Meteor create

=> Meteor server restarted at: http://localhost:3000/
I20240425-00:50:55.704(-7)? Checking that at least 1 user exists.
I20240425-00:50:55.704(-7)? Users exist. Application starting.
W20240425-01:15:45.402(-7)? (STDERR) node:internal/process/promises:289
W20240425-01:15:45.404(-7)? (STDERR) triggerUncaughtException(err, true /* fromPromise /);
W20240425-01:15:45.404(-7)? (STDERR) ^
W20240425-01:15:45.404(-7)? (STDERR)
W20240425-01:15:45.404(-7)? (STDERR) PoolClearedOnNetworkError: Connection to 127.0.0.1:3001 interrupted due to server monitor timeout
W20240425-01:15:45.404(-7)? (STDERR) at ConnectionPool.interruptInUseConnections (/Users//.meteor/packages/npm-mongo/.4.16.1-beta300.7.194xp4b.jbl6++os+web.browser+web.browser.legacy+web.cordova/npm/node_modules/mongodb/src/cmap/connection_pool.ts:479:28)
W20240425-01:15:45.404(-7)? (STDERR) at /Users/*/.meteor/packages/npm-mongo/.4.16.1-beta300.7.194xp4b.jbl6++os+web.browser+web.browser.legacy+web.cordova/npm/node_modules/mongodb/src/cmap/connection_pool.ts:464:35
W20240425-01:15:45.443(-7)? (STDERR) at processTicksAndRejections (node:internal/process/task_queues:77:11)
W20240425-01:15:45.443(-7)? (STDERR) at runNextTicks (node:internal/process/task_queues:64:3)
W20240425-01:15:45.443(-7)? (STDERR) at listOnTimeout (node:internal/timers:540:9)
W20240425-01:15:45.443(-7)? (STDERR) at processTimers (node:internal/timers:514:7) {
W20240425-01:15:45.443(-7)? (STDERR) address: '127.0.0.1:3001',
W20240425-01:15:45.443(-7)? (STDERR) [Symbol(errorLabels)]: Set(1) { 'RetryableWriteError' }
W20240425-01:15:45.444(-7)? (STDERR) }
W20240425-01:15:45.444(-7)? (STDERR)
W20240425-01:15:45.444(-7)? (STDERR) Node.js v20.11.1
=> Exited with code: 1
=> Your application is crashing. Waiting for file change.

[jirikrepl]

I have had this error since Meteor 2.14 or earlier.
It might be related to https://www.mongodb.com/community/forums/t/poolclearedonnetworkerror-mongodb-net-27017-interrupted-due-to-server-monitor-timeout/252292

Couldn't it be that some Mongo connectionTimeout has to be increased on localhost?

[leonardoventurini]

@bmartin1134 @jirikrepl Can you provide more details on how this happens? Does the computer go to sleep during that time? Or it simply crashes after a minute or two?

[jirikrepl]

I think it throws that error after some time. It does not crash the meteor process, it just prints the error. Also, I haven't noticed any Mongo errors within my meteor app on localhost. I just got used to this error:D

[bmartin1134]

@leonardoventurini I think you are right about going to sleep. I think an osx update on my test system enabled sleeping again.

I will close it for now. If i see it after i push to galaxy I will re-open.