-
Notifications
You must be signed in to change notification settings - Fork 142
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
Cause & solution for "inflater has been closed" exceptions found? #286
Comments
Might be a coincidence, but it seems to occur less when Connection: keep-alive header is removed? I remove it with Settings.builder().requestHeaders() by passing default CHROME ones but with "Connection" header removed. I'm also using a proxy. edit: fake news |
FOUND IT!
and it immediatelly started crashing, only 2/10 succeeded. Literally, these timeout settings somehow fix the whole problem. P. S. I'm testing with URL "https://accounts.google.com/signin/v2" |
This has been a longstanding issue and your info provides some excellent clues as to what the root cause might be. Anyone using Apache HttpComponents coming across this page from googling should take note. |
@hollingsworthd In this Method StreamConnection.getInputStream() you got the same Inputstream twice and open it |
@dlaske try fixing it, if it works, do a commit or post the fixed code here. I would very much appreciate it. These timeout settings of mine don't fix it 100% of the time, I still get it, but just little bit bigger success chance. |
I have the same problem, even assigning the timeout values. :/ |
I can't pinpoint the problem, but literally, one launch it's working 100% fine 10/10 no problem, 2nd launch (no code change) I get random "Inflater has been closed" exceptions. Anyone experienced it? Would love to keep using jBrowserDriver, but I gotta fix this
The text was updated successfully, but these errors were encountered: