[tenebrisalietum]

The screen memory is taking up so much RAM that it's overlapping with regions of memory the network interface uses.

[mjg59]

Resource are allocated via the kernel - it won't hand out overlapping address ranges.

[BalinKing]

Maybe the misbehaving driver is writing past the end of its requested space though, inadvertently? (I don't know if this is always called a "heap overflow" or if that's just Clang AddressSanitizer.)

[exikyut]

Or something like https://mjg59.dreamwidth.org/11235.html is happening.

[mjg59]

That resulted in a wide variety of different failures, from the kernel oopsing to various userspace components crashing. It would be very unusual to have unexpected DMA trigger such a specific failure.

(for avoidance of doubt, I wrote that blog post)