You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When trying to find unmapped routes the app gets slower and slower until finally crashes with our of memory exception.
What steps will reproduce the bug?
Go to my recordings
Select a route
Search for unmapped routes
Waitbor heck the responsiveness of fast panning out the map
What I expect to happen
UI should be smooth
Platform
Israel Hiking Map app
Israel Hiking Map site in a browser
OS Name and Version
Any
Browser Name and Version
Chrome, latest
Additional information
Initial debug shows that the reason for this seems to be related to how the mgl-marker is getting its lngLat from, which is s method that returns a new object every time.
This might be related to a recent change in Angular or ngx-maplibre-gl as I believe this was never an issue in the past and this code wasn't changed recently.
The text was updated successfully, but these errors were encountered:
I was not able to fully reproduce this in ngx-maplibre marker example, so it might be a bit more complicated, or requires a more complicated example.
The root of this issue is basically the creation of a lot of objects all the time, which probably causes some garbage collection backlog and this slowly degrades the performance of the website.
I look at all the other places that are using makers just in case, this is the only place that continuously created objects.
What happened?
When trying to find unmapped routes the app gets slower and slower until finally crashes with our of memory exception.
What steps will reproduce the bug?
What I expect to happen
UI should be smooth
Platform
OS Name and Version
Any
Browser Name and Version
Chrome, latest
Additional information
Initial debug shows that the reason for this seems to be related to how the mgl-marker is getting its lngLat from, which is s method that returns a new object every time.
This might be related to a recent change in Angular or ngx-maplibre-gl as I believe this was never an issue in the past and this code wasn't changed recently.
The text was updated successfully, but these errors were encountered: