This test case can also trigger a kernel panic (marking s-s). This was found on a Mac mini (Mid 2010) running MacOS 10.13.6.

I have attached the partially reduced test case. The constant kernel panics make it difficult to reduce further.

21|0|libsystem_kernel.dylib||||0x1cb66
21|1|libsystem_c.dylib|abort|||0x7f
21|2|libGPUSupport.dylib||||0x2118
21|3|GeForceTeslaGLDriver||||0x2dbf92
21|4|GeForceTeslaGLDriver||||0x2ddca7
21|5|GeForceTeslaGLDriver||||0x2dd934
21|6|libGPUSupport.dylib||||0x4e07
21|7|GLEngine||||0xff282
21|8|GLEngine||||0x1e125
21|9|XUL|<gleam::gl::ErrorReactingGl<F> as gleam::gl::Gl>::clear|hg:hg.mozilla.org/mozilla-central:third_party/rust/gleam/src/gl.rs:bc973d369db58faf254ddcef201089dc28e6d3be|94|0x1f
21|10|XUL|webrender::device::gl::Device::clear_target|hg:hg.mozilla.org/mozilla-central:gfx/wr/webrender/src/device/gl.rs:bc973d369db58faf254ddcef201089dc28e6d3be|3438|0xd
21|11|XUL|webrender::renderer::Renderer::draw_frame|hg:hg.mozilla.org/mozilla-central:gfx/wr/webrender/src/renderer.rs:bc973d369db58faf254ddcef201089dc28e6d3be|4254|0x23
21|12|XUL|webrender::renderer::Renderer::render_impl|hg:hg.mozilla.org/mozilla-central:gfx/wr/webrender/src/renderer.rs:bc973d369db58faf254ddcef201089dc28e6d3be|3461|0x1c
21|13|XUL|webrender::renderer::Renderer::render|hg:hg.mozilla.org/mozilla-central:gfx/wr/webrender/src/renderer.rs:bc973d369db58faf254ddcef201089dc28e6d3be|3205|0x5
21|14|XUL|wr_renderer_render|hg:hg.mozilla.org/mozilla-central:gfx/webrender_bindings/src/bindings.rs:bc973d369db58faf254ddcef201089dc28e6d3be|599|0x18
21|15|XUL|mozilla::wr::RendererOGL::UpdateAndRender(mozilla::Maybe<mozilla::gfx::IntSizeTyped<mozilla::gfx::UnknownUnits> > const&, mozilla::Maybe<mozilla::wr::ImageFormat> const&, mozilla::Maybe<mozilla::Range<unsigned char> > const&, mozilla::wr::RendererStats*)|hg:hg.mozilla.org/mozilla-central:gfx/webrender_bindings/RendererOGL.cpp:bc973d369db58faf254ddcef201089dc28e6d3be|155|0x16
21|16|XUL|mozilla::wr::RenderThread::UpdateAndRender(mozilla::wr::WrWindowId, mozilla::layers::BaseTransactionId<mozilla::VsyncIdType> const&, mozilla::TimeStamp const&, bool, mozilla::Maybe<mozilla::gfx::IntSizeTyped<mozilla::gfx::UnknownUnits> > const&, mozilla::Maybe<mozilla::wr::ImageFormat> const&, mozilla::Maybe<mozilla::Range<unsigned char> > const&)|hg:hg.mozilla.org/mozilla-central:gfx/webrender_bindings/RenderThread.cpp:bc973d369db58faf254ddcef201089dc28e6d3be|478|0xd
21|17|XUL|mozilla::wr::RenderThread::HandleFrameOneDoc(mozilla::wr::WrWindowId, bool)|hg:hg.mozilla.org/mozilla-central:gfx/webrender_bindings/RenderThread.cpp:bc973d369db58faf254ddcef201089dc28e6d3be|356|0x1d
21|18|XUL|mozilla::detail::RunnableMethodImpl<mozilla::wr::RenderThread*, void (mozilla::wr::RenderThread::*)(mozilla::wr::WrWindowId, bool), true, (mozilla::RunnableKind)0, mozilla::wr::WrWindowId, bool>::Run()|hg:hg.mozilla.org/mozilla-central:xpcom/threads/nsThreadUtils.h:bc973d369db58faf254ddcef201089dc28e6d3be|1237|0x1f
21|19|XUL|MessageLoop::RunTask(already_AddRefed<nsIRunnable>)|hg:hg.mozilla.org/mozilla-central:ipc/chromium/src/base/message_loop.cc:bc973d369db58faf254ddcef201089dc28e6d3be|442|0x13
21|20|XUL|MessageLoop::DeferOrRunPendingTask(MessageLoop::PendingTask&&)|hg:hg.mozilla.org/mozilla-central:ipc/chromium/src/base/message_loop.cc:bc973d369db58faf254ddcef201089dc28e6d3be|450|0x2e
21|21|XUL|MessageLoop::DoWork()|hg:hg.mozilla.org/mozilla-central:ipc/chromium/src/base/message_loop.cc:bc973d369db58faf254ddcef201089dc28e6d3be|523|0xb
21|22|XUL|base::MessagePumpDefault::Run(base::MessagePump::Delegate*)|hg:hg.mozilla.org/mozilla-central:ipc/chromium/src/base/message_pump_default.cc:bc973d369db58faf254ddcef201089dc28e6d3be|35|0xa
21|23|XUL|MessageLoop::Run()|hg:hg.mozilla.org/mozilla-central:ipc/chromium/src/base/message_loop.cc:bc973d369db58faf254ddcef201089dc28e6d3be|290|0x5
21|24|XUL|base::Thread::ThreadMain()|hg:hg.mozilla.org/mozilla-central:ipc/chromium/src/base/thread.cc:bc973d369db58faf254ddcef201089dc28e6d3be|192|0x8
21|25|XUL|ThreadFunc(void*)|hg:hg.mozilla.org/mozilla-central:ipc/chromium/src/base/platform_thread_posix.cc:bc973d369db58faf254ddcef201089dc28e6d3be|40|0x6
21|26|libsystem_pthread.dylib|_pthread_body|||0x154
21|27|libsystem_pthread.dylib|_pthread_start|||0x179
21|28|libsystem_pthread.dylib|thread_start|||0xd
21|29|XUL|std::__1::__deque_base<MessageLoop::PendingTask, std::__1::allocator<MessageLoop::PendingTask> >::clear()|/builds/worker/fetches/clang/include/c++/v1/deque|1195|0xf

