New issue
Advanced search Search tips

Issue 769837 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Oct 2
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: Bug



Sign in to add a comment

Disable StrictMode detectLeakedClosableObjects before calling OpenSslServerContext

Project Member Reported by kapishnikov@chromium.org, Sep 28 2017 
io.netty.handler.ssl.OpenSslServerContext(...) calls System.loadLibrary() that in certain circumstances (depends on classpath configuration) can cause intentional leak of a JarFile. This can cause a failure in BidirectionalStream tests if the tests are run with the StrictMode mode  enabled. For that reason, we should disable detectLeakedClosableObjects before calling OpenSslServerContext(...) and re-enable it afterwards. The method is called from Http2TestServer.

Internal b/66952708
Project Member

Comment 1 by sheriffbot@chromium.org, Oct 1

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 2 by mef@chromium.org, Oct 1 

Is it fixed? The internal b/66952708 is marked as fixed...

Comment 3 by pauljensen@chromium.org, Oct 2

Status: WontFix (was: Untriaged)
b/66952708 was worked around unfortunately.  I filed b/67413703 for the underlying Android bug, which was duped against another bug that is not yet fixed.  I guess we can close this Chromium bug as there isn't much we can do in Chromium other than continue to work around this until the underlying Android bug is fixed.
►

Sign in to add a comment