New issue
Advanced search Search tips

Issue 713772 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Apr 2017
Cc:
rsesek@chromium.org
mark@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 3
Type: Bug



Sign in to add a comment

crashpad error messages

Project Member Reported by erikc...@chromium.org, Apr 20 2017 
Using Chromium on ToT: 1840bcd0f90cc5e22225ca37d3751c5f398ab2d0

[0420/102013.599709:ERROR:crash_report_database_mac.mm(619)] open lock /Users/erikchen/Library/Application Support/Chromium/Crashpad/completed/09e908cd-6797-4843-85a0-1242dd83a442.dmp: Resource temporarily unavailable
[0420/102013.600704:ERROR:crash_report_database_mac.mm(619)] open lock /Users/erikchen/Library/Application Support/Chromium/Crashpad/completed/1fdbf558-ee63-41dd-a786-c78184ca4c70.dmp: Resource temporarily unavailable
[0420/102013.601443:ERROR:crash_report_database_mac.mm(619)] open lock /Users/erikchen/Library/Application Support/Chromium/Crashpad/completed/2104ee9e-5084-4131-86eb-b53d50fca29c.dmp: Resource temporarily unavailable
[0420/102013.601803:ERROR:crash_report_database_mac.mm(619)] open lock /Users/erikchen/Library/Application Support/Chromium/Crashpad/completed/27de12c0-8f70-4add-9acf-7db6277165a8.dmp: Resource temporarily unavailable
[0420/102013.602592:ERROR:crash_report_database_mac.mm(619)] open lock /Users/erikchen/Library/Application Support/Chromium/Crashpad/completed/3e2b3fee-72fe-4055-9cbe-df262020e85b.dmp: Resource temporarily unavailable
[0420/102013.603288:ERROR:crash_report_database_mac.mm(619)] open lock /Users/erikchen/Library/Application Support/Chromium/Crashpad/completed/77bb9aaf-be96-4945-84cb-24867e338a3c.dmp: Resource temporarily unavailable
[0420/102013.603918:ERROR:crash_report_database_mac.mm(619)] open lock /Users/erikchen/Library/Application Support/Chromium/Crashpad/completed/7bdfc4ff-314e-4486-8303-caca2451fb77.dmp: Resource temporarily unavailable
[0420/102013.604303:ERROR:crash_report_database_mac.mm(619)] open lock /Users/erikchen/Library/Application Support/Chromium/Crashpad/completed/7c8a8e26-247a-4c2e-853e-0d51e34f9c2f.dmp: Resource temporarily unavailable
[0420/102013.605050:ERROR:crash_report_database_mac.mm(619)] open lock /Users/erikchen/Library/Application Support/Chromium/Crashpad/completed/7d13c2ac-74ad-454d-8b22-89d30c252fad.dmp: Resource temporarily unavailable
[0420/102013.605654:ERROR:crash_report_database_mac.mm(619)] open lock /Users/erikchen/Library/Application Support/Chromium/Crashpad/completed/7e2cb494-f7e0-4b85-8518-89255f8a2298.dmp: Resource temporarily unavailable
[0420/102013.606023:ERROR:crash_report_database_mac.mm(619)] open lock /Users/erikchen/Library/Application Support/Chromium/Crashpad/completed/801ac8d5-23c8-4511-a81b-c3ae3fb46274.dmp: Resource temporarily unavailable

Comment 1 by mark@chromium.org, Apr 20 2017

Cc: rsesek@chromium.org
These should be harmless, something else was probably using the database at the same time.

But this isn’t a great crash report because it just says “error messages” and contains a dump of a bunch of error messages. Can you say what you were doing? Did you recently start Chrome? Did you visit about:crashes? Did something crash? Were any other Chromes running? Help us out.

Comment 2 by erikc...@chromium.org, Apr 20 2017 

I've been doing some testing on ToT. I regularly kill with Ctr-C from command line, rather than shutting down correctly. That being said, I wasn't doing anything at all other than just opening Chrome and letting it sit for a while. [otherwise clean profile, no navigations].

Comment 3 by mark@chromium.org, Apr 20 2017 

This should be a bit less likely after Crashpad 8297b19a5e85, in Chrome at 22d1fa7cd581. That just landed two days ago, do you have it yet?

Comment 4 by erikc...@chromium.org, Apr 20 2017

Status: WontFix (was: Untriaged)
Nope. I can reopen if I see the issue post patch.

Comment 5 by mark@chromium.org, Apr 20 2017 

Cool. That‘s almost definitely it. Before that change, you’d get two crashpad_handlers on just about the same schedule, and they’d both try to do the database purge (which is what it appears they were trying to do in your case) at just about the same instant.
►

Sign in to add a comment