Memory leak... about requestly

[sachinjain024]

@sarathnair @isiahmeadows Sorry for responding so late on this ticket. I actually forgot to update this one. We have made some cleanups in the code and removed some unused code+library.

I am expecting that should fix the issue. If by chance, you guys are still using Requestly (That would be a huge thing for me), can you please let me know if you face this?

[dead-claudia]

@sachinjain024 I'm not seeing it on my end any more and haven't for a while, so I think this could be closed.

[dead-claudia]

For such a simple tool conceptually, that's way too much memory.

[sachinjain024]

@isiahmeadows Thanks for logging this. I'd definitely keep this in mind in my development and will often check for memory consumption by this.

How did you check the memory consumption? Did you use Chrome Task Manager? Here is a screenshot of my device.

Of all the extensions I use, Requestly came at the bottom with ~40 MBs of memory and I think that's fair. Although I can not provide the breakdown of memory consumption within the extension. The only things Requestly caches are:

1. List of all rules are in memory
2. Listeners on Storage and other chrome events

What's your expectation? What should be the memory consumption?

[dead-claudia]

I did use Chrome's task manager. I didn't take a screenshot, though. It also takes several hours to get truly problematic (after ~10 hours, it usually hits about 300-400MB), so it's not something that quickly appears.

I would normally expect Requestly to stay near the bottom while not filtering anything, and slow memory leaks aren't easily caught.

Any idea where I could find the relevant source code? I'm actually willing to help rectify this when I can find time.

[sarathnair]

I have also experienced memory leak in program. I have set up some rules in requestly. These rules basically replace the URL. Every time I refresh my page I can see in Chrome's task manager that memory goes up and never comes down. For my application the requestly extension consumes additional 2MB memory in each page reload. This is a critical issue and should be looked into immediately.

[sachinjain024]

@sarathnair Can you please give me a screenshot of your chrome task manager. I just wanted to view the memory consumption by other tabs/processes as well before considering this as issue. Normally, chrome keeps on hogging memory if you do not refresh the page for a long time. I think the same holds true for extensions as well. Can you check the memory usage by other extensions as well ?

[sarathnair]

@sachinjain024

Here is the screen shot you asked. After a couple of refresh I see below:

I see similar behavior in Adblocker extension. But after a while Adblocker seems to release memory and come back its previous state.

[sachinjain024]

Thanks @isiahmeadows for confirming. Feel free to give us suggestions/feedbacks.You can also reachout to us at requestly dot extension at gmail dot com.