Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error: "Minified React error" in React dev tools when using Components tab #16926

Closed
tchaffee opened this issue Sep 27, 2019 · 7 comments
Closed

Comments

@tchaffee
Copy link

Do you want to request a feature or report a bug?
Bug

What is the current behavior?
React Dev tools gets this error when I try to look at the Components Tab

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem. Your bug will get fixed much faster if we can run your code and it doesn't have dependencies other than React. Paste the link to your JSFiddle (https://jsfiddle.net/Luktwrdm/) or CodeSandbox (https://codesandbox.io/s/new) example below:
I don't know how to reproduce it. It was working yesterday and not working today.

What is the expected behavior?
That the Components tab of the React dev tools doesn't crash.

Which versions of React, and which browser / OS are affected by this issue? Did this work in previous versions of React?
16.6.3

Here is what I see. It's not my React app crashing. It's the dev tools.

Selection_880

Copy paste of the errors from the screenshot in case that's helpful:

The error was thrown at hi (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:32:61172)
    at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:40:256084
    at Vo (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:40:256125)
    at oi (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:32:58828)
    at Jl (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:32:103390)
    at vc (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:32:89163)
    at Ac (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:32:89088)
    at ac (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:32:86037)
    at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:32:45275
    at n.unstable_runWithPriority (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:40:3691)
The error occurred in Vo
    in div
    in aa
    in div
    in za
    in div
    in si
    in div
    in li
    in Suspense
    in Wa
    in div
    in div
    in Jo
    in Xr
    in _o
    in Unknown
    in n
    in Unknown
    in div
    in div
    in zi
    in Ge
    in un
    in ba
    in Rc
@bvaughn
Copy link
Contributor

bvaughn commented Sep 27, 2019

Hi @tchaffee. Can you give me some more info about which operating system and browser/version you're using? I'm not able to reproduce this behavior, although clearly some others are (e.g. #16925) I'm just trying to figure out how to narrow down the cause.

@bvaughn
Copy link
Contributor

bvaughn commented Sep 27, 2019

@tchaffee If you can reproduce the problem reliably, I wonder if you'd be willing to install a test build of DevTools to see if it fixes the problem. (I could create a build after backing out one or two changes that might be related, to at least help narrow down the cause.)

@tchaffee
Copy link
Author

@bvaughn I can't reproduce it. It went away. Must have been something in my branch that has since changed. It was happening in both Chrome and Chromium.

OS: Ubuntu 18.04.3 LTS.
Chrome: Version 77.0.3865.90 (Official Build) (64-bit)
Chromium: Version 76.0.3809.100 (Official Build) Built on Ubuntu , running on Ubuntu 18.04 (64-bit)

If I do get it to happen again reliably, I'll freeze the branch and let you know.

@bvaughn
Copy link
Contributor

bvaughn commented Sep 27, 2019

Thanks much for the update.
Please do keep me posted.

@bvaughn
Copy link
Contributor

bvaughn commented Sep 27, 2019

Looks like fa1a326 was the problematic commit (based on someone else testing a one off build I made and confirming). Not sure why yet though.

@bvaughn
Copy link
Contributor

bvaughn commented Sep 27, 2019

Bugfix posted via PR #16934

@bvaughn
Copy link
Contributor

bvaughn commented Sep 28, 2019

4.1.2 has just been published to NPM and uploaded to the Chrome+Firefox stores with a fix for this issue. Thank you for the report and I apologize for the inconvenience.

@bvaughn bvaughn closed this as completed Sep 28, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants