Metal renderer, simulator, EXC_BAD_ACCESS in gmscore::renderer::MetalEntity::SetRenderState [208593323]

Fixed

Bug

Status Update

No update yet.

Description

[Deleted User]

created issue #1

Dec 1, 2021 07:11PM

We enabled the metal renderer as a possible workaround to 208487158. In that configuration, we encountered another, quite different, EXC_BAD_ACCESS with the stacktrace attached.

We suspect this is also an issue of M1 Max GPU support.

macOS 12.0.1 (21A559)
Google Maps SDK for iOS version:6.0.0 beta
Hardware model: M1 Max
Xcode Version 13.1 (13A1030d)

-------------------------------------------------------------------
[1] You can fork

https://github.com/googlemaps/maps-sdk-for-ios-samples.git and modify it until it demonstrates the issue

metal_trace

95 KB

Download

Comments

ma...@google.com <ma...@google.com> Dec 2, 2021 01:01AM

Assigned to ma...@google.com.

ma...@google.com <ma...@google.com> #2Dec 2, 2021 08:38AM

Thank you for posting.

We have verified and logged this issue internally. Please note that we cannot give you any timelines, but you can star the issue to get notifications.

ha...@gmail.com <ha...@gmail.com> #3Dec 12, 2021 09:08PM

This is not fixed in 6.0.1 so far and makes the switch to Metal impossible for many users.

da...@glovoapp.com <da...@glovoapp.com> #4Jan 5, 2022 12:22PM

Also, there is an issue with OpenGL in iOS simulators (ios 14 and 15) when running in M1 macs, so if building fully native there is no way for a dev to run in the simulator (Both Metal and OpenGL crash)

[Deleted User] <[Deleted User]> #5Jan 31, 2022 12:52PM

Any deadline on when this is going to be fixed?

ta...@uber.com <ta...@uber.com> #6Mar 4, 2022 10:38PM

+1, bumping up so that this gets prioritized. Thanks.

ma...@google.com <ma...@google.com> #7Mar 9, 2022 04:33AM

Marked as fixed.

We greatly appreciate your patience.

The fix for this issue will be included in the next Maps SDK for iOS version, hence setting the status of it accordingly.

Thanks for working with us!

[Deleted User] <[Deleted User]> #8Mar 16, 2022 11:42AM

Next version of the SDK is not 6.1.0, right? Just tested and it seems that the issue is still present.

[Deleted User] <[Deleted User]> #9Mar 29, 2022 05:37PM

We continue to see this issue in 6.1.0-beta.

[Deleted User] <[Deleted User]> #10Mar 29, 2022 05:45PM

We continue to see this in issue in 6.1.1-beta.

[Deleted User] <[Deleted User]> #11Apr 4, 2022 01:50PM

Plans on fixing it?

ra...@google.com <ra...@google.com> #12May 6, 2022 08:48AM

Hello team,

The fix will be included in version 6.2.1 and will be released some time this month.

Apologies for the inconvenience.

ha...@gmail.com <ha...@gmail.com> #13May 11, 2022 08:07AM

This is not fixed for us:

 newLibraryWithFile:3581: failed assertion `filepath must not be nil.'

ei...@trafi.com <ei...@trafi.com> #14Jun 21, 2022 08:47AM

I can confirm that after upgrading to 6.2.1, enabling metal renderer it crashes with the same assertion:

newLibraryWithFile:4071: failed assertion `filepath must not be nil.'

macOS 12.4 on Intel
Xcode 13.4.1

Message last modified on Jun 21, 2022 02:11PM

la...@gmail.com <la...@gmail.com> #15Jul 11, 2022 08:36AM

Any update here? This should only be marked as "Fixed" if it is actually confirmed by the reporters. Thank you!

ch...@vegannorway.com <ch...@vegannorway.com> #16Jul 11, 2022 08:48AM

Has been working perfectly for me since 6.2.1.