-
Notifications
You must be signed in to change notification settings - Fork 261
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
fix/pool-improperly-destroyed #584
Conversation
I am running the latest build 4.0.2, and am currently experiencing the same issue originally mentioned. Do you happen to know when the next release that will include this bug fix will be? Thanks, |
Hi @LMcNulty-MA, Thanks for letting us know. I'll look into it. Could you please provide some more info about when it happens in your case? Do you use export server as a node module and direct calls of mentioned function result in the problem? |
@PaulDalek Thanks for the reply, I will be brief and to the point with my replication of the issue
The following two files are what I'm using to produce this, and the highcharts-export-server.log is attached Server.js - NOTE: This is the exact setup from the github documentation
python request file
|
Hi @PaulDalek I'm so sorry to bother you, just wondering if you've had a chance to see the comment above, and if a fix may be in the works.. can't thank you enough |
Hi @LMcNulty-MA, My apologies for the delayed response. The code you are using comes from the Node.js Module section, which demonstrates the simplest way to export a single chart. At the end of the process, the |
Description of the problem
killPool()
- it should kill the poolinitPool()
- instead of initializing the pool, we got this:That's because
pool = true
, it was not set tofalse
after destruction :)Reported by an ADV user on FreshDesk.