Memory leak while just navigating through spreadcells by UP Down keyboard arrow

Memory leak while just navigating through spreadcells by UP Down keyboard arrow

Posted by: venkat on 12 May 2019, 11:07 pm EST

• 

  venkat

  • Post Options:
  • Link
    Copy

  Posted 12 May 2019, 11:07 pm EST

  We are trying your latest version of spreadjs on demo link, and got one serious memory issue.
  
  Steps to reproduce issue,

  1. Open demo link in chrome or any browser:
     
     link :https://www.grapecity.com/demos/spread/JS/InspectorSample

  2. Select any cell and navigate between cells with UP down Arrow scroll up , scroll down

  3.No need to punch any data in cells.

  4.As we are just moving through cells it is consuming minimum 5MB memory during each cell change and within 5-10 minute it consumes more than 2 GM memory and after certain limit browser crashed. The memory used for nevigation is never been released.

  5.On each cell move memory being consumed and not released at all, garbage collector cant get the memory to release it. This is very serious bug, and our live applications are crashing when users work more than 15 min.

  6.You can check and let me know in case of any other info.

  OS: Windows 7, 8, 10
  
  RAM : 4GB, 8GB
  
  Browser :Chrome (latest version), FireFox.

• 

  venkat

  • Post Options:
  • Link
    Copy

  Posted 13 May 2019, 12:50 am EST
• 

  sharad.tomer

  

  • Post Options:
  • Link
    Copy

  Posted 13 May 2019, 7:08 pm EST

  Hi,

  We are able to replicate the issue at our end and hence we have forwarded it to the concerned team for further investigation(INternal tracking ID #272537). We will let you know about any updates regarding the same.

  Thanks for reporting.

• 

  venkat

  • Post Options:
  • Link
    Copy

  Posted 15 May 2019, 5:33 pm EST

  Hi Sharad,

  Please fix this issue in next stable release , let us know when it will release?

  Regards,
  
  Umesh

• 

  sharad.tomer

  

  • Post Options:
  • Link
    Copy

  Posted 23 June 2019, 5:12 pm EST

  Hi Umesh,

  This issue has been fixed in the latest release. You may confirm the same from the inspector sample(https://www.grapecity.com/demos/spread/JS/InspectorSample). Now the memory consumption increases a while and then decreases as expected. Please let us know if the issue persists for you.

  Regards