[Tracking Requested - why for this release]: This bug was filed from the Socorro interface and is report bp-f7c2d2c6-a68a-46c6-ba7a-6b9432160503. ============================================================= On 46.0.1, for AMD CPUs, we've had a bunch of these crashes, all EXCEPTION_ACCESS_VIOLATION_WRITE crashes on the bad AMD CPUs. So far it's 5 crashes from 4 users. https://crash-stats.mozilla.com/signature/?product=Firefox&cpu_info=%5EAuthenticAMD+family+20+model+1&cpu_info=%5EAuthenticAMD+family+20+model+2&version=46.0.1&signature=nsIFrame%3A%3AGetUsedBorder#reports In all cases the EIP register ends with 0x124c, so they're all crashes at the same point. Based on the numbers so far it's not clear how bad a topcrash this is.

Tracking for 46 so we know to keep an eye on this crash once we get more data.

There are very few crashes matching this signature in recent builds, only 18 in the past 6 months for v60+. None of which are for "family 20". So I believe this issue has disappeared with the introduction of stylo. The remaining crashes seems Layout / Painting related, so we can handle them in bug 644696.