Try to avoid assumingMemoryBound. about aplay HOT 2 CLOSED

If you do want to return a typed pointer from malloc without initializing the memory (instead of using UnsafePointer.allocate) then:

malloc(size).bindMemory(to: UInt8.self, capacity: size)

from aplay.

I don't know what would cause SR-8248 and have not tried building or debugging your project.

You could try fixing any place in the code where you return an UnsafePointer from within the closure the receives the UnsafePointer as a closure argument. Those pointers are only valid within the closure body.

For example:

       let bytePtr = withUnsafePointer(to: &bigEndian) {
            $0.withMemoryRebound(to: UInt8.self, capacity: count) {
                UnsafeBufferPointer(start: $0, count: count)
            }
        }
        return Array(bytePtr)

You could write it safely like this:

  return withUnsafeBytes(of: i) {
    Array($0)
  }

Also, try not to use assumingMemoryBound anywhere (that's unlikely to be the cause of your bug today, but in future versions of the compiler will be more likely to break things).

from aplay.