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

Intermittent backtraces when running many dexplode-partitions #148

Closed
jeromekelleher opened this issue Apr 26, 2024 · 2 comments
Closed

Comments

@jeromekelleher
Copy link
Contributor

When running dexplode-partition over 13517 partitions of chr2 in parallel using xargs, I see quite a few of these:

Exception ignored in: <module 'threading' from '/usr/lib/python3.9/threading.py'>
Traceback (most recent call last):
  File "/usr/lib/python3.9/threading.py", line 1415, in _shutdown
    atexit_call()
  File "/usr/lib/python3.9/concurrent/futures/process.py", line 93, in _python_exit
    thread_wakeup.wakeup()
  File "/usr/lib/python3.9/concurrent/futures/process.py", line 79, in wakeup
    self._writer.send_bytes(b"")
  File "/usr/lib/python3.9/multiprocessing/connection.py", line 205, in send_bytes
    self._send_bytes(m[offset:offset + size])
  File "/usr/lib/python3.9/multiprocessing/connection.py", line 416, in _send_bytes
    self._send(header + buf)
  File "/usr/lib/python3.9/multiprocessing/connection.py", line 373, in _send
    n = write(self._handle, buf)
OSError: [Errno 9] Bad file descriptor

Don't know what's going on here, will update as I get more info

@benjeffery
Copy link
Contributor

I've not seen this FWIW

@jeromekelleher
Copy link
Contributor Author

Closed in #164

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