-
Notifications
You must be signed in to change notification settings - Fork 442
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
[VL] Managed memory leak in imported Spark UTs #1068
Comments
Tracking: 531 / 6341 UT cases are now leaking https://gist.github.com/zhztheplayer/40cbdd0be9502fa01d8397eaa087e74a |
Fix #1079 submitted for leak caused by iterator unconsumed data |
Add: Using debugging PR #1033 to count on leaked test cases |
Tracking: 531 / 6341 UT cases are leaking within #1079 Although #1079 fixes leak from some corner cases (e.g. TestOperator.scala which is out of this tracking) https://gist.github.com/zhztheplayer/9baf7566bd03d570286b9281be567043 |
Fix #1084 submitted for leak caused by Java side complex Arrow vector creation |
Tracking: 0 / 6341 UT cases are leaking within #1084 https://gist.github.com/zhztheplayer/b61fbf71af47d114eacb365ca7e33332 |
PR #1087 submitted to enable leak error reporting (which was previously warning) in Spark UT |
Closing as resolved. |
Errors with "Managed memory leak detected" are being reported from the import Spark UTs.
The errors were ignored since we set "spark.unsafe.exceptionOnMemoryLeak=false" in tests.
We should deal with all of the current reported leak issues then finally set "spark.unsafe.exceptionOnMemoryLeak=true".
The text was updated successfully, but these errors were encountered: