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 starting up a self-hosting workspace, I get very high CPU. Profiling revealed that a lot of time was spent appending stuff to an output buffer. The "hosted-instance-log" output stream revealed a very large number of messages like this:
Extension-Host:RangeError: Maximum call stack size exceeded
at DisposableCollection.get (/home/theia/node_modules/@theia/core/lib/common/disposable.js:65:23)
at DisposableCollection.dispose (/home/theia/node_modules/@theia/core/lib/common/disposable.js:72:18)
at DisposableCollection.disposable.dispose (/home/theia/node_modules/@theia/core/lib/common/disposable.js:101:13)
at DisposableCollection.disposable.dispose (/home/theia/node_modules/@theia/core/lib/common/disposable.js:101:13)
at DisposableCollection.disposable.dispose (/home/theia/node_modules/@theia/core/lib/common/disposable.js:101:13)
at DisposableCollection.disposable.dispose (/home/theia/node_modules/@theia/core/lib/common/disposable.js:101:13)
at DisposableCollection.disposable.dispose (/home/theia/node_modules/@theia/core/lib/common/disposable.js:101:13)
at DisposableCollection.disposable.dispose (/home/theia/node_modules/@theia/core/lib/common/disposable.js:101:13)
at DisposableCollection.disposable.dispose (/home/theia/node_modules/@theia/core/lib/common/disposable.js:101:13)
at DisposableCollection.disposable.dispose (/home/theia/node_modules/@theia/core/lib/common/disposable.js:101:13)
This looks a lot like we're directly or indirectly adding a DisposableCollection to itself.
Che version
latest
nightly
[x ] other: 7.27.0
Steps to reproduce
n/a
Runtime
kubernetes (include output of kubectl version)
Openshift (include output of oc version)
minikube (include output of minikube version and kubectl version)
minishift (include output of minishift version and oc version)
docker-desktop + K8S (include output of docker version and kubectl version)
other: (please specify) dogfooding instance
Installation method
chectl
provide a full command that was used to deploy Eclipse Che (including the output)
provide an output of chectl version command
OperatorHub
I don't know
Environment
my computer
Windows
Linux
macOS
Cloud
Amazon
Azure
GCE
other (please specify) dogfooding instance
other: please specify
Eclipse Che Logs
Additional context
The text was updated successfully, but these errors were encountered:
che-bot
added
the
status/need-triage
An issue that needs to be prioritized by the curator responsible for the triage. See https://github.
label
Mar 9, 2021
metlos
removed
the
status/need-triage
An issue that needs to be prioritized by the curator responsible for the triage. See https://github.
label
Mar 16, 2021
Describe the bug
When starting up a self-hosting workspace, I get very high CPU. Profiling revealed that a lot of time was spent appending stuff to an output buffer. The "hosted-instance-log" output stream revealed a very large number of messages like this:
This looks a lot like we're directly or indirectly adding a DisposableCollection to itself.
Che version
Steps to reproduce
n/a
Runtime
kubectl version
)oc version
)minikube version
andkubectl version
)minishift version
andoc version
)docker version
andkubectl version
)Installation method
chectl version
commandEnvironment
Eclipse Che Logs
Additional context
The text was updated successfully, but these errors were encountered: