Should chrome_crashpad_handler honor --user-data-dir?

238 views
Skip to first unread message

Demetrios Tsillas

unread,
Apr 19, 2019, 9:19:07 AM4/19/19
to Chromium-dev
I noticed when running 74.0.3729.0 on mac that I get the following command line for the chrome_crashpad_handler process:

501  5056     1   0  8:57AM ??         0:00.02 /Volumes/Data0/jtsillas/Work/workspace1/src/out/Release/Viasat Browser.app/Contents/Versions/74.0.3729.0/Viasat Browser Framework.framework/Helpers/chrome_crashpad_handler --no-periodic-tasks --monitor-self-annotation=ptype=crashpad-handler --database=/Users/jtsillas/Library/Application Support/Viasat/Viasat Browser/Crashpad --annotation=channel=devbuild --annotation=plat=OS X --annotation=prod=Viasat Browser_Mac --annotation=ver=74.0.3729.0 --handshake-fd=4

The --database dir is the global dir used for my normal data.

But the command line to run:

501  5050   725   0  8:57AM ttys000    0:07.60 ./out/Release/Viasat Browser.app/Contents/MacOS/Viasat Browser --user-data-dir=/Users/jtsillas/74_user_data

Is this intentional?



Mark Mentovai

unread,
Apr 19, 2019, 10:12:03 AM4/19/19
to jtsi...@gmail.com, Chromium-dev
I thought we fixed this a long time ago (bug 565446), but that turns out to have been Windows-only. I filed bug 954491 for this. Thanks for the report.

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/9db4ca2a-aa1c-4f10-8a2b-873afedd4c3a%40chromium.org.

Demetrios Tsillas

unread,
Apr 19, 2019, 10:28:38 AM4/19/19
to Chromium-dev, jtsi...@gmail.com
Thanks for the quick response.

One related topic:

I am running browser_tests using --test-launcher-bot-mode and I see a chrome_crashpad_handler start for each test (not sure this is useful unless the test is testing crashpad, but whatever). Once in a while there is a problem where chrome_crashpad_handler processes are being left around. I suspect its because we have many of them running against the same database dir.

I'm hoping your upcoming fix will help with this.
Reply all
Reply to author
Forward
0 new messages