Wappler crashes when closing a file with a huge spike in memory usage

Wappler General Bugs
1

Wappler Version : 7 Stable
Operating System : MacOS
Server Model: NodeJS
Database Type: MySQL
Hosting Type: Docker

Expected behavior

What do you think should happen?

When closing a file by clicking on the x button next to the file name, the file should close normally.

Actual behavior

What actually happens?

The file doesn't close and Wappler become unresponsive. The app can't be quit from the app menu or from the tray icon. Additionally, there is a spike in the memory usage when the file doesn't close in a normal manner.

The only method to quit the app and stop a spike in the memory usage is by Force Quit from the activity monitor. If I don't Force Quit, the memory usage keeps increasing, which is really concerning as it can make the whole system unstable and unusable.

I have attached a screenshot of the memory usage at 6.69GB. In normal running, the usage hovers around 1-1.5GB.

Screenshot 2025-06-23 at 12.18.44 pm
Screenshot 2025-06-23 at 12.18.44 pm1758×120 28.1 KB

UPDATE: Wappler has crashed 3 times today. There's no pattern that can be pin-pointed when Wappler crashes.

2

Are there any specific pages you are editing? Does it happen on close of the whole editor or just single page and if so what page is that?

Try maybe a full clean install from scratch to be sure that no old stuff still there.

3

Hi George,

It is a random occurance and until now, it has happened when closing a content page, which again can be any of the content pages.

When this happens, the app can't be quit from the Wappler -> Quit option or from the tray icon. I can see the increase in memory usage within a couple of seconds by 4-5GB. It has be force quit straightaway to avoid any issues with the system stability or usability.

4

try running Wappler with debug logging and hopefully you can reproduce it, then send us the debug log.

Is it also something from the final version now, or did you had it before with the betas?

6

Hi George,

How can I run it with debug loggin enabled when I don't know when it is going to crash. The memory usage has been an issue in Wappler when working in the code for more than 30 minutes and saving it continously. The memory usage has been increasing in v7 for sometime.