jhen0409 / jhen0409/react-native-debugger

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

Offen
#151 8 Kommentare 1 Reaktion 0 zugewiesene Personen Auf GitHub ansehen
bug help wanted upstream
Vorherrschende Sprache
JavaScript
Sterne
10.4k
Forks
815
PR-Merge-Kennzahlen
Keine gemergten PRs in 30 T.

Beschreibung

Context: https://github.com/jhen0409/react-native-debugger/pull/130#issuecomment-330034816 and [this troubleshooting](https://github.com/jhen0409/react-native-debugger/blob/master/docs/troubleshooting.md#how-to-resolve-problem-of-high-memory-usage-on-devtools)

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.

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

Beitragsleitfaden

Beitragsleitfaden öffnen

Rechercherichtung

Start with docs/troubleshooting.md and the context in pull request #130. Reproduce the high-memory-usage problem with an initial React Native project, then compare it with the latest ChromeDevTools/devtools-frontend commit. Done means confirming whether the issue persists and finding or filing the related Chromium bug report.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Bewertung

Tech-Stack
electron, javascript, react-native
Bereich
devtools, performance
Issue-Typ
Bug
Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Aktivitätsstatus
Veraltet
Klarheit
Muss geklärt werden
Anfängerfreundlichkeit
30/100

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.