Skip to content

Apple bug reports

Dzmitry Malyshau edited this page May 19, 2021 · 27 revisions

kvark:

  • 39726760: getting the maximum command buffer count supported by a queue
    • closed as fixed (the constructor now properly respects the given maximum)
    • but no actual query is added
  • 44665087: discard command buffers
    • use autorelease pool
  • 39939902: document thread safety
  • 40708496: overheating with GPU capture open
  • 40574782: viewport depth ranges
    • only affects macOS 10.13 and earlier on Intel GPUs
    • workaround provided
  • 40849018: depth copies
  • 40355147: format aliasing for texture copies
  • 40769756: slice aliasing for layered rendering
  • 40772035: rgba32 clears
  • 40918896: shader internal compiler error
    • fixed in 10.14
    • no workaround available, but it seems to mostly occur when using function constants in a particular way - may need to disable or heavily restrict usage of specialization constants in versions less than 10.14
  • 41773990: non-tracking command buffer still releases the resources used
  • 41852798: command buffer releases the tracked resources twice
  • 43471372: driver PSO caching effect on performance
  • 44082896: dual-source blending on Intel
  • 48871262: display stuttering with no v-sync
  • 48911699: multi-layer depth on NVidia
  • 6121407: memory stomp with MTLCaptureManager
  • 7469288: atomic operations are ignored in the fragment shader
  • FB7701997: depth testing not working
    • invalid test case, everything works properly otherwise
  • FB8247902: debug shaders linked with newLibraryWithSource
  • FB9051931: atan2(1, 0) weirdness

grovesNL:

  • 40476045: "cannot have global constructors (`llvm.global_ctors)" in compute
    • closed as duplicate of 35908470
    • should be available in macOS 10.14 beta
  • 40506294: querying support between feature sets/OS versions/how to know whether certain selectors such as buffers are available)
  • 40152566: clarification on copyFromBuffer 4-byte alignment
    • 1-byte aligned copies did not warn on certain devices
    • Apple states that these are not tested and may or may not succeed
  • 40302473: Metal validation enforces a pixel format to be set despite nil fragmentFunction and no color attachments/depth/stencil
  • 40244028: clarification on mipmapLevelCount for MTLTextureType1D in MTLTextureDescriptor
    • validation error states that 'MTLTextureDescriptor requests a mipmapLevelCount of 9 but the texture type MTLTextureType1D requires that mipmapLevelCount is 1 but the documentation does not seem to explicitly state this anywhere
  • 39726960: clarification on limits for newCommandQueueWithMaxCommandBufferCount
    • same as 39726760
  • 39822474: clarification on maximum texture size/how to query
    • textures larger than stated maximum buffer size are possible
  • 43707452: clarification of lodAverage macOS support
    • lodAverage isn't supported on macOS at all

Vulkan Portability subroup

Clone this wiki locally