Skip to content
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 Java OOM caused by incorrect state of shouldCapture when exception occurred #9944

Merged
merged 1 commit into from
Dec 4, 2023

Conversation

winningsix
Copy link
Collaborator

This closes #9829.

Typically, shouldCapture in ShimmedExecutionPlanCaptureCallbackImpl should work as pair of startCapture and getResultsWithTimeout. But it may fail to be restored when exception happens in Gpu run sesssion. In #9829 case, it missed to add a non-GPU operator resulting in an IllegalArgumentException. Then getResultsWithTimeout was failed to be updated.

@winningsix winningsix marked this pull request as ready for review December 4, 2023 09:15
@winningsix
Copy link
Collaborator Author

build

@jlowe jlowe merged commit 02e7d40 into NVIDIA:branch-24.02 Dec 4, 2023
39 checks passed
@sameerz sameerz added the test Only impacts tests label Dec 4, 2023
@winningsix winningsix deleted the oom branch December 4, 2023 22:47
res-life pushed a commit to res-life/spark-rapids that referenced this pull request Dec 11, 2023
pxLi pushed a commit that referenced this pull request Dec 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
test Only impacts tests
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[BUG] Java OOM when testing non-UTC time zone with lots of cases fallback.
4 participants