Lagging Issue with Bolt.diy + High RAM Usage

bolt.diy
1

Hello,

Thank you so much to the developers and contributors, I really appreciate all your work on this amazing project.

Just one question: I’m currently using Bolt.diy and started building a website with it using Claude 4. While working on the project, the page becomes very laggy, uses about 3 GB of RAM on its own, and eventually the tab stops responding, which prevents me from continuing to prompt and build.

Is there any solution I might not be aware of? I understand that web containers install the Node dependencies in the browser. Would hosting it on a VPS fix this issue?

Thanks in advance for your help.

2

Can you test ; feat: comprehensive major SDK update with advanced LLM and service integrations by Stijnus · Pull Request #2001 · stackblitz-labs/bolt.diy · GitHub

3

Thank you, but what could be the the cuase of the problem.

Since i worked on the ui abit locally and i don’t wanna lose the changes ive done :smiling_face_with_tear:

Thank you so much :folded_hands:

4

Hi,

Yes, you can test a GitHub Pull Request (PR) without risking data loss on your branch. The key principle is simple: never test directly on your working branch — always isolate it.

Here are safe approaches:

:white_check_mark: Option 1: Fetch & Checkout in a Detached Branch

git fetch origin pull/<PR_NUMBER>/head:pr-<PR_NUMBER>
git checkout pr-<PR_NUMBER>

This creates a local branch with the PR’s changes. Your branch stays intact. After testing:

git branch -D pr-<PR_NUMBER>

:white_check_mark: Option 2: Use a Temporary Branch

If you want to test the PR alongside your own branch:

git checkout -b test-pr
git pull origin pull/<PR_NUMBER>/head

This merges the PR into a disposable branch. Remove it when done:

git branch -D test-pr

:white_check_mark: Option 3: GitHub CLI (if installed)

gh pr checkout <PR_NUMBER>

This automatically checks out the PR into a safe branch.

Grtz,

Stijnus