POST
|
Hey Prasad/Ryan, Sorry to hijack this thread but I've run into a similar issue and had some detailed repro cases that might be helpful. This was my workflow: Show view controller with AGSMapView in navigation controller (Location Display turned on) - Do not interact with the map view at all Push a new view controller on the navigation controller Click back to return to the map view controller At this point, if GPS is still on and the users location is offscreen, I will get a similar crash when I tap the map. However, if I pan the map first, then tap, I have no issues. As a workaround, I started shutting off the GPS before pushing the new view controller and that resolved my issues. It's been a while since I did that work but I did the exact test you described (removing layers), and the crash did not seem to correlate to any specific layer. I can run these tests again if it would be helpful. Here's another post I made when this first happened. The crash output was slightly different but the issue seemed to be the same. This frame buffer exception was consistent and repeatable but the _platform_memmove crash that Prasad was seeing was more intermittent for me. Both occurred when tapping on the map after returning from another view controller. Frame_buffer_OGL::init_ FAILED when tapping map Hope that is helpful. Chris
... View more
07-18-2016
09:23 AM
|
0
|
1
|
976
|
POST
|
It's really hard to say with that one error message. My only recommendation would be to turn the log level up on your server and see you can get some more information on the error.
... View more
07-18-2016
06:13 AM
|
0
|
0
|
296
|
POST
|
I get the same thing in a few scenarios. It seems to happen when I push or present a new view controller and usually only when I have GPS turned on. Have you found any solution to this?
... View more
07-14-2016
03:40 PM
|
0
|
1
|
976
|
POST
|
Thanks for the tip. We installed that patch a while back and it got us past that issue a number of times. I think we sorted out the problem we were having. It's been a few days now and no issues. We ended up having to wrap one of our definition expressions in parentheses. If we didn't, the query that was built to find the diffs on the server side was returning an invalid result set.
... View more
06-24-2016
12:54 PM
|
2
|
1
|
685
|
POST
|
I already posed this to the Server group but hoping I have more luck here - sorry for the crosspost! I'm running into a seemingly random issue with ArcGIS Server 10.3 where the synchronization process hangs without error. I have an iOS client (using the Esri SDK) and I'm using per-layer synchronization. The majority of the time, synchronization succeeds but occasionally, it gets into a state where it never finishes. I've kicked up server logging to DEBUG level and what I'm seeing is that at seemingly random times, the log messages for the sync process just stop. This often occurs when you wait a few days between syncs but we've also seen it happen immediately after generating and downloading a new replica. We've seen it occur at various times during layer processing for a number of different data sets. Once it happens, the replica will never sync and we have to wipe it out and generate a new one. For example, I started a sync today and this was the last message in the log for the process: Copying row with GlobalId: {F250C221-8896-4669-B60B-B58CBA4F0EB0} for dataset: T_58_Inserts. Dataset: T_58_Inserts. Replica: SDO.Ags_Fs_1464975077233. At other times, it will hang and the last message will be mention acquiring an archive cursor like so: Acquiring Archive Difference Cursor for dataset:... I watched the server process in windows task manager and at the point when synchronization hangs, the process hits 6% CPU usage and stays there indefinitely. I've run SQL Server Profiler and don't see any obvious errors or hung queries. My first thought is that the sync process has gotten into an infinite loop somehow - just a guess based on the CPU spike and the fact that there aren't clear database issues. Has anyone run into this? Any known issues? Thanks!
... View more
06-07-2016
11:41 AM
|
0
|
5
|
2960
|
POST
|
Have you seen this? 2282 - ArcGIS 10.3.1 for (Desktop, Engine, Server) Feature Service Sync Performance Patch It's for 10.3.1 but it did the trick for me and i had the same issue.
... View more
06-06-2016
07:50 PM
|
1
|
2
|
296
|
POST
|
I never found a solution to this one but after additional troubleshooting I was able to narrow it down to some unique circumstances. For whatever reason, when locationDisplay was enabled and the users location was off screen, the crash occurred when returning to my map view. I stripped out all layers but the basemap and the problem seemed to fix it self. So I worked around this by disabling GPS when navigation away from the view controller and reenabling when the user returned (probably not a bad practice anyway). That sort of did the trick but I still have an occasionally crash likely and I'm assuming that is because of some race condition. It's good enough for now but I might dig in some more in the future. Hope this helps anyone that runs into a similar issue.
... View more
06-06-2016
10:12 AM
|
0
|
0
|
468
|
POST
|
I'm running into a seemingly random issue with ArcGIS Server 10.3 where the synchronization process hangs without error. I have an iOS client (using the Esri SDK) and I'm using per-layer synchronization. The majority of the time, synchronization succeeds but occasionally, it gets into a state where it never finishes. I've kicked up server logging to DEBUG level and what I'm seeing is that at seemingly random times, the log messages for the sync process just stop. This often occurs when you wait a few days between syncs but we've also seen it happen immediately after generating and downloading a new replica. We've seen it occur at various times during layer processing for a number of different data sets. Once it happens, the replica will never sync and we have to wipe it out and generate a new one. For example, I started a sync today and this was the last message in the log for the process: Copying row with GlobalId: {F250C221-8896-4669-B60B-B58CBA4F0EB0} for dataset: T_58_Inserts. Dataset: T_58_Inserts. Replica: SDO.Ags_Fs_1464975077233. At other times, it will hang and the last message will be mention acquiring an archive cursor like so: Acquiring Archive Difference Cursor for dataset:... I watched the server process in windows task manager and at the point when synchronization hangs, the process hits 6% CPU usage and stays there indefinitely. I've run SQL Server Profiler and don't see any obvious errors or hung queries. My first thought is that the sync process has gotten into an infinite loop somehow - just a guess based on the CPU spike and the fact that there aren't clear database issues. Has anyone run into this? Any known issues? Thanks!
... View more
06-06-2016
10:05 AM
|
0
|
0
|
1475
|
POST
|
Correct - I was creating copies of the graphics and adding those the second mapView. I tried what you described and it had no effect. I went one step further, and didn't add any graphics to the second mapView and still got the crash. The maps don't share any layers at all and the second mapView is just a baseman and one graphics layer. I'll try to get a stripped down example in a new project and see if I can reproduce. Thanks for the quick reply Divesh Goyal
... View more
05-12-2016
10:44 AM
|
0
|
0
|
468
|
POST
|
I've run into a particular scenario that results in a crash with the following console output. I'm on the latest 10.2.5 SDK using Objective-C and iOS 9.3.1. Frame_buffer_OGL::init_ FAILED to create_ FramebufferName libc++abi.dylib: terminating with uncaught exception of type Esri_runtimecore::Common::Internal_error_exception: Internal error exception Here's the general reproduction case: Create a view controller (MapViewController) that includes an AGSMapView and set the mapView touch delegate to self (the crash still occurs without ever setting the touchDelegate). The map view also includes a sketch layer, AGSFeatureTableLayer and a few graphics layers. We create one graphic and add it to the map which is our 'selection' but does not use the selection mechanism/API provided with graphics layer. The user clicks a button to open a second view controller (without interacting with the map) to display details about that selected graphic. The new view controller (DetailViewController) is pushed on the navigation stack. This new view controller is a UITableViewController and it's headerView is a small AGSMapView that includes a basemap and a copy of the selected graphic. User interaction is disabled for this new map view and we show it only to provide context to the user. The user clicks a barButtonItem to pop the DetailViewController and return to the MapViewController. The user taps the map. Crash. I've done quite a bit of testing and the key to this seems to be that it only occurs when the user presents the DetailViewController before ever interacting with the mapView. Some other notes: I tried setting the touchDelegate to nil before DetailViewController is pushed to the navigation stack and it did not make a difference. I tried it without ever setting the touchDelegate and it still crashed. If I attempt to pan the map instead of clicking, it works fine and future click events register without a crash. Anyone have any thoughts/ideas/workarounds? Is this a known issue? Thanks!
... View more
05-12-2016
05:40 AM
|
0
|
3
|
3959
|
POST
|
When I couldn't get it to update properly I noticed that cocoapods.org only listed up to 10.2.5 so I assumed it wasn't updates. I ran that command and set the version to 10.2.5 in the podfile. Worked like a charm.
... View more
09-29-2015
10:00 AM
|
0
|
0
|
288
|
POST
|
I'm using cocoapods and as far as I can tell, it has not been updated for the 10.2.5 release. Is that correct? If so, will that be happening soon?
... View more
09-29-2015
05:29 AM
|
0
|
2
|
2424
|
POST
|
You're right - this is a spatial reference issue. The reason your two points are showing up in different locations is because one has the proper spatial reference and the other doesn't. As a general rule of thumb, when you have graphics randomly showing up off the west coast of Africa, this is likely the cause. If I understand correctly, it's the second point that you show above that does not work correctly. Try changing self.mapView.spatialReference to [AGSSpatialReference wgs84SpatialReference] like you used for the first point. That should do the trick.
... View more
04-30-2015
05:15 AM
|
0
|
0
|
333
|
Title | Kudos | Posted |
---|---|---|
3 | 07-10-2018 10:26 AM | |
2 | 06-24-2016 12:54 PM | |
1 | 06-06-2016 07:50 PM |
Online Status |
Offline
|
Date Last Visited |
11-11-2020
02:23 AM
|