Closed Bug 1045102 Opened 10 years ago Closed 10 years ago

[e10s] Double HTTP redirects (e.g. Twitter short URLs) hang browser: Assertion (!DispatchingUrgentMessage()) failed. sync messages forbidden while handling urgent message

Categories

(Core :: Networking: HTTP, defect)

30 Branch
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 1041457
Tracking Status
e10s + ---

People

(Reporter: cpeterson, Unassigned)

Details

(Keywords: hang)

STR:
1. Enable e10s
2. Load http://www.johndcook.com/blog/2014/07/28/software-development-becoming-less-mature/
3. Page loads without any problems.

4. Load http://ow.ly/zEY8x
5. The ow.ly link redirects to the johndcook.com page without any problems.

6. Load http://t.co/HKL1viEUBs
7. The t.co links tries to redirect to the ow.ly link

RESULT:
HANG!

###!!! [MessageChannel][Child][/builds/slave/m-cen-osx64-ntly-0000000000000/build/ipc/glue/MessageChannel.cpp:585] Assertion (!DispatchingUrgentMessage()) failed.  sync messages forbidden while handling urgent message 
  MessageChannel 'backtrace':
  [(0) out sync PScreenManager::Msg_ScreenForBrowser(actor=-5) ]
  [(1) out sync PScreenManager::Msg_ScreenForBrowser(actor=-5) ]
  remote Interrupt stack guess: 0
  deferred stack size: 0
  out-of-turn Interrupt replies stack size: 0
  Pending queue size: 16, front to back:
    [ async ]
    [ async ]
    [ async ]
    [ async ]
    [ async ]
    [ async ]
    [ async ]
    [ async ]
    [ async ]
    [ async ]
    [ async ]
    [ async ]
    [ async ]
    [ async ]
    [ async ]
    [ async ]
[Child 46456] ###!!! ABORT: sync messages forbidden while handling urgent message: file /builds/slave/m-cen-osx64-ntly-0000000000000/build/ipc/glue/MessageChannel.cpp, line 1739
Blocks: 950745
No longer blocks: core-e10s
Summary: [e10s] Double short-URL HTTP redirect hangs browser: Assertion (!DispatchingUrgentMessage()) failed. sync messages forbidden while handling urgent message → [e10s] Double HTTP redirects (e.g. Twitter short URLs) hang browser: Assertion (!DispatchingUrgentMessage()) failed. sync messages forbidden while handling urgent message
I think this is actually caused by bug 1002354. I'm going to dupe it to bug 1041457.
Blocks: 1002354
No longer blocks: 950745
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.