clj-python / clj-python/libpython-clj

Subprocess failed (exit code: 139)

Open
#230 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Clojure
Stars
1.2k
Forks
74
PR merge metrics
No merged PRs in 30d

Description

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.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source files, tests, or entry points are named. Start by reproducing the crash with libpython-clj, nREPL, Java 1.8, and Python 3.7 or 3.10 while importing paddlenlp and running the reported computations; done means the exit-code-139 failure is explained and no longer occurs in those scenarios.

Written by the indexing model from the issue text.

Assessment

Tech stack
clojure, java, python
Domain
backend, developer-experience
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.