user email claims:
"""
Chromedriver is leaking at precisely devtools_client_impl.cc:242.
The ResponseInfo object that is getting created here is never being garbage
collected.
"""
User workaround indicates that this may not be an actual leak -- i.e., we still
have references to the memory -- but that we're leaving stale entries in
response_info_map_.
Original issue reported on code.google.com by jbudorick@chromium.org on 8 Oct 2014 at 5:11
Original issue reported on code.google.com by
jbudorick@chromium.org
on 8 Oct 2014 at 5:11