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

ape hardhat local node Reached heap limit Allocation failed - JavaScript heap out of memory [APE-1468] #159

Open
iris112 opened this issue Oct 20, 2023 · 0 comments

Comments

@iris112
Copy link

iris112 commented Oct 20, 2023

Environment information

  • ape and plugin versions:
$ ape --version
0.6.22

$ ape plugins list
  alchemy     0.6.5
  hardhat     0.6.13
  solidity    0.6.9
  vyper       0.6.11
  • Python Version: 3.10.12
  • OS: linux

What went wrong?

Please include information like:

  • what command you ran
    ape test
  • the code that caused the failure (see this link for help with formatting code)
    compile and run test cases
  • full output of the error you received
th_getTransactionReceipt
eth_getTransactionByHash
eth_gasPrice

<--- Last few GCs --->

[117881:0x7107180]   164897 ms: Scavenge 3992.4 (4118.7) -> 3989.4 (4120.0) MB, 10.6 / 0.0 ms  (average mu = 0.891, current mu = 0.817) allocation failure;
[117881:0x7107180]   164974 ms: Scavenge 3996.6 (4123.2) -> 3994.4 (4142.0) MB, 36.6 / 0.0 ms  (average mu = 0.891, current mu = 0.817) allocation failure;
[117881:0x7107180]   167246 ms: Mark-sweep 3996.8 (4143.0) -> 3995.7 (4146.0) MB, 2266.6 / 0.0 ms  (average mu = 0.670, current mu = 0.139) allocation failure; scavenge might not succeed


<--- JS stacktrace --->

FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
1: 0xb83f50 node::Abort() [/home/one/.nvm/versions/node/v18.17.0/bin/node]
2: 0xa94834  [/home/one/.nvm/versions/node/v18.17.0/bin/node]
3: 0xd647c0 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [/home/one/.nvm/versions/node/v18.17.0/bin/node]
4: 0xd64b67 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [/home/one/.nvm/versions/node/v18.17.0/bin/node]
5: 0xf42265  [/home/one/.nvm/versions/node/v18.17.0/bin/node]
6: 0xf5474d v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [/home/one/.nvm/versions/node/v18.17.0/bin/node]
7: 0xf2ee4e v8::internal::HeapAllocator::AllocateRawWithLightRetrySlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [/home/one/.nvm/versions/node/v18.17.0/bin/node]
8: 0xf30217 v8::internal::HeapAllocator::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [/home/one/.nvm/versions/node/v18.17.0/bin/node]
9: 0xf10760 v8::internal::Factory::AllocateRaw(int, v8::internal::AllocationType, v8::internal::AllocationAlignment) [/home/one/.nvm/versions/node/v18.17.0/bin/node]
10: 0xf081d4 v8::internal::FactoryBase<v8::internal::Factory>::AllocateRawWithImmortalMap(int, v8::internal::AllocationType, v8::internal::Map, v8::internal::AllocationAlignment) [/home/one/.nvm/versions/node/v18.17.0/bin/node]
11: 0xf0a488 v8::internal::FactoryBase<v8::internal::Factory>::NewRawOneByteString(int, v8::internal::AllocationType) [/home/one/.nvm/versions/node/v18.17.0/bin/node]
12: 0xf20e5e v8::internal::Factory::NewStringFromOneByte(v8::base::Vector<unsigned char const> const&, v8::internal::AllocationType) [/home/one/.nvm/versions/node/v18.17.0/bin/node]
13: 0xd73953 v8::String::NewFromOneByte(v8::Isolate*, unsigned char const*, v8::NewStringType, int) [/home/one/.nvm/versions/node/v18.17.0/bin/node]
14: 0xc6d35a node::StringBytes::Encode(v8::Isolate*, char const*, unsigned long, node::encoding, v8::Local<v8::Value>*) [/home/one/.nvm/versions/node/v18.17.0/bin/node]
15: 0xb5985a  [/home/one/.nvm/versions/node/v18.17.0/bin/node]
16: 0x1688e2f  [/home/one/.nvm/versions/node/v18.17.0/bin/node]
Stopping 'Hardhat node' process.

How can it be fixed?

Fill this in if you have ideas on how the bug could be fixed.

@vany365 vany365 changed the title ape hardhat local node Reached heap limit Allocation failed - JavaScript heap out of memory ape hardhat local node Reached heap limit Allocation failed - JavaScript heap out of memory [APE-1468] Oct 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant