NativeScript / worker-loader

36 stars 20 forks source link

web packing freeze #7

Closed erjdriver closed 6 years ago

erjdriver commented 6 years ago

Web-packing freezes..

The app is built successfully and I get the following message webpacking

`:asbg:clean UP-TO-DATE :deleteMetadata :deleteFlavors :deleteGeneratedBindings UP-TO-DATE :clean

BUILD SUCCESSFUL

Total time: 0.689 secs Running webpack for android... Project root: /Users/asrock/Documents/publish-android Snapshots build directory: /Users/asrock/Documents/publish-android/platforms/android/snapshot-build/build undefined 10% building modules 1/4 modules 3 active ...publish-android/app/light.android.css [at-loader] Using typescript@2.4.2 from typescript and "tsconfig.json" from /Users/asrock/Documents/publish-android/tsconfig.json.

10% building modules 3/4 modules 1 active ...publish-android/app/light.android.css(node:7774) DeprecationWarning: loaderUtils.parseQuery() received a non-string value which can be problematic, see https://github.com/webpack/loader-utils/issues/56 parseQuery() will be replaced with getOptions() in the next major version of loader-utils. 14% building modules 36/41 modules 5 active ...modules/tns-core-modules/text/span.js

`

and it hangs.

I've followed the steps in the README file - it's a TS project.

and

The funny thing is that the code was working and then I moved the code around a little bit and then I got the freeze.

As I was typing this out - the build unfroze and I got the following

`<--- Last few GCs --->

392102 ms: Mark-sweep 1214.9 (1434.7) -> 1214.2 (1434.7) MB, 1133.4 / 0.0 ms [allocation failure] [GC in old space requested]. 393194 ms: Mark-sweep 1214.2 (1434.7) -> 1214.0 (1434.7) MB, 1091.2 / 0.0 ms [allocation failure] [GC in old space requested]. 394446 ms: Mark-sweep 1214.0 (1434.7) -> 1221.5 (1411.7) MB, 1252.5 / 0.0 ms [last resort gc]. 395646 ms: Mark-sweep 1221.5 (1411.7) -> 1232.9 (1410.7) MB, 1199.5 / 0.0 ms [last resort gc].

<--- JS stacktrace --->

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

Security context: 0x2c2efe7cf781 1: doResolve [/Users/asrock/Documents/publish-android/node_modules/enhanced-resolve/lib/Resolver.js:~89] [pc=0x36085747e04f] (this=0x81771ab9849 <a Resolver with map 0x31eabdcbb9f9>,type=0x38a1cd30e7f1 <String[18]: described-relative>,request=0x2dfe926d80a9 <an Object with map 0x3c6ed1b439c9>,message=0x2dfe926d81c9 <String[146]: using description file: /Users/asrock/Documents/publish-androi...

FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory 1: node::Abort() [/usr/local/bin/node] 2: node::FatalException(v8::Isolate, v8::Local, v8::Local) [/usr/local/bin/node] 3: v8::internal::V8::FatalProcessOutOfMemory(char const, bool) [/usr/local/bin/node] 4: v8::internal::Factory::NewFixedArray(int, v8::internal::PretenureFlag) [/usr/local/bin/node] 5: v8::internal::HashTable<v8::internal::StringTable, v8::internal::StringTableShape, v8::internal::HashTableKey>::EnsureCapacity(v8::internal::Handle, int, v8::internal::HashTableKey, v8::internal::PretenureFlag) [/usr/local/bin/node] 6: v8::internal::StringTable::LookupKey(v8::internal::Isolate, v8::internal::HashTableKey) [/usr/local/bin/node] 7: v8::internal::StringTable::LookupString(v8::internal::Isolate, v8::internal::Handle) [/usr/local/bin/node] 8: v8::internal::LookupIterator::LookupIterator(v8::internal::Handle, v8::internal::Handle, v8::internal::LookupIterator::Configuration) [/usr/local/bin/node] 9: v8::internal::LookupIterator::PropertyOrElement(v8::internal::Isolate, v8::internal::Handle, v8::internal::Handle, bool, v8::internal::LookupIterator::Configuration) [/usr/local/bin/node] 10: v8::internal::Runtime::GetObjectProperty(v8::internal::Isolate, v8::internal::Handle, v8::internal::Handle) [/usr/local/bin/node] 11: v8::internal::Runtime_KeyedGetProperty(int, v8::internal::Object*, v8::internal::Isolate) [/usr/local/bin/node] 12: 0x3608541092a7 13: 0x36085747e04f child process exited with code null `

janbaykara commented 6 years ago

I get the same error. It happens when I try to import modules inside the worker file

altunyurt commented 6 years ago

Same here.

require("globals") inside worker file is ok, but any other require or import results in freeze.

interrobrian commented 5 years ago

I ran into this and determined it was ts-loader that was running out of memory. I switched to awesome-typescript-loader to fix it.