-
Notifications
You must be signed in to change notification settings - Fork 738
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
Crash in NativeCrypto.DigestUpdate (openssl native) #4530
Comments
The workaround for this is to disable the openssl digest support. |
MessageDigest openssl support is being disabled due to eclipse-openj9#4530, the test needs to check a different algorithm. ibmruntimes/openj9-openjdk-jdk11#117 ibmruntimes/openj9-openjdk-jdk8#259 [ci skip] Signed-off-by: Peter Shipton <Peter_Shipton@ca.ibm.com>
MessageDigest openssl support is being disabled due to eclipse-openj9#4530, the test needs to check a different algorithm. ibmruntimes/openj9-openjdk-jdk11#117 ibmruntimes/openj9-openjdk-jdk8#259 [ci skip] Signed-off-by: Peter Shipton <Peter_Shipton@ca.ibm.com>
Fixes are merged. |
Following the identification of issue eclipse-openj9/openj9#4530, updated the content to warn users that the Digest algorithm might cause a problem with this release. Signed-off-by: Sue Chaplain <sue_chaplain@uk.ibm.com>
Following the identification of issue eclipse-openj9/openj9#4530, updated the content to warn users that the Digest algorithm might cause a problem with this release. Signed-off-by: Sue Chaplain <sue_chaplain@uk.ibm.com>
Following the identification of issue eclipse-openj9/openj9#4530, updated the content to warn users that the Digest algorithm might cause a problem with this release. Signed-off-by: Sue Chaplain <sue_chaplain@uk.ibm.com>
I'm seeing this as a regression in: using the docker image: adoptopenjdk/openjdk8-openj9 |
@ashbm5 can you please investigate #4530 (comment) @ibm-rtvs can you please open a new issue. Until we have one, I'll reopen this one as a reminder. |
@vij-singh fyi |
@pshipton are there instructions how can this issue be reproduced? stacktrace? the test put in place to check for this issue is passing |
In the absence of a test case, or contact with @ibm-rtvs to get more information, there isn't much we can do. |
Perhaps not the same, but we do have #5611 opened. |
Note the crash reported by ibm-rtvs occurred from the "Finalizer thread".
|
Native stack is
@ashbm5 |
The MessageDigest native crypto has been disabled in the 0.14.2 release branches. |
MessageDigest native crypto has been disabled in master. |
The text was updated successfully, but these errors were encountered: