Closed Bug 1263601 Opened 5 years ago Closed 5 years ago

crash in mozilla::ipc::FatalError | mozilla::dom::PContentParent::FatalError | mozilla::dom::PContentParent::Write

Categories

(Core :: DOM: Content Processes, defect, P3)

48 Branch
x86
Linux
defect

Tracking

()

RESOLVED WORKSFORME
Tracking Status
firefox45 --- unaffected
firefox46 --- unaffected
firefox47 --- unaffected
firefox48 --- affected

People

(Reporter: mboldan, Unassigned)

References

(Depends on 1 open bug)

Details

(Keywords: crash, regression, Whiteboard: [Linux only])

Crash Data

Attachments

(1 file)

This bug was filed from the Socorro interface and is 
report bp-ad8dbd55-09f3-41f3-8038-6d70f2160411.
=============================================================

Steps to reproduce:
1. Launch Firefox.
2. Set devtools.responsive.html.enabled pref to true.
3. Go to any web page (Eg. ebay.com).
4. Enable RDM tool.
5. Take a series of screenshots.
6. Go to the Download folder and delete the screenshots.

Expected results:
The screenshots are deleted.

Actual results:
The screenshots are deleted and the FF crashes.

Notes:
1. More reports: https://crash-stats.mozilla.com/report/list?product=Firefox&signature=mozilla%3A%3Aipc%3A%3AFatalError+%7C+mozilla%3A%3Adom%3A%3APContentParent%3A%3AFatalError+%7C+mozilla%3A%3Adom%3A%3APContentParent%3A%3AWrite#tab-reports
2. I was unable to reproduce this issue on Windows 7 x 64 or on Mac OS X 10.10.4.
3. Also, I tried to crash FF by downloading files from http://www.thinkbroadband.com/download/ without success.
Whiteboard: [multiviewport] [triage]
Flags: qe-verify+
Priority: -- → P3
Whiteboard: [multiviewport] [triage] → [multiviewport] [reserve-rdm]
I have a hunch this might be fixed by the changes in bug 1263515 (or a related IPC bug).  :mboldan, could you retest with tomorrow's build (20160412) which should hopefully include the changes from bug 1263515?
Flags: needinfo?(mihai.boldan)
Attached video crash RDM.mp4
(In reply to J. Ryan Stinnett [:jryans] (use ni?) from comment #1)
> I have a hunch this might be fixed by the changes in bug 1263515 (or a
> related IPC bug).  :mboldan, could you retest with tomorrow's build
> (20160412) which should hopefully include the changes from bug 1263515?

The crash is still reproducible on FF 48.0a1 (2016-04-12) and on Ubuntu 14.04 x86.
As you can see in the attached video, the crash is not reproducible 100%.
Let me know if I can provide you any more information.
Flags: needinfo?(jryans)
Flags: needinfo?(mihai.boldan)
I think that's all we need for now.  Thanks for the video, it makes the steps quite clear!
Flags: needinfo?(jryans)
I think the IPC team would have a better chance of making progress here.  Let's try moving this bug over there.
Component: Developer Tools: Responsive Design Mode → IPC
Product: Firefox → Core
To clarify for IPC team, when comment 0 step 4 says "4. Enable RDM tool.", you can do this by going to Tools menu -> Web Developer -> Responsive Design Mode.
Component: IPC → DOM: Content Processes
This is happening inside a call to mozilla::dom::ContentParent::MaybeInvokeDragSession().
Whiteboard: [multiviewport] [reserve-rdm] → [multiviewport] [reserve-rdm][Linux only]
IPCFatalErrorMsg is "NULL actor value passed to non-nullable param", but I'm not sure how that would happen from SendInvokeDragSession.
The stack suggests that this is a regression from bug 1256952 which has today been backed out. So this should be fixed now. Can someone confirm?
Depends on: 1256952
Keywords: regression
:mboldan, can you retest in tomorrow's Nightly?
Flags: needinfo?(mihai.boldan)
I've tested this issue on Firefox 49.0a1 (2016-05-06) and on Ubuntu 14.04 x86.
The crash is no longer reproducible.
Flags: needinfo?(mihai.boldan)
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WORKSFORME
Whiteboard: [multiviewport] [reserve-rdm][Linux only] → [Linux only]
Andrew, from your comments above, were you able to reproduce this? I am unable to with the regressing patch. There's a new patch in 1256952 which fixes other regressions but I'm not sure if it fixes this crash.

If it does still crash, would you be able to provide more details as to what is happening?
Flags: needinfo?(continuation)
Sorry, I was just looking at crash reports.
Flags: needinfo?(continuation)
You need to log in before you can comment on or make changes to this bug.