mattdesl/budo

Memory leak?

Open

#213 opened on Jun 13, 2017

View on GitHub
 (3 comments) (0 reactions) (0 assignees)JavaScript (2,174 stars) (124 forks)batch import
help wantedquestion

Description

I am testing on a new MacBook Pro and seeing a lot of "Out of Memory" system errors after 100-200 consecutive reloads in a very heavy WebGL scene (loading 3D models and procedural geometry).

It's hard to know whether the memory leak is in Chrome, or budo, or somewhere else, but I'll start digging to see what's up. Generally the memory problem goes away as soon as I quit Chrome, but in some cases I've seen the memory come back as soon as I terminate the budo process.

Would be interested to hear if anybody else has run into this.

Contributor guide

Tech stack
javascriptnodejs
Domain
developer experiencetoolingbuild system
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
unclear
Prerequisites
Node.js basicsMemory profiling toolsBudo API basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20
Research direction
Investigate memory usage of budo process using Node.js heap snapshots. Check if the issue is related to budo's file watching or WebSocket connections. Look at existing comments for any clues. Consider testing with a minimal WebGL scene to isolate the problem. Files to examine: lib/server.js, lib/budo.js.