Hey guys,
so the problem that we’re facing, is that for 2 apps that we developed for the clients have been crashing due to high memory consumption. (>1.5GB)
This is quite frustrating, because in both cases we do not have any custom coded components (so memory leaks do not come from there)
We’re always using conditional rendering to display/hide sections. (so I would assume the memory should be cleaned after the components are un-mounted)
Out of those who experienced this, are you aware of any components that has memory leaks?
One particular app is specific to have really high amount of input fields (it’s really form-heavy)
But again, I guess you shouldn’t have memory leaks just because you’ve rendered 50 form fields. (we have general “form field” component that has type as property. So inside we have 10 inputs that are conditionally rendered based on type)
When I navigate to blank page (that only has sidebar) nothing happens with memory, it stays at 2GB
So my question, are you aware of any WW components that are know to have memory leaks?
I’ll check in with our tech team to see if there are any known issues related to memory leaks in specific components or patterns like yours. We’ll follow up here once we have more information;
In the meantime, if you haven’t already, feel free to send the project link to support via the WeWeb Dashboard chat, it can help us investigate the specific case faster.
Yeah, same here. We’ve only got one (pretty large) project left on WeWeb. Honestly, not fixing these memory leaks just isn’t acceptable. I’ve reported this so many times already — shared videos, sent in results from memory leak testing libraries that scan the entire app and clearly highlight the issues. The main problem seems to be that there’s no proper cleanup for global event listeners, so they just keep stacking up with every page change or over time (the scroll event listener in particular).
On top of that, the AI direction they’ve taken really doesn’t seem to be working in practice. Why not go for a simpler, more developer-friendly solution — like integrating into a standard Dev IDE (e.g. Cursor) — and leveraging existing developer resources to create custom components/sections? With MCP Servers, this could have been such a clean and straightforward approach to AI in WeWeb, while at the same time “outsourcing” the heavy lifting of AI development to those tools. That way, the only real responsibility would be keeping the resources and MCP servers up to date.
To be fair to them AI is a huge opportunity that nobody in the developer tools and app builder space wants to miss out on. Flutterflow literally built an entire separate product to tap into the AI wave. My issue with both teams - Flutterflow and Weweb is that in their dash for AI they are literally damaging their core product and I hope they don’t learn the lesson in a hard way. No company is too big/small to fail. NONE. And the first sign of danger is they stop listening to their core users. It is far easier to upsell an existing user than to acquire a new one, and I think there is already a “Lovable“ the world does not need another Lovable. So their website rebrand for me is just in poor taste - it screams “Copy Cat“ and this is me being honest cos I love this company. I mean if you get to the weweb website now, you literally have to squint to find the features page, the showcase page, the pricing page?? Who signed off on that!!??
It’s all “Type something into this box and trust us our AI will do the magic“ it’s so targetted at one single audience - and that same audience is inundated with options already. So I don’t just understand why they can’t remain true to their original mission - a low-code/no-code front end builder that actually works! And can be used for any type of project. I don’t want to rant. But I am very concerned about the crazy amount of bugs that have just exploded in the product since they began this Weweb 3.0 push. It is really not good. I don’t know. But if I give this another couple more months, my own days here too may be numbered. It could be so good. But they just seem so distracted. I am still rooting for them though. Always.
How does the memory issue present itself in production apps? In the last week I’ve had a couple of customers tell me “it blacks out and gives me the “Oops something happened” and asks to reload the page”.
I’m not seeing any issues in Xano logs, so I assume it’s a WeWeb issue. Support couldn’t find anything in the hosting logs, so now I’m wondering if this is a memory issue.
I’m assuming that self-hosting wouldn’t fix this either correct?
,
