DescriptionMake the toast more reliable and less dangerous
The current toast (re-activation) experiment suffers from the following problems:
1- False negative: the toast can be triggered even if chrome is being used
2- Nested message loop crash: If chrome tries to run while the toast is being shown, it crashes
This change addresses both conditions. Before running the toast we leverage the
process_singleton to detect another instance. If so we abort with "no thanks".
When showing the toast and its nested message loop we take the process_singleton lock which
inhibits dispatch of the wm_copydata message which spawns new tabs in the current process if
we try to span a new tab while in the nested message loop we crash.
BUG=32026
TES=see bug
Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=77214
Patch Set 1 #
Total comments: 4
Patch Set 2 : '' #
Messages
Total messages: 3 (0 generated)
|