raml-org / raml-js-parser-2

(deprecated)

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

out of memory

ginus opened this issue · comments

commented

<--- Last few GCs --->

[16371:0x102802400] 21957 ms: Mark-sweep 665.5 (708.8) -> 665.5 (708.8) MB, 275.3 / 0.0 ms allocation failure GC in old space requested
[16371:0x102802400] 22246 ms: Mark-sweep 665.5 (708.8) -> 665.5 (675.8) MB, 288.6 / 0.0 ms last resort GC in old space requested
[16371:0x102802400] 22518 ms: Mark-sweep 665.5 (675.8) -> 665.5 (675.8) MB, 271.5 / 0.0 ms last resort GC in old space requested

<--- JS stacktrace --->

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

Security context: 0x2fa5c5225ee1
1: mergeLibs(aka mergeLibs) [/Users/art/.nvm/versions/node/v8.9.4/lib/node_modules/api-console-cli/node_modules/raml-1-parser/dist/parser/highLevelImpl.js:~2541] [pc=0x30bb33f250a3](this=0x2fa559382311 ,from=0x2fa57d16a3b9 ,to=0x2fa57d16a3b9 )
3: mergeLibs(aka mergeLibs) [/Users/art/.nvm/versions/node/v8...

FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory
1: node::Abort() [/Users/art/.nvm/versions/node/v8.9.4/bin/node]
2: node::FatalException(v8::Isolate*, v8::Localv8::Value, v8::Localv8::Message) [/Users/art/.nvm/versions/node/v8.9.4/bin/node]
3: v8::internal::V8::FatalProcessOutOfMemory(char const*, bool) [/Users/art/.nvm/versions/node/v8.9.4/bin/node]
4: v8::internal::Factory::NewUninitializedFixedArray(int) [/Users/art/.nvm/versions/node/v8.9.4/bin/node]
5: v8::internal::(anonymous namespace)::ElementsAccessorBase<v8::internal::(anonymous namespace)::FastPackedObjectElementsAccessor, v8::internal::(anonymous namespace)::ElementsKindTraits<(v8::internal::ElementsKind)2> >::GrowCapacity(v8::internal::Handlev8::internal::JSObject, unsigned int) [/Users/art/.nvm/versions/node/v8.9.4/bin/node]
6: v8::internal::Runtime_GrowArrayElements(int, v8::internal::Object**, v8::internal::Isolate*) [/Users/art/.nvm/versions/node/v8.9.4/bin/node]
7: 0x30bb33b0463d
8: 0x30bb33f250a3

Hi @ginus !

We need a reproduction sequence or for your case.

commented

api-console dev api2.raml -s ~/projects/api-console --no-bower --verbose
info: Preparing sources before build...
info: Creating working directory...
info: Working directory created: /var/folders/6w/_mr83fjj4fn_mz70z378556w0000gn/T/tmp-31848rYQSRXA41OQu
info: Copying local API Console files to the working dir.
info: Copying files from /Users/art/projects/api-console
info: Template to use: standalone-plain.tpl
info: Copying template file to the working directory...
info: Updating main file template variables...
info: Getting the RAML data...

<--- Last few GCs --->

[31848:0x102802400] 12759 ms: Mark-sweep 665.5 (709.8) -> 665.5 (709.8) MB, 298.8 / 0.0 ms allocation failure GC in old space requested
[31848:0x102802400] 13043 ms: Mark-sweep 665.5 (709.8) -> 665.5 (675.8) MB, 284.4 / 0.0 ms last resort GC in old space requested
[31848:0x102802400] 13319 ms: Mark-sweep 665.5 (675.8) -> 665.5 (675.8) MB, 275.6 / 0.0 ms last resort GC in old space requested
....

We need instructions on how to install and use the 'api-console' plugin and content of your 'api2.raml'

Regards,
Konstantin

commented

api2.raml and relevant file: http://ginus.coding.me/cnc.db/raml.zip

Thanks for your report, @ginus.

The fix is in the 'devlop' branches set now and is going to be released in 1.1.41.

Regards,
Konstantin