Comment #2 on issue 31085 by craig.schlenter: Crash - UpdateManifest::ParseError() http://code.google.com/p/chromium/issues/detail?id=31085
I see that UpdateManifest::ParseError is calling va_start but never calls va_end. So does XmlErrorFunc and a couple of other places in the chromium code base. Do you want one big patch or a patch targeting this specifically and separate patches for the rest of the problems? Problem areas: chrome/common/extensions/update_manifest.cc x 2 chrome_frame/crash_reporting/vectored_handler_unittest.cc x 2 sandbox/linux/suid/sandbox.c (maybe not an issue since it calls exit) skia/ext/google_logging.cc views/examples/example_base.cc -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings -- Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs
