plotly / plotly/Kaleido

WARNING Thread(Thread-3 (run)) choreographer.browser_async:browser_async.py:_close()- Resorting to unclean kill browser

Open
#327 18 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

P2
Dominant language
Python
Stars
498
Forks
62
Avg merge
1d 11h
Merged PRs (30d)
2

Description

Using:
Python 3.11
Multiprocessing
Kaleido 1.0.0rc13
choreographer 1.0.7
plotly 6.1.0
venv

I have a script which using multiprocessing (limited to 30 cores right now on this machine), to generate lots of static images for hosting. I've just moved to testing the new plotly with the new kaleido (another long suffering W11 kaleido hanging process user here), but discovered a new problem so flagging it here because I've not seen it raised anywhere else.

My logs are full of:

WARNING Thread(Thread-3 (run)) choreographer.browser_async:browser_async.py:_close()- Resorting to unclean kill browser.
WARNING Thread(Thread-3 (run)) choreographer.browser_async:browser_async.py:_close()- Resorting to unclean kill browser.
WARNING Thread(Thread-3 (run)) choreographer.browser_async:browser_async.py:_close()- Resorting to unclean kill browser.
WARNING Thread(Thread-3 (run)) choreographer.browser_async:browser_async.py:_close()- Resorting to unclean kill browser.
WARNING Thread(Thread-3 (run)) choreographer.browser_async:browser_async.py:_close()- Resorting to unclean kill browser.
WARNING Thread(Thread-3 (run)) choreographer.browser_async:browser_async.py:_close()- Resorting to unclean kill browser.
WARNING Thread(Thread-3 (run)) choreographer.browser_async:browser_async.py:_close()- Resorting to unclean kill browser.
WARNING Thread(Thread-5 (run)) choreographer.browser_async:browser_async.py:_close()- Resorting to unclean kill browser.
WARNING Thread(Thread-5 (run)) choreographer.browser_async:browser_async.py:_close()- Resorting to unclean kill browser.
WARNING Thread(Thread-5 (run)) choreographer.browser_async:browser_async.py:_close()- Resorting to unclean kill browser.
WARNING Thread(Thread-5 (run)) choreographer.browser_async:browser_async.py:_close()- Resorting to unclean kill browser.
WARNING Thread(Thread-7 (run)) choreographer.browser_async:browser_async.py:_close()- Resorting to unclean kill browser.
WARNING Thread(Thread-7 (run)) choreographer.browser_async:browser_async.py:_close()- Resorting to unclean kill browser.
WARNING Thread(Thread-7 (run)) choreographer.browser_async:browser_async.py:_close()- Resorting to unclean kill browser.

I've not seen anyone post this. I'm attempting to put a small script together to reproduce this out of the venv in which it current runs to remove that.

Is it a known problem? Can I suppress the warning if that's all it is? Do I need to care?

Contributor guide

No contributing guide indexed for this repository

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

Start with choreographer/browser_async.py, especially the _close() path named in the warning, and review how browser shutdown behaves when multiprocessing creates many workers. Build the promised minimal reproduction using Python 3.11 and the listed Kaleido, choreographer, and Plotly versions. Done means identifying whether the warning indicates a real cleanup failure and documenting or testing the appropriate behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.