jhen0409/react-native-debugger

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

Open

#151 opened on Oct 3, 2017

View on GitHub
 (8 comments) (1 reaction) (0 assignees)JavaScript (850 forks)batch import
bughelp wantedupstream

Repository metrics

Stars
 (10,097 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

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

Contributor guide

Research direction
Check the linked PR #130 and the troubleshooting docs. Reproduce the high memory usage with a simple RN project. Investigate the Chromium 59 changes that introduced the memory issue. Look for related Chromium bug reports and test with the latest devtools frontend.
Tech stack
javascriptreact
Domain
mobilefrontend
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.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Needs investigation
Prerequisites
React Native debuggingChrome DevTools
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30