clj-python / clj-python/libpython-clj

Subprocess failed (exit code: 139)

未關閉
#230 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

還沒有人認領這個 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.

貢獻指南

開啟貢獻指南

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 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

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。