Fatal exception in next-render-worker-pages: v8::internal::ConcurrentMarking::RunMajor

[Mabisi]

Environment

Docker

Version

0.14.2

Describe the problem

Every few hours it will report an error and require a container restart to continue working. How can I make it return to normal?

Logs

�[36mℹ�[39m Saving updated configuration of 'default' config.
Error: socket hang up
    at connResetException (node:internal/errors:714:14)
    at Socket.socketOnEnd (node:_http_client:519:23)
    at Socket.emit (node:events:523:35)
    at endReadableNT (node:internal/streams/readable:1367:12)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
  code: 'ECONNRESET'
}
[next-auth][error][CLIENT_FETCH_ERROR] 
https://next-auth.js.org/errors#client_fetch_error fetch failed {
  error: {
    message: 'fetch failed',
    stack: 'TypeError: fetch failed\n' +
      '    at Object.fetch (/app/node_modules/next/dist/compiled/undici/index.js:1:26669)',
    name: 'TypeError'
  },
  url: 'http://a78c3cdf8a16:7575/api/auth/session',
  message: 'fetch failed'
}
Exporting hostname...
Migrating database...
yarn run v1.22.19
$ ts-node ./migrate.ts
Done in 2.30s.
Starting production server...
Listening on port 7575 url: http://a78c3cdf8a16:7575

�[41m�[30m ERROR �[39m�[49m Unexpected response: connect ECONNREFUSED 10.0.0.50:8923

Exporting hostname...
Migrating database...
yarn run v1.22.19
$ ts-node ./migrate.ts
Done in 2.24s.
Starting production server...
Listening on port 7575 url: http://a78c3cdf8a16:7575

�[41m�[30m ERROR �[39m�[49m App [object Object] not found


�[41m�[30m ERROR �[39m�[49m App [object Object] not found

�[36mℹ�[39m Saving updated configuration of 'default' config.
Exporting hostname...
Migrating database...
yarn run v1.22.19
$ ts-node ./migrate.ts
Done in 1.86s.
Starting production server...
Listening on port 7575 url: http://a78c3cdf8a16:7575
�[36mℹ�[39m Saving updated configuration of 'default' config.


#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0x7f2ea3ffe6c0
 1: 0xd04d31  [next-render-worker-pages]
 2: 0x20d9e61 V8_Fatal(char const*, ...) [next-render-worker-pages]
 3: 0x10665a6 v8::internal::ConcurrentMarking::RunMajor(v8::JobDelegate*, v8::base::EnumSet<v8::internal::CodeFlushMode, int>, unsigned int, bool) [next-render-worker-pages]
 4: 0x106a6fd v8::internal::ConcurrentMarking::JobTaskMajor::Run(v8::JobDelegate*) [next-render-worker-pages]
 5: 0x1d1d688 v8::platform::DefaultJobWorker::Run() [next-render-worker-pages]
 6: 0xd04ed1  [next-render-worker-pages]
 7: 0x7f2ea9e87ea7  [/lib/x86_64-linux-gnu/libpthread.so.0]
 8: 0x7f2ea9da7a2f clone [/lib/x86_64-linux-gnu/libc.so.6]

Context

No response

Please tick the boxes

• I confirm that I attached the proper logs
• I've read the docs
• I've checked for duplicate issues
• I've tried to debug myself

[Mabisi]

Can anyone help me solve this problem?

[manuel-rw]

Hi, this looks like an underlying error caused when rendering the pages.
The cause for this could be almost anything (eg. memory issues, incompatible hardware, buggy code, ...).
Can you provide more information on your hardware, software, your docker compose / run and when this happens?

[manuel-rw]

Hi @Mabisi , please respond with more details to this issue. As we are unable to reproduce this without further information, we may close this issue. Thank you for your understanding.

[lousyCraftsman]

I have run into the same issue. Any version higher than 0.14.3 and my homarr container slowly takes up all the available RAM and I have to restart the LXC to get anything back. Reverting to 0.14.3 resolves the issue.

[manuel-rw]

Hi @lousyCraftsman , this sounds like a memory leak and I suggest you to open a new issue.
As described in #1993, this will be fixed in 1.0.