Wappler New Problems Panel - Memory Bomb!

Wappler General Bugs
1

Hi Team,

Just updated to 7.7.5 on MAC OS and all seems OK except for the new “Problems” panel. When I click on that it scans for errors but it completely renders the rest of the Wappler app unusable, so much so that I can’t even close / exit Wappler I need to Force Quite every time. If I don’t click on that panel it’s fine, but the minute I click on it my Wappler app freezes and requires a Force Quit.

Thanks,

2

I’ve noticed that management of memory resources in Wappler has become a real productivity issue in the last few versions.

I haven’t upgraded to v7.7.5 yet (still running v7.7.3), but I’ve been experiencing a lot of issues with the Wappler app freezing and needing a Force Quit (on macOS). This usually happens when I try to close the app normally by clicking the Close icon. The memory usage for the Wappler process starts to spike quickly, which risks making the OS unstable. To fix this problem that keeps happening, I have to restart my laptop until the memory pressure builds up again.

This problem seems to pop up most when I’m working in the code panel and saving changes often. It seems like the memory issues were fixed when v7 came out, but they’ve come back in the last few versions.

4

Do you see any errors reports in the count next to the problems panel?

Does it happen each time if if Wappler is restarted?

5

how about having the Problems Panel by default open on “Current” and not “All”…
Then it might not be so resource intensive.. at it will then by default only open that page you are on.. Because if I click on any other SC / File it defaults back to "All” and rescans everything again…

7

Please make sure to post different issues in separate topics. The topic mentions memory usage by the problems panel.
If you have a different issue, report it detailed in a new, separate topic.

8

ok sorry

10

Fixed in Wappler 7.7.6

12

I don’t believe this is fixed. I am still experiencing the same issue after updating..

13

The problem panel was optimized and now uses even less resources than before. Also you can turn the auto scan in Wappler settings now.
So maybe try to check again what is causing a problem for you - and is it on a specific project?

14

All I did was open the problem panel (same project I’ve always worked in) as it showed 2 errors. It just froze Wappler completely after doing that. It’s the same issue as before

15

Are you experiencing this issue in a specific project or in all your projects?
What errors do you see reported that when selected make Wappler freeze?

16

I haven’t tested it in other projects. It just found 1 small error relating to a bad routing declaration in the page. As soon as I clicked the problem tab Wappler just froze instantly. I should point out it was in a partial sorry not a page

17

Please post a screenshot or copy the details of the exact error that’s causing the issue.