mattdesl/budo

Memory leak?

Open

#213 建立於 2017年6月13日

在 GitHub 查看
 (3 留言) (0 反應) (0 負責人)JavaScript (2,174 star) (124 fork)batch import
help wantedquestion

描述

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.

貢獻者指南

技術棧
javascriptnodejs
領域
developer experiencetoolingbuild system
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
half day
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
unclear
前置要求
Node.js basicsMemory profiling toolsBudo API basics
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
20
研究方向
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.