(In reply to Emilio Cobos Álvarez (:emilio) from comment #3) > This has never worked correctly. I only filed for tracking, really. I don't think it's terribly important to fix. Update, following up on this assessment from 3 years ago -- nowadays we have some crash volume that we believe to be associated with this issue, making it somewhat more important to fix. Looking at the last month of bug 1793410's crash volume: nearly half of them (28 out of 62) have `MOZ_CRASH Reason (Raw)` set to `Element state change during style refresh (3072)`. The numeric value `3072` there is `1<<10 | 1<<11` which is the bit pattern associated with our dupe-bug 1804806. So: when we fix this bug, we can expect it to address some or perhaps all of that `3072`-tagged crash volume from bug 1793410, i.e. as much as half of the crash volume there.
Bug 1651070 Comment 7 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 Emilio Cobos Álvarez (:emilio) from comment #3) > This has never worked correctly. I only filed for tracking, really. I don't think it's terribly important to fix. Update, following up on this assessment from 3 years ago -- nowadays we have some crash volume that we believe to be associated with this issue, making it somewhat more important to fix. Looking at the last month of bug 1793410's crash volume: nearly half of the crashes (28 out of 62) have `MOZ_CRASH Reason (Raw)` set to `Element state change during style refresh (3072)`. The numeric value `3072` there is `1<<10 | 1<<11` which is the bit pattern associated with our dupe-bug 1804806. So: when we fix this bug, we can expect it to address some or perhaps all of that `3072`-tagged crash volume from bug 1793410, i.e. as much as half of the crash volume there.