codesandbox / codesandbox/codesandbox-client

Memory Leak

Open
#5,162 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Needs More Info
Dominant language
JavaScript
Stars
13.6k
Forks
2.4k
Avg merge
6d 19h
Merged PRs (30d)
2

Description

🐛 bug report

Preflight Checklist

  • I have read the
    Contributing Guidelines
    for this project.
  • I agree to follow the
    Code of Conduct
    that this project adheres to.
  • I have searched the issue tracker for an issue that matches the one I want
    to file, without success.

Description of the problem

when i open my sand box in a separate tab using .csb.app url the tab crashes after a while , checked the memory tab and found out that the heap size is increasing in 15+Mb each second reaching 1Gb+ then crashing.
this wont happen in the editor embedded iframe , idk what is the difference,
after looking at the snapshot it was mostly strings(65%+ ,package licenses loaded multiple times) and system objects.
i found out that this doesn't happen with Edge browser , this happens with chrome (Version 87.0.4280.66 (Official Build) (32-bit) and (64-bit)) .
this basically happens with any template i tried react and vue
screenshot:
image

Link to sandbox: link (optional)

any template will do

Your Environment
Software Name/Version
Сodesandbox
Browser Google Chrome Version 87.0.4280.66 (Official Build) (32-bit) and (64-bit)
Operating System Windows 10 pro 64bit Build 18363

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the leak by opening any React or Vue sandbox through its .csb.app URL in Chrome and monitoring heap growth, then compare it with the embedded editor iframe and Edge. Done means identifying the repeated package-license or system-object allocations and preventing the standalone tab from growing until it crashes.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.