-
Notifications
You must be signed in to change notification settings - Fork 0
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
browsermob proxy instance not starting every now and then because port is already taken #16
Labels
Comments
Looks like the locking mechanism doesn't work reliably enough if a lot of monitor tasks start in parallel. |
Needs to be cleanly solved via #14. |
Actually, it looks like a lot more ports are claimed by browsermob process than there are testcases:
(there are only 12 testcases, thus there should only be 1 master proxy process and 12 children processes) |
manuelkiessling
added a commit
that referenced
this issue
Jan 12, 2017
manuelkiessling
added a commit
that referenced
this issue
Jan 13, 2017
Seems solved with 9b94701. |
manuelkiessling
added a commit
that referenced
this issue
Jan 16, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
No description provided.
The text was updated successfully, but these errors were encountered: