jhen0409/react-native-debugger

Help to track chrome devtools memory bug (Chromium >= 59)

Open

#151 建立於 2017年10月3日

在 GitHub 查看
 (8 留言) (1 反應) (0 負責人)JavaScript (10,097 star) (850 fork)batch import
bughelp wantedupstream

描述

Context: https://github.com/jhen0409/react-native-debugger/pull/130#issuecomment-330034816 and this troubleshooting

The current version of RNDebugger (~ 0.7.x, Chromium 58) haven't this problem, but it will caused when we must to upgrade Chromium version (#130), so official remote debugger (Chrome browser) also does.

  • Confirm it caused since Chromium 59 (still on 62 Beta / 63 Canary)
  • Confirm the problem still on the latest commit of ChromeDevTools/devtools-frontend
  • Help to find related Chromium bug report, or just report with initial RN project

貢獻者指南

技術棧
javascriptreact
領域
developer experiencetooling
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
4
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
half day
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
needs investigation
前置要求
familiarity with Chrome DevToolsunderstanding of React Native debugging
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
25
研究方向
First, confirm the memory bug still exists in the latest commit of ChromeDevTools/devtools frontend by building and testing it with an initial React Native project. If confirmed, search the Chromium bug tracker for existing reports related to high memory usage in DevTools since Chromium 59. The issue is linked to PR #130 and the troubleshooting docs. Compile findings and report a new Chromium bug if none exists.