Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Kernel dies (ungracefully) on import from out-of-memory condition #133

Closed
michaelweinold opened this issue Jul 18, 2022 · 1 comment
Closed

Comments

@michaelweinold
Copy link
Contributor

Importing the ecoinvent 3.8 cutoff dataset (~2.2GB) on a system with 4GB ram results in kernel death along with a non-descript error message. Importing the same dataset on a system with 32GB ram works fine. The associated error messages are likely related to out-of-memory conditions, as per VS Code issue #9741:

Running

ei38cutoff = bi.SingleOutputEcospold2Importer(
    "/data/user/weinol_m/ecoinvent/ecoinvent_3-8_cutoff_ecoSpold02/datasets",
    "ecoinvent 3.8 cutoff"
)
ei38cutoff.apply_strategies()
ei38cutoff.statistics()

returns:

Jupyterhub: "connection failed"

Screenshot 2022-07-18 at 15 29 35

Visual Studio Code: "The Kernel crashed while executing code in the the current cell or a previous cell."

Screenshot 2022-07-18 at 15 34 48

The VS Code Jupyter output reads:

(...)
info 15:33:0.573: Cell 2 executed with state Success
info 15:33:0.779: Cell 3 executed with state Success
info 15:33:0.896: Cell 4 executed with state Success
info 15:33:2.513: Execute Cell 5 /psi/home/weinol_m/Systematic bias in Monte Carlo medians.ipynb
error 15:34:28.932: Error in waiting for cell to complete [Error: Canceled future for execute_request message before replies were done
	at a.KernelShellFutureHandler.dispose (/psi/home/weinol_m/.vscode-server/extensions/ms-toolsai.jupyter-2022.6.1201981810/out/node_modules/@jupyterlab/services.js:2:32353)
	at /psi/home/weinol_m/.vscode-server/extensions/ms-toolsai.jupyter-2022.6.1201981810/out/node_modules/@jupyterlab/services.js:2:26572
	at Map.forEach (<anonymous>)
	at y._clearKernelState (/psi/home/weinol_m/.vscode-server/extensions/ms-toolsai.jupyter-2022.6.1201981810/out/node_modules/@jupyterlab/services.js:2:26557)
	at /psi/home/weinol_m/.vscode-server/extensions/ms-toolsai.jupyter-2022.6.1201981810/out/node_modules/@jupyterlab/services.js:2:29000
	at runMicrotasks (<anonymous>)
	at processTicksAndRejections (node:internal/process/task_queues:96:5)]
warn 15:34:28.933: Cell completed with errors {
  message: 'Canceled future for execute_request message before replies were done'
}
info 15:34:28.935: Cancel all remaining cells true || Error || undefined
info 15:34:28.935: Cancel pending cells
info 15:34:28.936: Cell 5 executed with state Error

Kernel: Linux x86_64 GNU/Linux
Distribution: Red Hat Enterprise Linux Server release 7.9 (Maipo)
Specs: 4GB RAM, 1 vCPU (Intel Xeon E5-2697Av4)

@michaelweinold michaelweinold transferred this issue from brightway-lca/brightway2 Aug 2, 2022
@cmutel
Copy link
Member

cmutel commented Sep 17, 2023

This is a great issue report, and I am going to ignore it 😛

@cmutel cmutel closed this as not planned Won't fix, can't repro, duplicate, stale Sep 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants