1612807 - [Web Replay] Crash in [@ IPCError-browser | CommitFromIPC Invalid Transaction from Child]

Status: RESOLVED WORKSFORME

(Core Graveyard :: Web Replay, defect, P2)

Description

[Gabriele Svelto [:gsvelto]]

This bug is for crash report bp-6dc07980-97ef-409e-acf3-7cbc20200131.

Top 10 frames of crashing thread:

0 XUL void mozilla::ipc::MessageChannel::Send<mozilla::Tuple<mozilla::Maybe<base::FileDescriptor>, unsigned int> > ipc/glue/MessageChannel.h:221
1 XUL mozilla::ipc::IdleSchedulerChild::Init ipc/glue/IdleSchedulerChild.cpp:42
2 XUL mozilla::IdlePeriodState::RequestIdleToken xpcom/threads/IdlePeriodState.cpp:182
3 XUL mozilla::IdlePeriodState::GetIdleDeadlineInternal xpcom/threads/IdlePeriodState.cpp:91
4 XUL mozilla::ThreadEventQueue<mozilla::PrioritizedEventQueue>::GetEvent xpcom/threads/IdlePeriodState.h:71
5 XUL nsThread::ProcessNextEvent xpcom/threads/nsThread.cpp:1141
6 XUL <name omitted> xpcom/threads/nsThreadUtils.cpp:486
7 XUL mozilla::ipc::MessagePump::Run ipc/glue/MessagePump.cpp:87
8 XUL MessageLoop::Run ipc/chromium/src/base/message_loop.cc:290
9 XUL nsBaseAppShell::Run widget/nsBaseAppShell.cpp:137

macOS-only crash, the oldest report we have on file is for buildid 20200121093246. The stacks don't seem to make any sense but after our recent discussion during the crash reporting meeting I suppose that's expected when hitting certain IPC crashes :-/.

Comment 1

[Andrew McCreight [:mccr8]]

These crashes all have WebReplay enabled. I'm not sure if there's a bug on file for this crash or not. The WebReplay component is in some kind of semi-shut down state.

Comment 2

[Gabriele Svelto [:gsvelto]]

There is a Core > Web Replay component but somehow it doesn't show up in the drop-down when I edit the bug. In the light of bug 1609815 I don't think there's much we can do here, should we close this as WONTFIX?

Comment 3

[Andrew McCreight [:mccr8]]

(In reply to Gabriele Svelto [:gsvelto] from comment #2)

There is a Core > Web Replay component but somehow it doesn't show up in the drop-down when I edit the bug.

That's due to bug 1610077 comment 0.

In the light of bug 1609815 I don't think there's much we can do here, should we close this as WONTFIX?

I'd like to wait for the removal to land, and then we can double check that all of these crashes go away.

Comment 4

[Andrew McCreight [:mccr8]]

Emma, could you please move this to the WebReplay component? Thanks.

Comment 5

[Emma Humphries ☕️🎸🧞‍♀️✨ (she/they) [:emceeaich] (Pacific Time) use needinfo]

Since WebReplay is not actively maintained in-tree, this bug should be moved to https://webreplay.org/'s bug tracker.

Comment 6

[Emma Humphries ☕️🎸🧞‍♀️✨ (she/they) [:emceeaich] (Pacific Time) use needinfo]

Oh, wait, we want to make sure the crash goes away. Sorry. Because WebReplay is not open to new bugs, moving to Core::General.

Comment 7

[Anthony Jones (:ajones, :kentuckyfriedtakahe, :k17e)]

Jan - what do you want to with this bug?

Comment 8

[Jan Honza Odvarko [:Honza] (always need-info? me)]

Jason is working on this - assigned to him.

Comment 9

[BugBot [:suhaib / :marco/ :calixte]]

The priority flag is not set for this bug.
:aklotz, could you have a look please?

For more information, please visit auto_nag documentation.

Comment 10

[Andrew McCreight [:mccr8]]

The WebReplay frontend has been removed, and these crashes went away around that same time.