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
Summary: Insomnia gradually uses more and more RAM regardless of if I'm using it actively or not. I have left it open for several days and have seen it using ~4GB. Watching Task Manager, it appears that Insomnia will consume an additional 1MB every minute or two. Restarting the application frees up memory. I've seen this happen with another Electron app (Slack) too, though it appears they got a handle on it and it doesn't exhibit the same behavior anymore.
How To Reproduce
Please list all pertinent information and steps needed to reproduce the issue. For example:
Sorry for the delay on this one. I haven't had a big enough time block to dig into this, but I do want to get to it soon. The DB that insomnia uses is in-memory, so large requests and responses will quickly inflate the amount of RAM needed. My initial solution for this will be to pull large blobs (request and response bodies) out of the DB and store them directly on the file system.
As for leaks, I'm not seeing any on my end when the app is idle. I observe memory increasing for around 30 seconds, but eventually returning back down (probably after garbage collection).
Overview
Insomnia Version:
5.1.1Operating System:
Windows 7Summary:
Insomnia gradually uses more and more RAM regardless of if I'm using it actively or not. I have left it open for several days and have seen it using ~4GB. Watching Task Manager, it appears that Insomnia will consume an additional 1MB every minute or two. Restarting the application frees up memory. I've seen this happen with another Electron app (Slack) too, though it appears they got a handle on it and it doesn't exhibit the same behavior anymore.How To Reproduce
Please list all pertinent information and steps needed to reproduce the issue. For example:
Other Notes
In the time it took me to write this up it consumed +~12MB. Could this be related to logging?
The text was updated successfully, but these errors were encountered: