FYI, https://chromium-review.googlesource.com/c/chromium/src/+/860617 just landed and Chrome should now be terminating itself before the end of main().This avoids subtle static uninitialization issues.
Please let me know if this causes any issues.We would like to move this termination even sooner : https://crbug.com/800808.PS: I would have like to do this in //content for all embedders to benefit but I couldn't since test frameworks hook ContentMain() and wouldn't be happy with process termination.Cheers!Gab
--
--
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/CAJTZ7LLOeYGiv-xSUZ6TtkRbgYGU2niU0gzOyv2tHMPMKVczPA%40mail.gmail.com.
On Mon, Jan 15, 2018 at 4:36 AM Gabriel Charette <g...@chromium.org> wrote:FYI, https://chromium-review.googlesource.com/c/chromium/src/+/860617 just landed and Chrome should now be terminating itself before the end of main().This avoids subtle static uninitialization issues.Shouldn't we be trying to get rid of static destructors anyway, even without this change?
PK
PK