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

Memory leak if dist folder is present #98

Closed
mvsde opened this issue Dec 10, 2020 · 1 comment
Closed

Memory leak if dist folder is present #98

mvsde opened this issue Dec 10, 2020 · 1 comment
Assignees
Labels

Comments

@mvsde
Copy link
Member

mvsde commented Dec 10, 2020

It’s a bit strange but if the dist folder is present, the whole thing goes down with a memory leak:

pangolin-core dev


● Pangolin.js █████████████████████████ sealing (92%)  
 asset processing

(node:66434) [DEP_WEBPACK_COMPILATION_ASSETS] DeprecationWarning: Compilation.assets will be frozen in future, all modifications are deprecated.
BREAKING CHANGE: No more changes should happen to Compilation.assets after sealing the Compilation.
	Do changes to assets earlier, e. g. in Compilation.hooks.processAssets.
	Make sure to select an appropriate stage from Compilation.PROCESS_ASSETS_STAGE_*.
(Use `node --trace-deprecation ...` to show where the warning was created)

<--- Last few GCs --->

[66434:0x5d79a90]    30569 ms: Mark-sweep (reduce) 2040.3 (2073.0) -> 2035.7 (2073.0) MB, 23.0 / 0.1 ms  (+ 46.9 ms in 19 steps since start of marking, biggest step 14.9 ms, walltime since start of marking 85 ms) (average mu = 0.309, current mu = 0.378) f[66434:0x5d79a90]    30591 ms: Scavenge 2037.4 (2069.5) -> 2036.7 (2069.5) MB, 3.0 / 0.0 ms  (average mu = 0.309, current mu = 0.378) task 


<--- JS stacktrace --->

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
 1: 0xa03530 node::Abort() [node]
 2: 0x94e471 node::FatalError(char const*, char const*) [node]
 3: 0xb7773e v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [node]
 4: 0xb77ab7 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [node]
 5: 0xd32345  [node]
 6: 0xd32ecf  [node]
 7: 0xd40f5b v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [node]
 8: 0xda073c v8::internal::ScavengeJob::Task::RunInternal() [node]
 9: 0xc6a96b non-virtual thunk to v8::internal::CancelableTask::Run() [node]
10: 0xa71704 node::PerIsolatePlatformData::RunForegroundTask(std::unique_ptr<v8::Task, std::default_delete<v8::Task> >) [node]
11: 0xa73569 node::PerIsolatePlatformData::FlushForegroundTasksInternal() [node]
12: 0x1379a66  [node]
13: 0x138c545  [node]
14: 0x137a398 uv_run [node]
15: 0xa438d4 node::NodeMainInstance::Run() [node]
16: 0x9d1735 node::Start(int, char**) [node]
17: 0x7f5dc70c0cb2 __libc_start_main [/lib/x86_64-linux-gnu/libc.so.6]
18: 0x96971c  [node]
Aborted (core dumped)
@mvsde mvsde added the bug label Dec 10, 2020
@mvsde mvsde self-assigned this Dec 10, 2020
@mvsde mvsde changed the title Memory leak if dist folder is present Memory leak if dist folder is present Dec 10, 2020
@mvsde mvsde added the v5 label Jan 13, 2021
@mvsde
Copy link
Member Author

mvsde commented Aug 17, 2021

This may have been resolved with dependency upgrades. Since I couldn’t reproduce this issue any more.

@mvsde mvsde closed this as completed Aug 17, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant