This bug was filed from the Socorro interface and is report bp-fb849be6-ab85-485c-aa32-8ba0f0180321. ============================================================= Seen while looking at nightly crash stats - crashes started using 20180313100127: http://bit.ly/2HUPrsC. 57 crashes/12 installs. Possible regression range based on Build ID: https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=fdd1a0082c71673239fc2f3a6a93de889c07a1be&tochange=c56ef1c14a555023949ad727c86e3c2df995edd2 Possibly Bug 1444580? ni on emilio. Top 10 frames of crashing thread: 0 xul.dll static void mozilla::dom::`anonymous namespace'::ScriptLoaderRunnable::LoadingFinished dom/workers/ScriptLoader.cpp:667 1 xul.dll static void mozilla::dom::`anonymous namespace'::ScriptLoaderRunnable::DataReceivedFromCache dom/workers/ScriptLoader.cpp:1372 2 xul.dll static nsresult mozilla::dom::`anonymous namespace'::CacheScriptLoader::OnStreamComplete dom/workers/ScriptLoader.cpp:1865 3 xul.dll mozilla::net::nsStreamLoader::OnStopRequest netwerk/base/nsStreamLoader.cpp:108 4 xul.dll nsInputStreamPump::OnStateStop netwerk/base/nsInputStreamPump.cpp:708 5 xul.dll nsInputStreamPump::OnInputStreamReady netwerk/base/nsInputStreamPump.cpp:436 6 xul.dll nsInputStreamReadyEvent::Run xpcom/io/nsStreamUtils.cpp:102 7 xul.dll mozilla::ThrottledEventQueue::Inner::ExecuteRunnable xpcom/threads/ThrottledEventQueue.cpp:193 8 xul.dll mozilla::ThrottledEventQueue::Inner::Executor::Run xpcom/threads/ThrottledEventQueue.cpp:79 9 xul.dll nsThread::ProcessNextEvent xpcom/threads/nsThread.cpp:1040 =============================================================

I'm not familiar with this code at all, seems highly unrelated to bug 1444580. It's hitting a release assert: MOZ_RELEASE_ASSERT(mWorkerPrivate->PrincipalURIMatchesScriptURL()) It's more likely that baku's recent refactoring of WorkerRef and stuff is related. But not sure. Andrea, mind redirecting if you're not familiar with what's going on here?

CacheScriptLoader is used in ServiceWorker only. Moving the NI to bkelly.

We have a lead on this over in bug 1406547. Its likely the timing is more related to site changes than a build change.

:bkelly assigning this to you for now, if the lead doesn't pan out please update this ticket accordingly.