POST
|
Hi Michael, This is good news - pleased we can help identify a bug . So for our LoB application we're doing a couple of things - we've got two builds running in debug mode, one with FeatureLayers related code disabled and one with GraphicsOverlays relate code disabled. Overnight the build with GraphicsOverlays related code disabled didn't crash and the build with the FeatureLayers disabled did crash overnight with the same issue. We're now focusing on which specific GraphicsOverlays layer - we have 4 being used in our app, other Fire Appliance(s) position, Buildings, Route Line (network dataset), current Location Marker & Destination Marker). If we're able to pin point a specific GraphicsOverlays which is giving us the trouble we can then possibly look at workarounds? - with respects to the future fix, is there a chance of a hotfix? If not and we can't do a workaround we'll need to drop back to 100.4 (assuming 100.5 has this same issue). Appreciate your help on this matter. Thanks Bryan
... View more
10-15-2019
12:45 PM
|
0
|
0
|
1852
|
POST
|
Hi Michael, We've managed to capture the stack trace for when our UWP application crashes: > runtimecore.dll!std::vector<int,class std::allocator<int> >::_Emplace_reallocate<int &>(int * const,int &) Unknown runtimecore.dll!Esri_runtimecore::Map_renderer::Labelable::label_class_ids(void) Unknown runtimecore.dll!Esri_runtimecore::Map_renderer::Dynamic_layer_current::update_entities_(class std::vector<class Esri_runtimecore::Geometry::Envelope_2D,class std::allocator<class Esri_runtimecore::Geometry::Envelope_2D> > const &) Unknown runtimecore.dll!<lambda>(void)() Unknown runtimecore.dll!std::_Func_impl_no_alloc<<lambda_afe6e24629c3913758f1a9575b5fdf4f>,unsigned char>::_Do_call() Unknown runtimecore.dll!pplx::task<unsigned char>::_InitialTaskHandle<void,<lambda>(void),pplx::details::_TypeSelectorNoAsync>::_LogWorkItemAndInvokeUserLambda<std::function<unsigned char __cdecl(void)>>() Unknown runtimecore.dll!pplx::task<unsigned char>::_InitialTaskHandle<void,<lambda>(void),pplx::details::_TypeSelectorNoAsync>::_Init() Unknown runtimecore.dll!pplx::details::_PPLTaskHandle<unsigned char,pplx::task<unsigned char>::_InitialTaskHandle<void,<lambda>(void),pplx::details::_TypeSelectorNoAsync>,pplx::details::_TaskProcHandle>::invoke() Unknown runtimecore.dll!pplx::details::_TaskProcHandle::_RunChoreBridge(void *) Unknown runtimecore.dll!Esri_runtimecore::Common::Core_scheduler::invoke_(struct Esri_runtimecore::Common::Core_scheduler::Queued_proc *) Unknown runtimecore.dll!Esri_runtimecore::Common::Core_scheduler::Queued_proc::invoke(void) Unknown runtimecore.dll!Esri_runtimecore::Common::Core_scheduler::bridge_proc_(void *) Unknown runtimecore.dll!Esri_runtimecore::Common::Windows_Threadpool_scheduler::Scheduler_param::work_callback(struct _TP_CALLBACK_INSTANCE *,void *,struct _TP_WORK *) Unknown ntdll.dll!00007ff9ddaa849c() Unknown ntdll.dll!00007ff9ddaa6a29() Unknown kernel32.dll!00007ff9dba14034() Unknown ntdll.dll!00007ff9ddaf3691() Unknown Not being an expect in the depths of the ArcGIS Runtime, I suspect the issue lies in the following area: > runtimecore.dll!std::vector<int,class std::allocator<int> >::_Emplace_reallocate<int &>(int * const,int &) Unknown runtimecore.dll!Esri_runtimecore::Map_renderer::Labelable::label_class_ids(void) Unknown runtimecore.dll!Esri_runtimecore::Map_renderer::Dynamic_layer_current::update_entities_(class std::vector<class Esri_runtimecore::Geometry::Envelope_2D,class std::allocator<class Esri_runtimecore::Geometry::Envelope_2D> > const &) Unknown Would you be able to assist with pointing us in the direction of what ArcGIS Runtime calls from the API we'd need to focus in on? (maybe Esri.ArcGISRuntime.Layers.DynamicLayer) Thanks Bryan
... View more
10-14-2019
04:53 PM
|
0
|
3
|
1852
|
POST
|
As an update to this Michael, we've rolled back to 100.4 and we're not seeing the frequent app crashes anymore. We'll continue with 100.6 in parallel to continue the debugging as per the article above. Thanks for your help. As a side note, we too use RouteTask.SolveRouteAsync() (as mentioned in the article) however we are specifying the SpatialReference when creating MapPoint geometries to represent Stops.
... View more
10-11-2019
12:31 AM
|
0
|
0
|
1852
|
POST
|
Excellent, will get our devs across this and feedback. Thank you.
... View more
10-10-2019
05:54 PM
|
0
|
0
|
1853
|
POST
|
Is version 100.4 of the ArcGIS Runtime still being supported by Esri? We're going to see if the crashing happens with this version.
... View more
10-10-2019
05:46 PM
|
0
|
1
|
381
|
POST
|
We're seeing an extremely similar issue with ArcGIS Runtime 100.6 (Xamarin Forms 4.2), our application is frequently crashing and auto restarting (many times per hour on occasion). Faulting module name: runtimecore.dll, version 100.6.0.2513, time stamp: 0x5d5705ee. Exception code: 0xc0000005 We didn't have this issue with the 100.2.x version we used with XF 2.x. Is there a feature in the ArcGIS Runtime which we can enable which logs out debug level activity of what calls/actions are being made by our LoB application to the map control? e.g. change base layer, add feature layer, go to Lng/Lat etc. Thanks Bryan
... View more
10-10-2019
05:07 PM
|
0
|
9
|
1853
|
IDEA
|
It'd like it be possible to increase the size of the MapView Magnifier. I have users in the field who find the size of the Magnifier too small (11" HD screen) - the magnification level itself is fine, just the size of the Magnifier itself is what we'd like to increase (by a factor of 1.5x - 2.0x).
... View more
03-24-2019
04:20 PM
|
1
|
0
|
485
|
Title | Kudos | Posted |
---|---|---|
1 | 03-24-2019 04:20 PM |
Online Status |
Offline
|
Date Last Visited |
11-11-2020
02:24 AM
|