You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When specifying low memory limits for a diagramsnet container in Kubernetes, chromium processes could remain in a zombie state if we send a lot of parallel requests.
The diagramsnet service just stopped working with following error, but the container is still alive.
Error 400: : An error occurred while converting the diagram: connect ECONNREFUSED 127.0.0.1:40619
E.g:
$ seq 10 | xargs -P 10 -I -- curl -k https://kroki.local/diagramsnet/svg/eNpLyUwvSizIUHBXqPZIzcnJ17ULzy_KSanlAgB1EAjQ
Error 400: Error: An error occurred while converting the diagram: Navigating frame was detached
Error: Navigating frame was detached
at #onFrameDetached (file:///usr/local/kroki/node_modules/puppeteer-core/lib/esm/puppeteer/cdp/LifecycleWatcher.js:100:47)
at file:///usr/local/kroki/node_modules/puppeteer-core/lib/esm/third_party/mitt/mitt.js:36:7
at Array.map (<anonymous>)
at Object.emit (file:///usr/local/kroki/node_modules/puppeteer-core/lib/esm/third_party/mitt/mitt.js:35:20)
at CdpFrame.emit (file:///usr/local/kroki/node_modules/puppeteer-core/lib/esm/puppeteer/common/EventEmitter.js:77:23)
at #removeFramesRecursively (file:///usr/local/kroki/node_modules/puppeteer-core/lib/esm/puppeteer/cdp/FrameManager.js:448:15)
at #onClientDisconnect (file:///usr/local/kroki/node_modules/puppeteer-core/lib/esm/puppeteer/cdp/FrameManager.js:91:42)Error 400: : An error occurred while converting the diagram: connect ECONNREFUSED 127.0.0.1:43847
Error 400: Error: An error occurred while converting the diagram: Navigating frame was detached
Error: Navigating frame was detached
at #onFrameDetached (file:///usr/local/kroki/node_modules/puppeteer-core/lib/esm/puppeteer/cdp/LifecycleWatcher.js:100:47)
at file:///usr/local/kroki/node_modules/puppeteer-core/lib/esm/third_party/mitt/mitt.js:36:7
at Array.map (<anonymous>)
at Object.emit (file:///usr/local/kroki/node_modules/puppeteer-core/lib/esm/third_party/mitt/mitt.js:35:20)
at CdpFrame.emit (file:///usr/local/kroki/node_modules/puppeteer-core/lib/esm/puppeteer/common/EventEmitter.js:77:23)
at #removeFramesRecursively (file:///usr/local/kroki/node_modules/puppeteer-core/lib/esm/puppeteer/cdp/FrameManager.js:448:15)
at #onClientDisconnect (file:///usr/local/kroki/node_modules/puppeteer-core/lib/esm/puppeteer/cdp/FrameManager.js:91:42)
at runNextTicks (node:internal/process/task_queues:60:5)
at listOnTimeout (node:internal/timers:540:9)
at process.processTimers (node:internal/timers:514:7)Error 400: Error: An error occurred while converting the diagram: Navigating frame was detached
Error: Navigating frame was detached
at #onFrameDetached (file:///usr/local/kroki/node_modules/puppeteer-core/lib/esm/puppeteer/cdp/LifecycleWatcher.js:100:47)
at file:///usr/local/kroki/node_modules/puppeteer-core/lib/esm/third_party/mitt/mitt.js:36:7
at Array.map (<anonymous>)
at Object.emit (file:///usr/local/kroki/node_modules/puppeteer-core/lib/esm/third_party/mitt/mitt.js:35:20)
at CdpFrame.emit (file:///usr/local/kroki/node_modules/puppeteer-core/lib/esm/puppeteer/common/EventEmitter.js:77:23)
at #removeFramesRecursively (file:///usr/local/kroki/node_modules/puppeteer-core/lib/esm/puppeteer/cdp/FrameManager.js:448:15)
at #onClientDisconnect (file:///usr/local/kroki/node_modules/puppeteer-core/lib/esm/puppeteer/cdp/FrameManager.js:91:42)
at runNextTicks (node:internal/process/task_queues:60:5)
at listOnTimeout (node:internal/timers:540:9)
at process.processTimers (node:internal/timers:514:7)Error 400: Error: An error occurred while converting the diagram: Navigating frame was detached
Error: Navigating frame was detached
at #onFrameDetached (file:///usr/local/kroki/node_modules/puppeteer-core/lib/esm/puppeteer/cdp/LifecycleWatcher.js:100:47)
at file:///usr/local/kroki/node_modules/puppeteer-core/lib/esm/third_party/mitt/mitt.js:36:7
at Array.map (<anonymous>)
at Object.emit (file:///usr/local/kroki/node_modules/puppeteer-core/lib/esm/third_party/mitt/mitt.js:35:20)
at CdpFrame.emit (file:///usr/local/kroki/node_modules/puppeteer-core/lib/esm/puppeteer/common/EventEmitter.js:77:23)
at #removeFramesRecursively (file:///usr/local/kroki/node_modules/puppeteer-core/lib/esm/puppeteer/cdp/FrameManager.js:448:15)
at #onClientDisconnect (file:///usr/local/kroki/node_modules/puppeteer-core/lib/esm/puppeteer/cdp/FrameManager.js:91:42)Error 400: : An error occurred while converting the diagram: connect ECONNREFUSED 127.0.0.1:43847
Error 400: : An error occurred while converting the diagram: connect ECONNREFUSED 127.0.0.1:43847
Error 400: : An error occurred while converting the diagram: connect ECONNREFUSED 127.0.0.1:43847
Error 400: : An error occurred while converting the diagram: connect ECONNREFUSED 127.0.0.1:43847
Error 400: Error: An error occurred while converting the diagram: Navigating frame was detached
Error: Navigating frame was detached
at #onFrameDetached (file:///usr/local/kroki/node_modules/puppeteer-core/lib/esm/puppeteer/cdp/LifecycleWatcher.js:100:47)
at file:///usr/local/kroki/node_modules/puppeteer-core/lib/esm/third_party/mitt/mitt.js:36:7
at Array.map (<anonymous>)
at Object.emit (file:///usr/local/kroki/node_modules/puppeteer-core/lib/esm/third_party/mitt/mitt.js:35:20)
at CdpFrame.emit (file:///usr/local/kroki/node_modules/puppeteer-core/lib/esm/puppeteer/common/EventEmitter.js:77:23)
at #removeFramesRecursively (file:///usr/local/kroki/node_modules/puppeteer-core/lib/esm/puppeteer/cdp/FrameManager.js:448:15)
at #onClientDisconnect (file:///usr/local/kroki/node_modules/puppeteer-core/lib/esm/puppeteer/cdp/FrameManager.js:91:42)
Issue:
When specifying low memory limits for a diagramsnet container in Kubernetes, chromium processes could remain in a zombie state if we send a lot of parallel requests.
The diagramsnet service just stopped working with following error, but the container is still alive.
E.g:
Normal state:
Hanging Chromium processes in the zombie state:
What did you expect to see?
The Chromium processes should be properly handled.
The text was updated successfully, but these errors were encountered: