GoogleCrashdumpUploader creates, but never destroy it's instance of
LibcurlWrapper. This is not a problem for some users of GoogleCrashdumpUploader
(Chrome) which (currently) create one instance of the crash reporter, use it,
and then terminate. However, if this ever changes then memory leaks would ensue.
Original issue reported on code.google.com by cmumford@chromium.org on 31 Mar 2014 at 5:42
Original issue reported on code.google.com by
cmumford@chromium.org
on 31 Mar 2014 at 5:42Attachments: