Bug 1713230 Comment 35 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

(Following up comment #23)

> So you're getting the 0x1be385f9 (aka 0xfffffff9/-7) context error, which means "out of memory". As I said in comment #19, my hunch is that these are more likely to happen the more pixels your graphics card is driving.

I now consider this hunch disproven -- at least with regard to these custom errors. I don't know where to go from here. I'll let you know if I think of something.
(Following up comment #23)

> So you're getting the 0x1be385f9 (aka 0xfffffff9/-7) context error, which means "out of memory". As I said in comment #19, my hunch is that these are more likely to happen the more pixels your graphics card is driving.

I now consider this hunch disproven -- at least with regard to this custom error. I don't know where to go from here. I'll let you know if I think of something.
(In reply to J. Ryan Stinnett [:jryans] (Use needinfo, replies may be slow) from comment #31)

> Today the crash [occurred again](https://crash-stats.mozilla.org/report/index/91704699-0767-4090-a6e4-54bbf0220317) without the external display, so we now know it's possible to trigger with and without the external display. For now, I'll reconnect the display.

(Following up comment #23)

> So you're getting the 0x1be385f9 (aka 0xfffffff9/-7) context error, which means "out of memory". As I said in comment #19, my hunch is that these are more likely to happen the more pixels your graphics card is driving.

I now consider this hunch disproven -- at least with regard to this custom error. I don't know where to go from here. I'll let you know if I think of something.

Back to Bug 1713230 Comment 35