Every buffer increases memory used by internet browser by 500 mb

Permanently deleted user

31 Oktober 2017 15:43

Hello,

 

I have a Geocortex site with a few point layers.

 

Users frequently select a point and create 10 km buffers around that point to get around 3000-5000 records identified in the buffer from different point layers.

 

However, every time such a buffer is executed, the memory usage for the internet browser tab goes up by an additional 500 MB and stays there.

 

And for every subsequent buffer after that the memeroy keeps going up by aroudn 500 MB.

 

So after performing a few buffers in a row, the site become very slow obviously.

 

Clearing the buffer results, does not relese the memory, nor does changing themes.

 

Is there a solution to release the memory. chrome developer tools shows JS heap getting bigger and bigger after every buffer. I am at Essentials 4.6.3/HTML viewer 2.7.2

0

• 

  Permanently deleted user

  10 November 2017 00:10

  Hi Soham,

   

  Are you seeing this memory leak in one browser in particular? Are you able to reproduce it in different browsers?

  0
• 

  Permanently deleted user

  10 November 2017 15:31

  Its in all browsers Jordan.

  0
• 

  Permanently deleted user

  17 November 2017 19:14

  Okay, I recommend opening a support case with Esri Canada, so we can follow up. In the meantime, I'll run this by the QA team. I don't suppose your application is publicly accessible, is it?

  0
• 

  Permanently deleted user

  17 November 2017 19:17

  Ok Jordan, I have already done that and ESRI support staff has responded to me by saying they are also able to replicate the issue and they said they will let me know once they have received some official feedback on their observations from Latitude. My application is not publicly accessible.

  0
• 

  Permanently deleted user

  17 November 2017 20:55

  Thanks, Soham. I see the case. I'll follow up with the team. In looking for similar issues, I see that a few memory leaks were fixed in version 2.9, so, if you were looking to try something in the meantime, you could see if upgrading your viewer to a more recent version fixes your issue.

  0
• 

  Permanently deleted user

  17 November 2017 20:57

  Ok Jordan will try that. ESRI did reply back to me saying this issue is logged in Latitude's bug tracking system as follows: "GVH-16676 Memory not released following buffer operations."

  0
• 

  Permanently deleted user

  18 November 2017 01:00

  Okay, it sounds like Esri Canada were able to reproduce this issue in 2.9.2, so upgrading likely won't help a whole lot. I'll follow up again once we've taken a deeper look.

  0
• 

  Permanently deleted user

  19 November 2017 23:51

  Is the memory leak occurring on the server or on the end user machine? If the server, ours it the one with Geocortex or the one with ArcGIS Server?

  0
• 

  Permanently deleted user

  20 November 2017 14:20

  Thanks Jordan.

   

  Hi Mike, the memory leak occurs at the end user machine.

  0

Du måste logga in om du vill lämna en kommentar.