(In reply to Christian Holler (:decoder) from comment #57) > I already made a recommendation in comment 21. This should be fixed by the developers [...] It has nothing to do with TSan. It looks like the problematic allocation is coming from TSAN, not from Firefox, right? Googling for the message turns up other projects hitting the same issue, and some of the results mention huge allocations **from TSAN's race detector** specifically. I don't know that there's anything we can do on the Firefox/Gecko side to reduce the size of TSAN's own allocations. > or the test should be disabled. There's no specific one test that could be disabled here; it looks like this happens for lots of tests, per the bug title. It also apparently can happen before we've even launched a test, e.g. here during `Marionette DEBUG Waiting for initial application window`: https://treeherder.mozilla.org/logviewer?job_id=404646659&repo=mozilla-esr102&lineNumber=2316 ...though in most cases it seems to happen just after we've logged a `drawWindow` call, i.e. it's usually associated with us taking a reftest snapshot (which isn't something that we can skip).
Bug 1770595 Comment 59 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Christian Holler (:decoder) from comment #57) > I already made a recommendation in comment 21. This should be fixed by the developers [...] It has nothing to do with TSan. It looks like the problematic allocation is coming from TSAN, not from Firefox, right? Googling for the message turns up other projects hitting the same issue, and some of the results mention huge allocations **from TSAN's race detector** specifically. I don't know that there's anything we can do on the Firefox/Gecko side to reduce the size of TSAN's own allocations. > or the test should be disabled. There's no specific one test (or set of tests) that could be disabled here; it looks like this happens for lots of tests, per the bug title. It also apparently can happen before we've even launched a test, e.g. here during `Marionette DEBUG Waiting for initial application window`: https://treeherder.mozilla.org/logviewer?job_id=404646659&repo=mozilla-esr102&lineNumber=2316 ...though in most cases it seems to happen just after we've logged a `drawWindow` call, i.e. it's usually associated with us taking a reftest snapshot (which isn't something that we can skip).