Hang after too many gl requests in Docker
See original GitHub issueFrom the tests documented starting at https://github.com/plotly/streambed/issues/9865#issuecomment-349995119:
When image-exporter is run as an imageserver in Docker, after a small number of gl requests (30-40), the image-exporter hangs completely. The request in progress times out, and the server won’t accept any more connections and must be restarted.
Two examples:
- If
test/image-make_baseline.js
is used to rungl*
, it hangs atgl3d_chrisp-nan-1.json
. - If
test/image-make_baseline.js
is used to rungl3d*
, it makes it pastgl3d_chrisp-nan-1.json
and hangs atgl3d_snowden_altered.json
.
This means that the issue is unlikely to be specific to any one plot, but rather some resource becomes exhausted or something builds up to the point where image generation can’t proceed.
Issue Analytics
- State:
- Created 6 years ago
- Comments:39 (39 by maintainers)
Top Results From Across the Web
What to do when all docker commands hang?
After the instance reboots, whenever I try to run ANY docker command (e.g., docker info), it just hangs and doesn't return.
Read more >Container Scanning - GitLab Documentation
Creates a container_scanning job in your CI/CD pipeline. Pulls the built Docker image from your project's container registry (see requirements) and scans it...
Read more >Ombi plex login - cittafamiglia.it
Plex for Pros. 9 mar 2021 Plex · Login to Ombi as an administrator. tv and sign in if you have not. tv...
Read more >delete issues gitlab
View issues, comments, merge requests, and changed files in the sidebar, ... open the Command Palette and run the Azure: Sign In …....
Read more >Fastapi event loop - Agenzia traduzioni Terni
The server detected an infinite loop while processing the request (sent in lieu ... Hi - I grabbed this from the FastAPI issue...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Oh I should mention. I tried running the gl image tests in docker without the ignore-gpu-blacklist flag yesterday:. Without that flag the gl images fail to generate.
@monfera @etpinard I’ve added some debugging stuff to the Docker container in #44.
Xvfb
runs with X errors sent to STDOUT (instead of being ignored), and auditing is turned on. This means it prints a message for every X connection and disconnection, which shows if Electron is connecting and disconnecting (spoiler alert: it isn’t).Xvfb
’s screen dimensions have been doubled.Usage:
docker build -f deployment/Dockerfile -t isdebug .
), or grab it from quay.isdebug
and expose the VNC and imageserver ports:docker rm -f isdebug ; docker run -p 9091:9091 -p 5900:5900 --name isdebug -ti isdebug
docker exec -ti isdebug /vnc
localhost:0
using your favourite client, such asgvncviewer
on Ubuntu or Chicken of the VNC on OS X.node test/image/make_baseline.js gl*
(you’ll want to modifytestContainerUrl
intasks/util/constants.js
, like in https://github.com/plotly/plotly.js/tree/image-exporter-testing)In my case the image exporter window where the work was occurring was in fluxbox tab 2. Some errors were printed during normal operation (at this point images were being generated successfully):
When the server hung, a different message was printed:
I have not had the chance to investigate the significance of either of these things.