1719684 - Crash in [@ mozilla::net::nsHttpChannel::SetupReplacementChannel] when navigating to cnn.com with the profiler running

Status: RESOLVED FIXED

(Core :: Gecko Profiler, defect)

Description

[Markus Stange [:mstange]]

Crash report: https://crash-stats.mozilla.org/report/index/108ce160-78ae-43f2-ae34-5e40d0210708

Reason: EXC_BAD_ACCESS / KERN_INVALID_ADDRESS

Top 10 frames of crashing thread:

0 XUL mozilla::net::nsHttpChannel::SetupReplacementChannel netwerk/protocol/http/nsHttpChannel.cpp:4982
1 XUL mozilla::net::nsHttpChannel::SetupReplacementChannel netwerk/protocol/http/nsHttpChannel.cpp:4981
2 XUL mozilla::net::nsHttpChannel::StartRedirectChannelToURI netwerk/protocol/http/nsHttpChannel.cpp:2778
3 XUL mozilla::net::nsHttpChannel::HandleAsyncAPIRedirect netwerk/protocol/http/nsHttpChannel.cpp:2712
4 XUL mozilla::detail::RunnableMethodImpl<mozilla::net::nsHttpChannel*, void  xpcom/threads/nsThreadUtils.h:1201
5 XUL mozilla::TaskController::DoExecuteNextTaskOnlyMainThreadInternal xpcom/threads/TaskController.cpp:805
6 XUL nsThread::ProcessNextEvent xpcom/threads/nsThread.cpp:1152
7 XUL NS_ProcessPendingEvents xpcom/threads/nsThreadUtils.cpp:431
8 XUL nsBaseAppShell::NativeEventCallback widget/nsBaseAppShell.cpp:87
9 XUL nsAppShell::ProcessGeckoEvents widget/cocoa/nsAppShell.mm:468

---

Steps to reproduce:

1. Start the profiler.
2. Open a new tab.
3. Enter cnn.com in the URL bar.
4. Press Enter.

Crash.

Comment 1

[Julien Wajsberg [:julienw]]

Fixed by backing out bug 1717047.
Thanks for reporting the bug!

Comment 2

[Julien Wajsberg [:julienw]]

The problem was caused by a redirection from https://c.amazon-adsystem.com/aax2/apstag.js to moz-extension://d6ceb57f-9f8d-488e-8fe9-a4e122be06b3/shims/apstag.js. Looks like moz-extension URLs aren't HttpChannel, who could have guessed? ;-)