Gradual memory increase on browser leading to unresponsive app

[kfawcett]

@George

Well it depends indeed on the data they return. So hundreds of server connect actions with each returning tens of thousands records might get too much if all running on a single page.

I feel like this bug report and mine are different, but I'm experiencing a memory leak with only 100-200 records.

Memory Leak in running app

Wappler Version: Wappler 6 Beta 15 Operating System: Windows 11 Server Model: Capacitor Database Type: Pouch/IndexedDB Hosting Type: localhost Expected behavior Memory should be fairly stable. Actual behavior Memory continues to increase over time until the page crashes. [Memory Leak caused crash] How to reproduce I’m trying to figure this out. Seems like it could be due to adding records into pouchdb/indexeddb. If 100 records are added in one go, from API calls, then the memory starts …