Jeff - is this bug actionable?

Will need to track down hardware for reproducing this issue. Not as straight forward these days.

Hey Jim, This is a sec-high and looks like it got stalled when getting hardware became an issue. Can you find an owner to look at trying to repro this? If getting hardware is still a problem, just let me know. Thanks!

(Clearing the needinfo to Jeff since I'm sure he's got a ton of NIs that he's still working through since coming back.)

Hey Jeff, do you know if we have this hardware?

Hey Daniel, curious why you rated this a sec-high?

My guess is because of the kernel panics. It is very easy to trigger them.

According to the inventory we have a MacBook Pro that's of a similar vintage. I don't know how to find it in the Toronto office though. I also might have something at home but I don't know if I have a power adapter to drive it.

Tyson: are there any special repro steps? I've tried a 2014 MacBook Pro (not quite as old as yours) with macos 10.13.6 but didn't see any crashes. From your about:support page you don't seem to have any special prefs flipped. Is it just the ancient hardware failing? Or can you repro this on more than one machine?

Waiting on repo steps and trying to get a hold of hardware for testing.

(In reply to Daniel Veditz [:dveditz] from comment #9)

Tyson: are there any special repro steps?

No nothing special.

Is it just the ancient hardware failing?

I only have access to old macminis so that could be the case.

I have a similar era mbp that might be able to reproduce. I'll try to get it updated to 10.13

Jeff: were you able to set up your old hardware? Or should we just let this go as "INCOMPLETE"?

Not yet, getting there.

Since the bug is closed, the stalled keyword is now meaningless.
For more information, please visit auto_nag documentation.

Feel free to reopen it if you want to investigate it, but it feels like some kind of driver or hardware issue with ancient Mac minis is not going to be a high priority after a few months.