iOS 11 Simulator unusable slow

We are Unity developers and we are testing a very empty project in iPhoneX simulator (only display few images), CPU 100% usage and every click need 10s to response.....

Using:

Unity 5.6.3p4

Xcode 9.0 (9A235)

macOS 10.12.6

1.1Ghz Core m3 CPU

8GB RAM

Get Xcode 9.1beta2 from the member center.

I've been paying attention to this thread because I've had the problem with the iPhone X simulator being unusably slow under Xcode 9. Unfortunately I was not able to snag a copy of the beta that had a working version of libCoreVMClient.dylib, but I found that copying over the one from 9.1beta2 fixed the problem.

Today I updated to Xcode 9.0.1 and the problem was back in full force, despite "Simulator improvements for iPhone X" being mentioned in the release notes. I had to go back to the beta's copy of the .dylib file again to fix it.

I'm running Sierra 10.12.6 on a late 2011 MacBook Pro 17 inch.

I can confirm that Xcode 9.0.1 does NOT fix the issue. MKMapView still slow. Xcode 9.1 beta 2 DOES fix it.

While XCode 9.1 beta 2 at least allows mapkit to run at a reasonable speed, I'm still getting issues with the simulator generating dozens of console error messages as follows:

2017-10-23 21:40:29.867748+0100 XXXXX [9914:159503] [VKDefault] Tile 10556.25433.16 (128) in current unloaded state for 0.00 seconds - Raster Overlays Above Labels - Failed to decode (terminal) (0.00 sec)

This is extremely annoying because it's impossible to comb through my console output to get to debugging statements that I'm trying to review. Is anyone else having this problem? Any solutions?

I am seeing the same VKDefault Tile errors when running on a device, and the tile overlay on my map (which has worked fine for many years) is flashing like crazy -- all the tiles are being redrawn over and over endlessly. I think there has got to be a deeper bug in MapKit that is at play here.

XCode 9.1 was released, but it is a persistent problem: the simulator is slow even running iOS 10.3.1

Anyone still got this issue?

Even thought they adress the issue in the release notes?

After update to xcode 9.1, the simulator is still slow 😟

I concur. I just uploaded and installed Xcode Version 9.1 (9B55), and using Simulator Version 10.0 (SimulatorApp-835.2.1), the performance using MapKit is abysmally slow. This was supposed to be addressed:

• Fixed an issue in Simulator's OpenGL that could cause SceneKit apps to run slowly and the CPU to hit 100% when attempting to pan in an MKMapView.
• In Simulator, panning an

  MKMapView

  in a SceneKit app now works correctly. (33664759)

Hope it can be resolved soon!

This is expected. The fix did not make it into Xcode 9.0.1.

If you believe the Simulator should have GPU accelerated rendering I would encourage you to file radars requesting that. Please understand it is not up to me or my team; the best way to send feedback to the responsible team is to file radars.

Since there was a suggestion, from your team, on how to temp fix this issue. Could you provide the files needed? THere is no way to pull down Xcode 9 Beta 3 and I am still having the same exact issue in 9.1. Just only worse now.

As mentioned elsewhere, the issue no longer exists as of iOS 11.1 (which is in Xcode 9.1). If you are still having some issues with iOS 11.1, please file new radars.

Try pressing command + T.

Hi,

I'm still having issues with the MKTileOverlay. I'm running Version 9.2 (9C40b) and iOS 11.2.2 (15C202). If this issue have been solved. Is my problem something else?

