Post not yet marked as solved
I suggest you to read the comprehensive article "Optimizing Parallel Reduction in Metal for Apple M1" from Matthew Kieber-Emmons : https://kieber-emmons.medium.com/optimizing-parallel-reduction-in-metal-for-apple-m1-8e8677b49b01
You can use __fp16 or _Float16 data types.
__fp16 is not an arithmetic data type and should be used for storage purposes. It allows conversion from and to floats.
_Float16 is an arithmetic data type and have supports for standard operations.
_Float16 is more modern and a better choice. You can set a half constant with the f16 suffix following your real number.
Post not yet marked as solved
Thanks Ceylo, I'll give it a try, the next time I suspect such a situation!
If applicable, in the case I detect any remaining activity, could it be attached to a killed application?
An in this case, would it not be occuring below any monitoring?
Post not yet marked as solved
I have exactly the same error on a M1 Max (MacBook Pro 16") :
Execution of the command buffer was aborted due to an error during execution. Invalid Resource (00000009:kIOGPUCommandBufferCallbackErrorInvalidResource)
There is no crash, only a slowdown when the log is displayed.
Post not yet marked as solved
MTKView has a colorspace property. And to paraphrase Apple documentation :
The default value is nil, indicating that the rendered content isn’t color-matched. If you set this to a different color space, Core Animation performs any necessary color transformations when compositing the view’s contents.
Post not yet marked as solved
Sorry, I meant wantsExtendedDynamicRangeContent and not maximumExtendedDynamicRangeColorComponentValue
Post not yet marked as solved
And a direct construction of the CGImage via:
CGImageSourceRef imageSource = CGImageSourceCreateWithURL((CFURLRef)url, nil);
CGImageRef image = CGImageSourceCreateImageAtIndex(imageSource, 0, NULL);
contains 8bits components too...
Post not yet marked as solved
And finally, it seems that
CGImageRef cgImage = imageRep.CGImage;
destroys the original representation, as CGImageGetBitsPerComponent(cgImage) returns 8 (initially 10) and CGImageGetBitsPerPixel(cgImage) 32 (initially 40).
Post not yet marked as solved
I have the exact same annoying messages...
Thanks Dan!I'm glad to hear that...
> That's it: the root disk cannot be mounted, that’s why the installation fails. No root, no system, of course.That makes sense... But the boot process seems to have already started, and the external drive should already be accessible.> I wonder if that’s a bug or a deliberate behavior.There is no mention in the release notes, that Mojave beta installation on an external drive is not allowed.> Maybe you'd get a better answer if you filed a bug report?The bug reports rarely (never?) conduce to an explaination 😁Thanks again Ving-Cent...
After a video analysis of the screen just before the failure sign appears in verbose mode, the message is: "still waiting for root device".Same message in single user mode.
Thanks Vingt-Cent,I've just tried it. So, the last message that is displayed before the warning sign appears is approximately : "AppleUSBHostPort :: disconnect :: persistent enumeration failures". In fact, there is another line that is written just before the failure screen, but this last one makes the text over the screen totally unreadable.I launch the install on a MacBook Pro 1016 on an external SSD drive that is probably an USB-C one...
That's what I thought in the first place, but there is no such mention in the 10.14 release notes.
