-
Notifications
You must be signed in to change notification settings - Fork 35
Go routine memory allocation issue #181
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
Comments
Same problem, with 1.5.3, but 1.5.2 seems to work. |
thanks @RainerW - i think we are narrowing in on the issue. seems to only happen with godror 0.46.0 and later, not earlier versions. doing more debugging to try to isolate the root cause |
See: godror/godror#361 |
In testing, using connection pooling parameters resolved the issue. However, let's see what godror maintainers think :) |
We believe we have this fixed in 1.5.4 - if you still see the error, please reopen, or open a new issue to let you know. Thanks very much for your input. |
@markxnelson, unfortunately I still face this issue in |
@VictorErmakov can you share the parameters used for the exporter, as well as the following details about the environment you're running it on:
In my testing, I found that increasing the maximum idle connections can resolve this problem:
|
@anders-swanson Following parameters helped! At least it does not throw an error in the first 10 minutes! Probably it should be added in the example Thanks! |
Perfect, thanks for opening the PR. I am hopeful future versions of godror will handle this better too. |
error emit like below
Typically, it fetches data successfully for the first 2-3 times, but it seems that during the memory allocation/deallocation process of goroutines, they get tangled, leading to issues with duplicate memory allocation or deallocation. Please provide your opinion.
The text was updated successfully, but these errors were encountered: