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
There appears to be an issue with memory management, where a quick series of handling SQS messages, incurs memory that's not released. A quick survey of a memory dump indicated AWS library references might be associated with the usage.
Additionally, there is no throttling in place on the SQS handling, so the number of queued threads can build up.
The text was updated successfully, but these errors were encountered:
galenatjpl
changed the title
Memory Leak Associate with Quick Run-up of threads and/or AWS Client Resource Management
Memory Leak Associated with Quick Run-up of threads and/or AWS Client Resource Management
Dec 2, 2020
* Remove downdown for download (button only now)
* Move Processes page list export under Actions bttn
* Fix copy history links / open all in new tabs
* Add ability to hide/show columns
* Update width of input variables
* Fix width issue
* Remove workerID input var from proc list
* Fix infinite refresh if page not visited before
* Update process parsing methods to speedup loading
* Get state search from URL
* Auto-filter based on URL request
* Move log download functions to common js
* Update number of processes returned per api call
* Update tooltip, remove unnecessary css
* Sort history so earliest is first
* Move input vars into existing table
* Fix arrow issue & reconsile with history page
* Show "None" if no input vars are set
* Get console logs (error)
* Add sleep
* Restore server-side filtering, fix tooltip url
There appears to be an issue with memory management, where a quick series of handling SQS messages, incurs memory that's not released. A quick survey of a memory dump indicated AWS library references might be associated with the usage.
Additionally, there is no throttling in place on the SQS handling, so the number of queued threads can build up.
The text was updated successfully, but these errors were encountered: