Closed
Bug 1449120
Opened 7 years ago
Closed 4 years ago
Crash in IPCError-browser | PRemotePrintJob::Msg_ProgressChange Route error: message sent to unknown actor ID
Categories
(Core :: Printing: Output, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: philipp, Unassigned)
References
Details
(Keywords: crash)
Crash Data
This bug was filed from the Socorro interface and is
report bp-4b50422c-4dec-41f2-917b-f95c60180325.
=============================================================
these content crashes on windows are newly appearing since 59.0b12 - that's when bug 1432409 landed, so there's likely some relation there.
overall the signature is rather low volume currently accounting for 0.3% of content crashes in 60.0b.
![]() |
||
Comment 2•7 years ago
|
||
I'm not sure why the crashes are being labeled as having PRemotePrintJob::Msg_ProgressChange in their signatures, since it doesn't seem to appear in the stack of the crashing thread. Bob, have you seen that before? Or any thoughts on this bug in general?
Flags: needinfo?(jwatt) → needinfo?(bobowencode)
Comment 3•7 years ago
|
||
(In reply to Jonathan Watt [:jwatt] from comment #2)
> I'm not sure why the crashes are being labeled as having
> PRemotePrintJob::Msg_ProgressChange in their signatures, since it doesn't
> seem to appear in the stack of the crashing thread. Bob, have you seen that
> before? Or any thoughts on this bug in general?
The reported stacks are for the child process, the dump for the parent I checked is failing on Msg_ProgressChange for a non-existing actor.
My guess is that bug 1432409 removed the crashes for Msg_StatusChange and at least some of them go on to hit this and bump up the Msg_ProgressChange failures.
So, I guess we just need a similar extra guard in RemotePrintJobChild::OnProgressChange (maybe OnStateChange as well although I don't see any crashes for that).
At least until we can get rid of these nested event loops and properly clean up the lifetimes here.
It's difficult to know if that will sort this, but I don't think it can hurt.
The crash is fairly common on Beta so I guess we should see if it's working soon, even if we miss the uplift.
Flags: needinfo?(bobowencode)
Comment 4•4 years ago
|
||
Closing because no crashes reported for 12 weeks.
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•