This bug is for crash report bp-bf29640d-1a8e-47e3-82ec-d83f80191108.

Seen while looking at nightly crash stats - this one appears in 71 and 70 in small volume as well: https://bit.ly/2K3mn5p. Marking as sec sensitive due to possible UAFs in some of the signatures.

Comments:

• Saving as pdf from print menu caused crash

Top 10 frames of crashing thread:

0 libobjc.A.dylib NXMapRemove 
1 AppKit -[NSView buildLayerTreeWithOwnLayerRequirement:someAncestorWantsLayer:] 
2 AppKit -[NSView buildLayerTreeWithOwnLayerRequirement:someAncestorWantsLayer:] 
3 AppKit -[NSView buildLayerTreeWithOwnLayerRequirement:someAncestorWantsLayer:] 
4 AppKit -[NSView buildLayerTreeWithOwnLayerRequirement:someAncestorWantsLayer:] 
5 AppKit -[NSView buildLayerTree] 
6 AppKit NSViewBuildLayerTreeForDisplay 
7 AppKit -[NSWindow displayIfNeeded] 
8 AppKit __NSWindowGetDisplayCycleObserverForDisplay_block_invoke 
9 AppKit NSDisplayCycleObserverInvoke 

There's a small number of ESR 60/68 crashes, but of the fx70+ regression it looks like most are UAFs.

I also saw a crash report comment that talked about printing a page on a banking site, and the URL is for a banking site, so maybe a test case can be pulled out of that: bp-ed567908-1216-4bf6-baa6-1e9840191110

I was able to print the front page of that bank site without any issues on Nightly on OSX, FWIW.

I thought I had access to the comments in bug reports, but I don't seem to have access anymore (or not for this crash). How would I request access to those?

Here's an example of a recent bug requesting access: https://bugzilla.mozilla.org/show_bug.cgi?id=1568457
You have to file a bug like that, and get manager approval.

This is most likely another duplicate of bug 1596826.