clj-python / clj-python/libpython-clj
Subprocess failed (exit code: 139)
还没有人认领这个 Issue。
- 主要语言
- Clojure
- 星标
- 1.2k
- 派生
- 74
- PR 合并指标
- 30 天内没有已合并 PR
描述
I don't know whether it's a common problem.
When I imported some big deep-learning module, for example, paddlenlp, and after I finished some computation, nRepl would crash with the info 'Subprocess failed (exit code: 139)'.
However, when the computation was running, it seemed that nRepl wouldn't crash. When I repeated a computation for 1000 times, and each time I modified a bit to make it acctually run so many iterations, nRepl would crash after the loop finished.
But even when I didn't do anything after I require-python this module, it would also crash. Sometimes, nRepl didn't crash after a series of computations, and even an hour passed it wouldn't crash any more if no operation inputted, until I ran another command (even clojure-native form) on it.
I used Java 1.8 and python 3.7, cider on emacs, and it repeated when I changed into python 3.10.
贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
调研方向
未指定源文件、测试或入口点。首先使用 libpython-clj、nREPL、Java 1.8 和 Python 3.7 or 3.10 重现崩溃,同时导入 paddlenlp 并运行报告中的计算;当 exit-code-139 失败得到解释,且不再在这些场景中发生时,即表示完成。
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- clojure, java, python
- 领域
- backend, developer-experience
- Issue 类型
- 缺陷
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 活跃度
- 停滞
- 描述清晰度
- 需要澄清
- 新手友好度
- 25/100