appsmith
appsmith copied to clipboard
[Bug]: Appsmith going down when reached high memory
Is there an existing issue for this?
- [X] I have searched the existing issues
Description
When I'm using appsmith for a long time, the memory is increasing, and the appsmith application is taking too long to respond, sometime on my console browser show 504 gateway timeout. after i restarted the appsmith apps, it's going normal again. i didn’t see error anything on appsmith, it's just going slow and i just reboot the services it's back to normal
What i expect is appsmith is normal to access, not slow when reach some memory value
Steps To Reproduce
- Appsmith is using on production
- After a couple of hour, memory increasing
- appsmith is going to slow, and sometimes give 504 timeout
- restart appsmith
- back normal
Public Sample App
No response
Environment
Production
Severity
Critical (Broken Production apps)
Issue video log
No response
Version
Self Hosted - v1.16
This critical issue has not seen activity for a while. It will be closed in 7 days unless further activity is detected or the Critical tag is removed.
Need more observability to understand the repro steps by having logs from the customer's instance. Currently blocked by this github issue.
cc : @pratapaprasanna
This critical issue has not seen activity for a while. It will be closed in 7 days unless further activity is detected or the Critical tag is removed.
@rajatagrawal can we get a date by when we can debug this?
@ariretiarno Apologies for the slow response. Would it be possible to get on a call to help triage this issue ?
This critical issue has not seen activity for a while. It will be closed in 7 days unless further activity is detected or the Critical tag is removed.
@ariretiarno if it is still happening, can you please take a thread dump when the issue occurs and send it across?
You can use jstack to take a thread dump. I would recommend to take a heap dump using jmap as well, but it can't be shared across in public, as it will contain sensitive data.
Closing this issue as we haven't heard back from you in a while