Allow callers of CommandLine::Init to know whether they were the first caller.

Allow callers of CommandLine::Init to know whether they were the first caller.

If there are multiple callers to Init, only one should call Reset. The boolean return value tells the caller whether they are the one responsible for the destruction. As long as the lifetimes of clients are strictly nested (i.e., a client X who uses CommandLine after client Y has initialized it always ceases its use before client Y destroys it) this secures access to this singleton object.

One client in particular is updated to follow this model. I will submit follow-up CLs for remaining clients (at least, those who currently do call Reset).

This is motivated by a crash in the chrome_frame_net_tests. This test executable nests a TestSuite within the lifetime of a ContentMainRunner (i.e., the engine that is typically used to run Chrome). The content layer initializes CommandLine and Resets it, but the TestSuite also resets it, leading to a DCHECK. This is currently the last remaining issue keeping the chrome_frame_net_tests off the waterfall, and I am very eager to get them back there to reduce the likelihood of further issues being introduced.

BUG=114369
TEST=A test has been modified to reflect this change.


Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=123763

[erikwright (departed), 2012-02-27 15:03:55]

Hi Brett,

This is a bit of a high priority as it is the last thing keeping the Chrome
Frame net tests off the waterfall. As long as they are not there, new issues may
prevent them from getting back on.

Thanks,

Erik

[brettw, 2012-02-27 16:58:40]

lgtm

[commit-bot: I haz the power, 2012-02-27 17:00:29]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/erikwright@chromium.org/9477001/7

[commit-bot: I haz the power, 2012-02-27 18:38:15]

Change committed as 123763