BC7 Mipmap Problems in Catalina and Mojave

Question

dwn OP

Created Nov ’21

Replies 5

Boosts 0

Views 2.1k

Participants 3

I've run into two (possibly related) problems involving mipmaps in BC7 RGBA Unorm textures.

The first, and more serious, is a crash when uploading the last mipmap level of a texture. Thus far this has only happened on two machines, both running Catalina. Also, only certain textures cause the crash, but there doesn't seem to be anything unusual about them. From the crash reports:

MacOS 10.15.7 19H1519, Intel Graphics 4000 (this is from a debug, single-threaded build)

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   com.apple.driver.AppleIntelHD4000GraphicsMTLDriver	0x00007fff25cff33d CpuSwizzleBlt + 11667
1   com.apple.driver.AppleIntelHD4000GraphicsMTLDriver	0x00007fff25ce7ca0 -[MTLIGAccelTexture replaceRegion:mipmapLevel:slice:withBytes:bytesPerRow:bytesPerImage:] + 1387
2   com.apple.driver.AppleIntelHD4000GraphicsMTLDriver	0x00007fff25ce7e2f -[MTLIGAccelTexture replaceRegion:mipmapLevel:withBytes:bytesPerRow:] + 74

MacOS 10.15.7 19H1419, Intel Graphics 5000 (this is from a release, multi-threaded build)

Thread 9 Crashed:
0  com.apple.driver.AppleIntelHD5000GraphicsMTLDriver         0x00007fff2973b9c0 CpuSwizzleBlt + 9224
1  com.apple.driver.AppleIntelHD5000GraphicsMTLDriver         0x00007fff2972714b -[MTLIGAccelTexture replaceRegion:mipmapLevel:slice:withBytes:bytesPerRow:bytesPerImage:] + 1385
2  com.apple.driver.AppleIntelHD5000GraphicsMTLDriver         0x00007fff297272c3 -[MTLIGAccelTexture replaceRegion:mipmapLevel:withBytes:bytesPerRow:] + 64

I'll post the full crash reports to Feedback Assistant.

The second problem only happens on Mojave, and results in what looks like garbled pixel data in the mipmaps (I don't have access to the machine to do a frame capture). I can work around this issue by disabling mipmaps in the texture sampler.

There are no Metal validation errors, and neither problem happens on Big Sur (I don't yet have a Monterey machine). Uncompressed textures are fine, as well, although mipmaps for those are generated on-the-fly rather than uploaded.

Padding the source pixel data doesn't help, so the seg fault likely isn't caused by a too-large or unaligned read.

Has anyone else run into problems with mipmaps in BC7 compressed textures?

Boost

Answer 1

OP

Apple

Nov ’21

Hi dwn,

Thank you for filing a Feedback Assistant ticket with us! If you can post the ticket number here, I can route it to the driver team to investigate.

In the meantime, my recommendation is to verify sure that you are satisfying alignment and size requirements for the lowest mip level.

This is particularly important for compressed textures, where you still need to provide a full block at the lowest mip level, as well as maintain the alignment. For the specific case of BC7, you need to make sure the alignment is 16 bytes and that you provide Metal a whole block of size 16 bytes.

0

Answer 2

dwn OP

Nov ’21

I've now confirmed that the crash also happens using the texture loader from MetalKit. I've added a simple test application to the feedback ticket.

0

Answer 3

dwn OP

Sep ’22

This crash is still occurring in MacOS Monterey (12.1, 12.2 and 12.3.1). We've confirmed it with end users with Intel HD Graphics 4000, Intel HD Graphics 5000, and Intel Iris Pro. One such device is a Macbook Pro 15" from 2015.

I've updated the Feedback Assistant ticket as well.

0

Answer 4

Alecazam OP

Oct ’22

I use BC7 textures fine on Intel and M1 systems. But these are 2018 MBP with AMD and Intel parts.

One problem with KTX files is that each mip level has a 4 byte length. This messes up the upload of data, and Metal typically wants 16B alignment of each mip level. Metal validation should flag that.

If you are doing a memcpy then that may not be the issue. I was originally trying to mmap uncompressed ktx files when I hit this issue.

0

Answer 5

dwn OP

Oct ’22

Our mip levels are 16-byte aligned--each level is copied out of the KTX container before we use it. This crash seems to be specific to certain GPU and/or OS versions. We don't have this problem on any M1 system, or on most Intel systems.

The feedback assistant ticket has a very simple MetalKit project that shows off the error.

0