2018-01-16 23:22:12.670943+0100 App[619:77452] Could not inset legal attribution from corner 4
2018-01-16 23:22:12.691675+0100 App[619:77452] Could not inset compass from edges 9
2018-01-16 23:22:12.691739+0100 App[619:77452] Could not inset scale from edge 9
2018-01-16 23:22:12.691865+0100 App[619:77452] Could not inset legal attribution from corner 4
2018-01-16 23:22:12.738091+0100 App[619:77452] Could not inset compass from edges 9
2018-01-16 23:22:12.738129+0100 App[619:77452] Could not inset scale from edge 9
2018-01-16 23:22:12.738234+0100 App[619:77452] Could not inset legal attribution from corner 4
2018-01-16 23:22:12.738637+0100 App[619:77452] Could not inset compass from edges 9
2018-01-16 23:22:12.738653+0100 App[619:77452] Could not inset scale from edge 9
2018-01-16 23:22:12.738695+0100 App[619:77452] Could not inset legal attribution from corner 4
2018-01-16 23:22:12.781050+0100 App[619:77548] [GEODBWriter] /BuildRoot/Library/Caches/com.apple.xbs/Sources/GeoServices/GeoServices-1359.32.9.1.19/GEODBWriter.mm:601 Could not open database (/var/mobile/Library/Caches/com.apple.geod/MapTiles/MapTiles.sqlitedb): (14) unable to open database file
2018-01-16 23:22:12.781617+0100 App[619:77548] [GEODBWriter] /BuildRoot/Library/Caches/com.apple.xbs/Sources/GeoServices/GeoServices-1359.32.9.1.19/GEODBWriter.mm:601 Could not open database (/var/mobile/Library/Caches/com.apple.geod/MapTiles/MapTiles.sqlitedb): (14) unable to open database fileApp2018-01-16 23:22:12.793628+0100 Shoota[619:77548] [logging] API called with NULL prepared statement
2018-01-16 23:22:12.793650+0100 App[619:77548] [logging] misuse at line 84098 of [2b0954060f]
2018-01-16 23:22:12.793655+0100 App[619:77548] [logging] API called with NULL prepared statement
2018-01-16 23:22:12.793659+0100 App[619:77548] [logging] misuse at line 84098 of [2b0954060f]
2018-01-16 23:22:12.793676+0100 App[619:77548] [logging] API called with NULL prepared statement
2018-01-16 23:22:12.793680+0100 App[619:77548] [logging] misuse at line 84098 of [2b0954060f]
2018-01-16 23:22:12.793684+0100 App[619:77548] [logging] API called with NULL prepared statement
2018-01-16 23:22:12.793700+0100 App[619:77548] [logging] misuse at line 84098 of [2b0954060f]App2018-01-16 23:22:12.793703+0100 Shoota[619:77548] [logging] API called with NULL prepared statement
2018-01-16 23:22:12.793707+0100 App[619:77548] [logging] misuse at line 83511 of [2b0954060f]
2018-01-16 23:22:12.793711+0100 App[619:77548] [GEODBWriter] /BuildRoot/Library/Caches/com.apple.xbs/Sources/GeoServices/GeoServices-1359.32.9.1.19/GEODBWriter.mm:437 SQL error: (21) out of memory
2018-01-16 23:22:12.808617+0100 App[619:77452] [VKDefault] Tile 34210.17884.16 (128) in current unloaded state for 0.00 seconds - Raster Overlays Above Labels - Failed to decode (terminal) (0.00 sec)
2018-01-16 23:22:12.808651+0100 App[619:77452] [VKDefault] Tile 34208.17884.16 (128) in current unloaded state for 0.00 seconds - Raster Overlays Above Labels - Failed to decode (terminal) (0.00 sec)
2018-01-16 23:22:12.808664+0100 App[619:77452] [VKDefault] Tile 34209.17884.16 (128) in current unloaded state for 0.00 seconds - Raster Overlays Above Labels - Failed to decode (terminal) (0.00 sec)
2018-01-16 23:22:12.808676+0100 App[619:77452] [VKDefault] Tile 34207.17884.16 (128) in current unloaded state for 0.00 seconds - Raster Overlays Above Labels - Failed to decode (terminal) (0.00 sec)
2018-01-16 23:22:12.808687+0100 App[619:77452] [VKDefault] Tile 34210.17882.16 (128) in current unloaded state for 0.00 seconds - Raster Overlays Above Labels - Failed to decode (terminal) (0.00 sec)
2018-01-16 23:22:12.808697+0100 App[619:77452] [VKDefault] Tile 34210.17883.16 (128) in current unloaded state for 0.00 seconds - Raster Overlays Above Labels - Failed to decode (terminal) (0.00 sec)
2018-01-16 23:22:12.808791+0100 App[619:77452] [VKDefault] Tile 34208.17882.16 (128) in current unloaded state for 0.00 seconds - Raster Overlays Above Labels - Failed to decode (terminal) (0.00 sec)

OpenGL was the only one that worked for me.

Could it be that this is a similar problem to here:

https://forums.developer.apple.com/thread/96511

??

Just a me too response. It's one thing to force Metal on us and deprecate OpenGL, another to criple the simulator.

Is it possible that this bug is still around 4 years later? I’m on Xcode 13 and the simulator is almost unusable. So painful.