Closed Bug 594580 Opened 15 years ago Closed 15 years ago

e10s HTTP: fennec segfaults if closed while viewing HTML 5 video

Categories

(Core :: Networking: HTTP, defect)

x86_64
Linux
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME
Tracking Status
fennec 2.0+ ---

People

(Reporter: jduell.mcbugs, Unassigned)

References

Details

(Whiteboard: resolve me, Nov 5)

cjones discovered this. Here's the video he used--any HTML 5 vid should do it. Just close while it's playing. http://double.co.nz/video_test/test2.html jdm: cjones was under impression you've been looking at this--true? Dies in child with very unhelpful stack in gbd, at least: #0 mozilla::ipc::RPCChannel::EnteredCxxStack (this=0x7fffb457aba0, that=..., direction=mozilla::ipc::RPCChannel::OUT_MESSAGE, msg=0x7fffb457ab60) at ../../dist/include/mozilla/ipc/RPCChannel.h:220 #1 CxxStackFrame (this=0x7fffb457aba0, that=..., direction=mozilla::ipc::RPCChannel::OUT_MESSAGE, msg=0x7fffb457ab60) at ../../dist/include/mozilla/ipc/RPCChannel.h:273 Cannot access memory at address 0x7fffb457ab48
tracking-fennec: --- → ?
The crash I spent a bit of time looking at was bug 592666, which was a very different stack. I'd be interested in seeing what |p *this| shows in gdb, here.
tracking-fennec: ? → 2.0+
can anyone reproduce this?
Whiteboard: resolve me, Nov 5
Cannot reproduce on Linux 32 GTK.
could be a race.
It used to be 100% reproducible. I no longer see an error at shutdown during video playback either. There are still some warnings, most of them common to any fennec shutdown, except these: NOTE: child process received `Goodbye', closing down ... ###!!! [Child][AsyncChannel] Error: Channel closing: too late to send/recv, messages will be lost ... WARNING: content process _exit()ing: file /home/jduell/central/t/dom/ipc/ContentChild.cpp, line 395 Not sure if these indicate anything we need to fix, or if we should just RESOLVE WORKSFORME.
Those messages are nothing special. I'd call this WFM.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.