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

Do not crash when encountering empty stack traces #10

Merged
merged 1 commit into from
Jan 3, 2020

Conversation

fvennetier
Copy link
Member

Recent JVMs run with OmitStackTraceInFastThrow enabled by default. When an exception occurs several times, the stack trace is no more generated, but COSBench still tries to parse it and fails miserably. One solution is to run COSBench with -XX:-OmitStackTraceInFastThrow. For extra security, we will also ignore such empty stack traces.

Fixes: intel-cloud#323
Fixes: intel-cloud#331

Recent JVMs run with OmitStackTraceInFastThrow enabled by default. When
an exception occurs several times, the stack trace is no more generated,
but COSBench still tries to parse it, and fails miserably. One solution
is to run COSBench with -XX:-OmitStackTraceInFastThrow. For extra
security we will also ignore such empty stack traces.

Fixes: intel-cloud#323
Fixes: intel-cloud#331
@fvennetier fvennetier requested a review from fatpat December 31, 2019 15:42
Copy link
Member

@fatpat fatpat left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@fvennetier fvennetier merged commit e212bd7 into open-io:master-openio Jan 3, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants