Thanks. Almost certainly a regression from bug 1300293, which touched the assertion that's failing here (moved it and promoted it from MOZ_ASSERT to NS_ASSERTION), in https://hg.mozilla.org/mozilla-central/rev/fc179320bf36cb2b398d4f49be817ece9562b100 Jason, would you mind testing to see whether you get a non-fatal version of this assertion before this range (`***ASSERTION: ` etc.)? It'd be good to know whether that range is where the assertion started failing vs. whether the assertion was already failing but simply became fatal (in the above-linked commit).
Bug 1576972 Comment 4 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Thanks. Almost certainly a regression from bug 1300293, which touched the assertion that's failing here (moved it and promoted it from MOZ_ASSERT to NS_ASSERTION), in https://hg.mozilla.org/mozilla-central/rev/fc179320bf36cb2b398d4f49be817ece9562b100 Jason, would you mind testing to see whether you get a non-fatal version of this assertion in a build from before your bisected range (`###!!! ASSERTION: ...` with the same message, rather than a fatal abort)? It'd be good to know whether that range is where the assertion started failing vs. whether the assertion was already failing but simply became fatal (in the above-linked commit).
Thanks. Almost certainly a regression from bug 1300293, which touched the assertion that's failing here (moved it and promoted it from MOZ_ASSERT to NS_ASSERTION), in https://hg.mozilla.org/mozilla-central/rev/fc179320bf36cb2b398d4f49be817ece9562b100 Jason, would you mind testing to see whether you get a non-fatal version of this assertion in a build from before your bisected range (`###!!! ASSERTION: ...` with the same message, rather than a fatal abort)? It'd be good to know whether that range is where the assertion **started failing** vs. whether that range is simply where an already-failing assertion became fatal (via the above-linked commit).
Thanks. Almost certainly a regression from bug 1300293, which touched the assertion that's failing here (moved it and promoted it from NS_ASSERTION to MOZ_ASSERT), in https://hg.mozilla.org/mozilla-central/rev/fc179320bf36cb2b398d4f49be817ece9562b100 Jason, would you mind testing to see whether you get a non-fatal version of this assertion in a build from before your bisected range (`###!!! ASSERTION: ...` with the same message, rather than a fatal abort)? It'd be good to know whether that range is where the assertion **started failing** vs. whether that range is simply where an already-failing assertion became fatal (via the above-linked commit).