Uobject Max Count reached Crash

[Musgi]

Package is crashing in a 2-3 mins duration after runing duo to the issue given in the image with crash report
creating UArcGISSpatialReference even for the same component instead of updating it is causing very heavy load on the GC it cant keep up with the amount of objects being created and the object pool max limit is reached within few mins .
This is very clear especially in the StreamLayer Level if you run it and take alook on the amounf of Objects being created as shown in the second image with the red outline , This number will grow extreemly fast in this level due to having alot of UArcGISLocationComponents so it raches very quickly as well. Package the sample project with this level as the main game level and test the level is the 4th image.
In normal levels the issue remains the same except that the growth is not as fast so it wont happen unless the app left running for a while.

5t Image include a try to fix it by caching the UArcGISSpatialReference in a map and try to reuse i needed oen with the same key points but it failed and crashed due to map entries turning invalid ((Name=Illegal name (block index out of range))) and getting this as their value crash happens on GetHandle() Function .

EDIT: I attached another image shwoing the acctual number of ArcGISSpatialReference being created and logs equivelan to it using this
obj list class=ArcGISSpatialReference
in the level while runnin the game or in eidtor will always show an increase in count with doing nothing .When firing up StreamLayer or doing anything related to a arcgislocationcomponent this nnumbers go up quickly.

[Mohamed-Arafa669]

This is a serious issue that is halting developing lots of things please kindly can anyone help ?

[TransformologyXR]

Thank you for posting this. We are facing the same issue, which is causing major problems to our smart city solution. We are trying a workaround and we are at a stage where we need to either make major changes to the arcGIS SDK code or change direction and choose another approach, replacing arcGIS SDK

[mmgaw113]

Hello,
Thanks for pointing this issue out to use. I was able to verify the behavior in a build, but not in the engine. With that said, I managed to troubleshoot and determine what was causing the problem and have a pull request up for a fix. Please feel free to test this branch out to see if it fixes your problem: #146

I will close this issue when the Pull Request has been merged and verified by an internal team member.
Thanks,
Mason

[arash-sh]

Regarding your attempt for caching the spatial reference, that is something that should work and should definitely reduce the number of created uobjects. The crash here might be due to GC'ing an internal object that corresponds to the local variable holding the spatial reference. Basically if you have multiple copies of a spatial reference instance (e.g., passing it by value to a function, or returning a copy, etc. ) whenever any copy goes out of scope, it will destroy the underlying internal object, so all copies become invalid. As a result, the handle of the instance becomes nullptr. You could check .GetHandle() in your validity check to avoid a crash. To ensure that internal spatial reference objects are not being destroyed unintentionally, you could use strategies such as smart pointers or std::move and avoid copies as much as possible.
If you know what spatial references you need ahead of time, it might be easier to store those in a static member variable rather than updating the map at runtime.

Also, since this seems to be an issue with the number of uobjects, if you don't need blueprint compatibility, your could try switching to the ArcGISSpatialReference class (non-uobject type).

[Musgi]

While this fixes the quick crashing due to planes. the issue still remains the object counter is going up as i stated in the issue the planes was just an accelarting factor the porject will crash after leaving it running for a while. The issue that needs to be fixed is the newobjects created with no outer (WIll never be GC) and the creation of points and spatrefs without reuesing the already created ones/

[mmgaw113]

A fix has been merged. For the stream layer sample, we are not using the UArcGISPoint to create a new position for the ArcGISLocation Component. Instead we are using the non-uobject class ArcGISPoint to create a point and convert it to Engine Transform to set the plane position. It is not a fix for the underlying issue, as we would like to be able to use UArcGISPoint. We will continue to look into a formal solution within the plugin. Please let us know if this issue can be closed.