To people seeing these crashes:
If you have a MacBook Pro, it may contain more than one kind of graphics hardware -- builtin "HD Graphics 4000" hardware plus something from a different vendor (perhaps AMD). If so, you may be able to avoid these crashes by forcing programs you run to use the other ("discrete") kind. One way to do this is to use [gfxCardStatus](https://gfx.io/).
Apple AMD drivers also have lots of bugs, and they can trigger crashes with signatures that are similar (though not identical) to those of this bug. But Apple's Intel drivers on macOS 10.15.7 build 19H1519 seem to be the worst of the worst. So you'll likely be better off if you can avoid using them.
Bug 1738289 Comment 16 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
To people seeing these crashes (on macOS 10.15.7 build 19H1519, with Intel graphics hardware):
If you have a MacBook Pro, it may contain more than one kind of graphics hardware -- builtin "HD Graphics 4000" hardware plus something from a different vendor (perhaps AMD). If so, you may be able to avoid these crashes by forcing programs you run to use the other ("discrete") kind. One way to do this is to use [gfxCardStatus](https://gfx.io/).
Apple AMD drivers also have lots of bugs, and they can trigger crashes with signatures that are similar (though not identical) to those of this bug. But Apple's Intel drivers on macOS 10.15.7 build 19H1519 seem to be the worst of the worst. So you'll likely be better off if you can avoid using them.