Can anyone here confirm or deny that the newest versions of tensorflow-metal are free of this issue? Reading back in this thread, the problem seems to first appear in version 0.5.0 and reportedly disappears starting in 0.8.0- but I'd really appreciate it if any additional people can confirm that.
Thanks.
wbattel4607
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Last seen
User for
Post
Replies
Boosts
Views
Activity
This problem is brutal. We want to purchase new Apple Silicon Macs but cannot in the face of such a glaring problem. I hope Apple realizes how big of an issue this is and resolves it soon.
Can anyone confirm if this problem persists on tensorflow-metal version 0.7.0?