Skip to content

React-dev-utils error handling is incredibly slow (>1.5s processing on main thread) on Android #11265

@MCArth

Description

@MCArth

Describe the bug

React-dev-utils appears to be catching an error from chrome, and, on my machine, spends 1.7 seconds doing things. Perhaps this is worst case behaviour (especially since I see a quicksort in the stack!) but it is severely impacting my development experience. This wouldn't be as frustrating if this was only first case behaviour, however nothing seems to be cached and it repeatedly takes this same length of time.

image

image

Chromium bug report: https://bugs.chromium.org/p/chromium/issues/detail?id=1235139

Which terms did you search for in User Guide?

slow, catching error, react-dev-utils

Environment

Application version: Version 92.0.4515.117
Operating system: Android 11; ONEPLUS A6000 Build/RKQ1.201217.002

npx create-react-app --info output:

Environment Info:

current version of create-react-app: 4.0.3
running from C:\Users\mcart\AppData\Roaming\npm-cache_npx\23676\node_modules\create-react-app

System:
OS: Windows 10 10.0.19042
CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
Binaries:
Node: 14.15.1 - C:\Program Files\nodejs\node.EXE
Yarn: Not Found
npm: 6.14.1 - C:\Program Files\nodejs\npm.CMD
Browsers:
Chrome: 92.0.4515.107
Edge: Spartan (44.19041.1023.0), Chromium (92.0.902.62)
Internet Explorer: 11.0.19041.1
npmPackages:
react: ^17.0.1 => 17.0.1
react-dom: ^17.0.1 => 17.0.1
react-scripts: 4.0.1 => 4.0.1
npmGlobalPackages:
create-react-app: Not Found

Steps to reproduce

  1. Reproduce chromium bug while using dev-utils

Expected behavior

It should not use the main thread for 1.7 seconds.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions