Opened 3 days ago
Last modified 3 days ago
#63606 new defect (bug)
npm run dev: Warning: Maximum call stack size exceeded
Reported by: |
|
Owned by: | |
---|---|---|---|
Milestone: | Awaiting Review | Priority: | normal |
Severity: | normal | Version: | 3.7 |
Component: | Build/Test Tools | Keywords: | has-patch has-test-info needs-testing 2nd-opinion |
Focuses: | Cc: |
Description
When running npm run dev
an error appears
Warning: Maximum call stack size exceeded
Before it finally crashes with
FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
Commented on Slack and @desrosj informed that he found this when a large number of plugins were sitting on the plugins
directory. Presently I have 54 units (all non-active, but still sitting there)
I tried to remove them all, and it appears that this solves the problem.
This has been sitting here since the inception of the first Gruntfile verison [25001]
Change History (3)
This ticket was mentioned in PR #9030 on WordPress/wordpress-develop by @SirLouen.
3 days ago
#1
- Keywords has-patch added; needs-patch removed
#3
@
3 days ago
- Keywords 2nd-opinion added
More information
I've noted that with woocommerce
plugin is possible to reproduce this
Not easy to reproduce though: the more files, the easier.
I think that just excluding plugins in watch
is enough.
Maybe just adding akismet, although in watch mode, akismet is totally irrelevant. So probably it can be ignored.
Testing & Reproduction Instructions
node_modules
files it will be easier to reproduce. The more files in the plugins directory, the better to reproduce thisnpm run dev
Warning: Maximum call stack size exceeded
With the patch, this should be gone
Trac ticket: https://core.trac.wordpress.org/ticket/63606