Skip to content

Long startup && Long Rebuild && Random crush #9952

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

Open
SpeedySH opened this issue Oct 29, 2020 · 4 comments
Open

Long startup && Long Rebuild && Random crush #9952

SpeedySH opened this issue Oct 29, 2020 · 4 comments

Comments

@SpeedySH
Copy link

#9482 # Describe the bug
I just update to last versions on TypeScript + React. And get this bug 👍

Did you try recovering your dependencies?

Yes, i try.
Proof:
изображение
My Dependencies:
"dependencies": { "@testing-library/jest-dom": "^5.11.5", "@testing-library/react": "^11.1.0", "@testing-library/user-event": "^12.1.10", "clsx": "^1.1.1", "date-fns": "^2.16.1", "history": "^5.0.0", "idb": "^5.0.7", "nanoid": "^3.1.16", "node-sass": "^4.14.1", "normalize.css": "^8.0.1", "react": "^17.0.1", "react-dom": "^17.0.1", "react-redux": "^7.2.2", "react-redux-loading-bar": "^5.0.0", "react-router-dom": "^5.2.0", "react-scripts": "^4.0.0", "react-spring": "^8.0.27", "redux": "^4.0.5", "redux-devtools-extension": "^2.13.8", "redux-logger": "^3.0.6", "redux-thunk": "^2.3.0", "source-map-explorer": "^2.5.0" }, "devDependencies": { "@types/jest": "^26.0.15", "@types/node": "^14.14.6", "@types/react": "^16.9.55", "@types/react-dom": "^16.9.9", "@types/react-redux": "^7.1.9", "@types/react-router-dom": "^5.1.6", "@types/redux-logger": "^3.0.8", "@typescript-eslint/eslint-plugin": "^4.6.0", "@typescript-eslint/parser": "^4.6.0", "babel-eslint": "^10.1.0", "eslint-config-airbnb-typescript": "^12.0.0", "eslint-config-prettier": "^6.15.0", "eslint-plugin-import": "^2.22.0", "eslint-plugin-jsx-a11y": "^6.4.1", "eslint-plugin-no-use-extend-native": "^0.5.0", "eslint-plugin-optimize-regex": "^1.2.0", "eslint-plugin-promise": "^4.2.1", "eslint-plugin-react": "^7.21.5", "eslint-plugin-react-hooks": "^4.2.0", "eslint-plugin-sonarjs": "^0.5.0", "eslint-plugin-unicorn": "^23.0.0", "husky": "^4.3.0", "lint-staged": "^10.5.0", "prettier": "^2.1.2", "typescript": "^4.0.5" },

Which terms did you search for in User Guide?

Yes. i search.

Environment

`PS C:\Users\Melon\Desktop\aviasales-test-task> npx create-react-app --info
npx: установлен (translate: install) 91 в 22.017s

Environment Info:

current version of create-react-app: 4.0.0
running from C:\Users\Melon\AppData\Roaming\npm-cache_npx\3908\node_modules\create-react-app

System:
OS: Windows 10 10.0.18363
CPU: (4) x64 Intel(R) Core(TM) i3-4130 CPU @ 3.40GHz
Binaries:
Node: 14.14.0 - C:\Program Files\nodejs\node.EXE
Yarn: Not Found
npm: 6.14.8 - C:\Program Files\nodejs\npm.CMD
Browsers:
Chrome: Not Found
Edge: Spartan (44.18362.449.0)
Internet Explorer: Not Found
(I dont't know why this stuff no detect firefox. Firefox-DEV: 83.0b4
npmPackages:
react: ^17.0.1 => 17.0.1
react-dom: ^17.0.1 => 17.0.1
react-scripts: ^4.0.0 => 4.0.0
npmGlobalPackages:
create-react-app: Not Found
`

Steps to reproduce

You can clone my project and try ( https://github.com/MeloncholyShiro/-Aviasales-Test-Task- )

  1. npm run start
  2. Fix any stuff in files like 5-10 minutes active work
  3. Get crush 👍

Actual behavior

I have stuck trace :D

`<--- Last few GCs --->

[10888:000002130E0BD4D0] 1685067 ms: Mark-sweep 2022.2 (2072.4) -> 2005.9 (2073.2) MB, 2627.5 / 0.1 ms (average mu = 0.210, current mu = 0.068) allocation failure scavenge might not succeed
[10888:000002130E0BD4D0] 1686782 ms: Mark-sweep 2022.2 (2073.4) -> 2003.9 (2072.4) MB, 1618.1 / 0.1 ms (average mu = 0.154, current mu = 0.057) allocation failure scavenge might not succeed

<--- JS stacktrace --->

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
1: 00007FF72FB61C0F napi_wrap+109135
2: 00007FF72FB06B56 v8::internal::OrderedHashTablev8::internal::OrderedHashSet,1::NumberOfElementsOffset+33350
3: 00007FF72FB07926 node::OnFatalError+294
4: 00007FF7303D62FE v8::Isolate::ReportExternalAllocationLimitReached+94
5: 00007FF7303BB14D v8::SharedArrayBuffer::Externalize+781
6: 00007FF73026557C v8::internal::Heap::EphemeronKeyWriteBarrierFromCode+1516
7: 00007FF7302708DA v8::internal::Heap::ProtectUnprotectedMemoryChunks+1258
8: 00007FF73026DA89 v8::internal::Heap::PageFlagsAreConsistent+2457
9: 00007FF730262621 v8::internal::Heap::CollectGarbage+2033
10: 00007FF730260825 v8::internal::Heap::AllocateExternalBackingStore+1365
11: 00007FF730280D47 v8::internal::Factory::NewFillerObject+183
12: 00007FF72FFAE561 v8::internal::interpreter::JumpTableTargetOffsets::iterator::operator=+1409
13: 00007FF73045EE4D v8::internal::SetupIsolateDelegate::SetupHeap+463949
14: 00007FF7303F3B8B v8::internal::SetupIsolateDelegate::SetupHeap+24971
15: 00007FF7304E23D2 v8::internal::SetupIsolateDelegate::SetupHeap+1001938
16: 00007FF7303F7832 v8::internal::SetupIsolateDelegate::SetupHeap+40498
17: 000002ED75FF2956
 ERROR  Command failed with exit code 134.`

@dimazuien
Copy link

Can confirm long rebuilds. After updating react/react-dom/react-scripts on my project to ^17/^17/^4 rebuilds had become noticeably slower. Rebuilds had become fast again after reverting packages back to ^16/^16/^3

@fastie9000
Copy link

same here

@ChiefORZ
Copy link

ChiefORZ commented Nov 2, 2020

we stumbled upon the same issue on developing with the newest version of CRA. and found out that it is extreeemly slow, when you have a custom .eslintrc in your create-react-app project. when removing the custom eslint config - the hot-reload in development mode seams back to the normal speed.

it is probably, because the EXTEND_ESLINT got turned on by default. we are reverting back to CRA@^3 for now...

@stale
Copy link

stale bot commented Dec 25, 2020

This issue has been automatically marked as stale because it has not had any recent activity. It will be closed in 5 days if no further activity occurs.

@stale stale bot added the stale label Dec 25, 2020
@stale stale bot removed the stale label Apr 6, 2021
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

4 participants