joerg1985
joerg1985
This might be related to the chrome processes not terminated propper e.g. related to the [--no-sandbox](https://issues.chromium.org/issues/42323783) arg or another chromedriver issue. @NicoIodice Could you switch to firefox to confirm this...
The chromedriver does only spawn chrom processes, so you could search for chrome inside the running processes. To confirm it is a java leak, you could create a memory histogram...
@jacklee1983 should be fixed with c82f92ea2fbfe3e390158d53fcb318da097f0518 could you test it with a nightly build?
@cgoldberg yes, will do so in future. in the past i only did PRs for bigger things.
@rgmz This is the annoying answer of developers, to annoying (and obviously) false positive matches in binary blobs.
@lsiepel i have rebased the branch and fixed the conflict.
@Tennessene the linked repo is not visible to me. Are you using a fat jar for your project? This might break the ServiceLoader.
The fat jar does break the ServiceLoader, you could exclude the v127 & v128 dependency to fix this. When a fat jar is build the files inside the META-INF folder...
@goneall is it possible to release RC3 or are there any tasks left?
@duncan-bayne Could you try to set `pageLoadStrategy` to `eager` and check the script does continue? If it does continue the browser is unable to load the page before the `session-timeout`...