All browser tabs with Softr Studio crash after a short while, requiring a refresh. Tabs with other web pages (platforms) remain active. This has been occurring for about a week now on Chrome browser. Anyone else noticing this?
After two weeks and working with support with no resolution, here is the most likely problem (with Softr):
Yes, absolutely. You are fundamentally right: it is primarily Softr’s responsibility.
When other web pages and apps run smoothly on your Chromebook and only Softr crashes, the issue almost always boils down to how Softr’s software manages resources inside the browser.
Here is why this falls on Softr’s engineering team to solve, and what is happening behind the scenes:
1. Memory Leaks and Code Cleanup
Standard websites are mostly static text, images, and light scripts. Softr Studio, by contrast, is a massive Single Page Application (SPA)—effectively an entire desktop visual IDE running inside a browser tab.
Every time you add a block, edit settings, switch views, or preview a layout, Softr’s JavaScript code creates objects and event listeners in memory. If their developers don’t write clean garbage-collection routines to destroy old data when it’s no longer needed:
-
The tab’s memory footprint steadily inflates (a classic memory leak).
-
Eventually, the tab crosses the memory ceiling allowed by Chrome OS.
-
The browser’s “Out of Memory” (OOM) killer abruptly terminates the tab to protect the rest of the computer from freezing.
2. Failure to Optimize for Average Hardware
Professional software platforms are expected to profile and optimize their applications for mainstream consumer hardware, not just high-end developer workstations.
-
If a visual builder requires 12GB+ of unthrottled RAM just to stay alive during basic editing, that represents unoptimized front-end architecture (e.g., lack of DOM virtualization, redundant state re-renders, or heavy uncompressed asset caching).
-
Leading browser-based tools like Figma and Canva invest heavily in custom memory management so their software runs reliably on 8GB machines and Chromebooks. Softr has to hold itself to the same standard.
3. Even When Chromium Changes, Developers Must Adapt
Occasionally, a Google Chrome update changes how the V8 JavaScript engine handles memory or how iframes are sandboxed, which can inadvertently trigger instabilities in complex web apps.
However, even when an upstream browser change acts as the catalyst:
-
Chrome is an open, standard platform adhering to web specifications.
-
Softr cannot reasonably expect millions of users to downgrade their browsers or buy more expensive laptops.
-
SaaS companies must monitor browser releases, identify where their scripts conflict with new browser behavior, and push hotfixes to their codebase.
@dominiconorton. Read the post.