Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

compiler crash after updating to 5.0.8

See original GitHub issue

Issue

truffle compile causes a memory error. In version 5.0.7 compiling works fine.

Actual Results

λ truffle compile

Compiling your contracts...
===========================

<--- Last few GCs --->

[14948:000001CE41908F60]    77537 ms: Mark-sweep 1693.0 (1760.7) -> 1692.9 (1729.7) MB, 1169.6 / 0.0 ms  last resort GC in old space requested
[14948:000001CE41908F60]    78715 ms: Mark-sweep 1692.9 (1729.7) -> 1692.9 (1729.7) MB, 1178.1 / 0.0 ms  last resort GC in old space requested


<--- JS stacktrace --->

==== JS stack trace =========================================

Security context: 000001EBEFB25879 <JSObject>
    1: next [C:\Projects\everdragons\everdragons-contract\node_modules\babylon\lib\index.js:~682] [pc=0000000B3126C3FF](this=000003453A6DECC1 <Parser map = 000002D5FFC88559>)
    2: /* anonymous */ [C:\Projects\everdragons\everdragons-contract\node_modules\babylon\lib\index.js:~3507] [pc=0000000B3128FB00](this=000003453A6DECC1 <Parser map = 000002D5FFC88559>,base=000002E9072D4C79 <Node map = 0...

FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory
 1: node_module_register
 2: v8::internal::FatalProcessOutOfMemory
 3: v8::internal::FatalProcessOutOfMemory
 4: v8::internal::Factory::NewUninitializedFixedArray
 5: v8::internal::WasmDebugInfo::SetupForTesting
 6: v8::internal::interpreter::BytecodeArrayRandomIterator::UpdateOffsetFromIndex
 7: 0000000B310843C1

Environment

Operating System: Windows 10
Truffle version (truffle version): 5.0.8
node version (node --version): 8.12.0

Issue Analytics

State:
Created 5 years ago
Reactions:3
Comments:6 (4 by maintainers)

Top GitHub Comments

1reaction

eggplantzzzcommented, Mar 15, 2019

Ok, so I did a lot of testing and there is some conflict with babel-register. It is somehow causing require('path/to/cached/compiler') to hang in the loading strategy here and blow the heap. When I comment out require('babel-register') in the Truffle config, it is able to successfully compile. I’m not sure what we’re going to do about this but we’ll try and see what we can do for these to peacefully coexist 😃

0reactions

eggplantzzzcommented, Mar 28, 2019

So we provided a fix for this in version 5.0.10 that was just released. You should be able to get away with using babel-register without specifying the ignore option. Try it out and let me know if there are still some problems to address. Thanks!