Regression? Just updated to this build before the quoted crash happened. (Jan Andre Ikenmeyer [:darkspirit] from bug 1374622 comment 19) > Nightly 58 x64 20170929220356 de_DE @ Debian Testing (KDE/Radeon RX480) > gpu process + layers force accel + webrender (layersfree) + webrendest + > blob-images > > https://techcrunch.com/2017/09/29/its-time-to-give-firefox-another-chance/ > > Crash just by scrolling down that page. (It doesn't scroll, flickers once > and I see a new crash report.) > > > MOZ_CRASH Reason: Should have been allocated by now! > > Meldungs-ID Sendedatum > bp-baa670e2-9476-46e6-9526-3341b0170930 30.09.17 03:47 > bp-ba22b174-be56-456d-b330-f6ada0170930 30.09.17 03:47 > bp-7604ccd3-606f-4507-934c-330200170930 30.09.17 03:45 > bp-844be0bb-0909-4362-90e1-a499a0170930 30.09.17 03:45 > bp-d27af249-3f0c-4cc5-b069-34a0e0170930 30.09.17 03:45 > bp-53e5f131-3d96-44df-b453-cecc60170930 30.09.17 03:44 > bp-06e9f98d-14d5-42af-b1e8-d7a710170930 30.09.17 03:44 > bp-81c10756-341c-43ab-a9fc-aac620170930 30.09.17 03:44 > bp-8ff68042-1ad7-4beb-8e1a-061cf0170930 30.09.17 03:44 Also seen on Youtube. bp-2efef380-bb5d-4bbc-82f4-209990170930 30.09.17 04:09 bp-8fdcbdb4-a25c-4658-8c3d-16bdf0170930 30.09.17 04:09 bp-66dd8455-5eb9-4d14-b9f4-2016a0170930 30.09.17 04:09 bp-ce516f67-b4e5-41d9-8ab0-dc14b0170930 30.09.17 04:09 bp-61b44d31-65e2-4031-beeb-ceccc0170930 30.09.17 04:08 bp-7dce57ec-c0b7-4d6b-a366-785150170930 30.09.17 04:08 bp-1bbf652e-26dc-47c6-ba0b-8270b0170930 30.09.17 04:08

layers.acceleration.force-enabled;true layers.gpu-process.enabled;true layers.gpu-process.force-enabled;true layers.gpu-process.max_restarts;1000 gfx.webrender.blob-images;true gfx.webrender.enabled;true gfx.webrendest.enabled;true Visited https://techcrunch.com/2017/09/29/its-time-to-give-firefox-another-chance/ and scrolled down. If it flickerd white and didn't scroll, it was a bad build. > mozregression --good 2017-09-28 --bad 2017-09-30 --profile-persistence clone-first > [...] > 10:32.75 INFO: Last good revision: e365cc4aa8f1d3d7bfc6ace91522896cbaf3741a > 10:32.75 INFO: First bad revision: 754da8e698978a5d21542fd1f35ac250c2768077 > 10:32.75 INFO: Pushlog: > https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=e365cc4aa8f1d3d7bfc6ace91522896cbaf3741a&tochange=754da8e698978a5d21542fd1f35ac250c2768077 May be this one: > Bug 1402321 - Update webrender to commit 9c5f8682e75839ad8c26480b89f87bbb37aa7894. r=jrmuizel I had to manually "skip" some builds that wanted to start in "Safe Mode". If I do not skip and type "bad" I get > 5:27.11 INFO: Last good revision: e365cc4aa8f1d3d7bfc6ace91522896cbaf3741a > 5:27.11 INFO: First bad revision: 13e8329439654bbf9c888d37c6abb342d114a8cd > 5:27.11 INFO: Pushlog: > https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=e365cc4aa8f1d3d7bfc6ace91522896cbaf3741a&tochange=13e8329439654bbf9c888d37c6abb342d114a8cd which doesn't make sense.

Windows: [@ core::option::expect_failed | webrender::frame_builder::FrameBuilder::build ] Seen on Socorro: 20170919100405 bp-17bae8fe-5409-4422-8d88-b5ae50170919 > MOZ_CRASH Reason Each render task must allocate <= size of one target! (1258×24) = old "see also" bug Then no crash for about 10 days. Spike since yesterday: 20170929220356 bp-337d5081-7f3d-4650-816a-222bb0170930 > MOZ_CRASH Reason Should have been allocated by now!

Oh, there is a second new crash reason: bp-d57f94a9-6b05-4724-b652-0bc390170930 (my Debian Testing) > MOZ_CRASH Reason handle not requested or allocated!

Pretty sure that's https://github.com/servo/webrender/issues/1779

I'm running into this issue over and over while scrolling through https://www.washingtonpost.com/news/post-nation/wp/2017/09/30/trump-called-san-juans-mayor-a-weak-leader-heres-what-her-leadership-looks-like/ bp-6e39c949-eab4-4840-958c-21ca30170930 bp-f29657a7-d92a-42b9-af02-7af4a0170930 bp-756a64a4-458e-4c37-9ae8-a07a00170930 bp-d4db3dd9-24ff-4191-8a4c-9fbcd0170930 bp-57160111-53e1-448d-bf5c-84e870170930 bp-d6c2263c-35a3-4a3c-aa4f-55ad50170930 ran mozregression and came up with: 13:17.98 INFO: Last good revision: 13e8329439654bbf9c888d37c6abb342d114a8cd 13:17.98 INFO: First bad revision: 53da1770ecd10b289fdaddc199431c94b415aaca 13:17.98 INFO: Pushlog: https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=13e8329439654bbf9c888d37c6abb342d114a8cd&tochange=53da1770ecd10b289fdaddc199431c94b415aaca

Leaving 58 unaffected only because WebRender is off by default.

This is the #3 Windows topcrash in Nightly 20171002100134, with 81 occurrences.

Just landed a WR update that should fix at least some of these (the chosen signature is so generic that it covers almost every crash in processing the display list). Should show up in the next nightly.

(In reply to Jan Andre Ikenmeyer [:darkspirit] from comment #0) > > Nightly 58 x64 20170929220356 de_DE @ Debian Testing (KDE/Radeon RX480) > > gpu process + layers force accel + webrender (layersfree) + webrendest + blob-images > > > > https://techcrunch.com/2017/09/29/its-time-to-give-firefox-another-chance/ > > > > Crash just by scrolling down that page. (It doesn't scroll, flickers once and I see a new crash report.) Nightly 58 x64 20171003220138 (includes bug 1403971, Tue Oct 03 20:25:55 2017 +0000) de_DE @ Debian Testing. At least this STR (+ gpu process crash on transaction overview in my online banking) do not work for me anymore.

Last crashes with 20171003100226. My 20171003220138 (12 hours later) was fine (comment 9). Fixed by https://github.com/servo/webrender/issues/1779 / bug 1403971.

Verified: Last crash with build: 20171003100226. Thank you. The upstream fix was from Gankro, but this FIXED bug is (was) still unassigned.