search

plotly / angular-plotly.js

MIT License
233 stars 78 forks source link

Angular 12 support #175

Open martingratt opened 3 years ago

martingratt commented 3 years ago

Hello, I want to know if Plotly is supporting Angular12? I tried to install Plotly on a plain Angular12 project and getting the following error:

\ Generating browser application bundles (phase: building)... <--- Last few GCs ---> 4)[23632:000001C536715940] 63927 ms: Mark-sweep 2050.9 (2059.2) -> 2048.4 (2061.7) MB, 563.3 / 0.0 ms (+ 463.1 ms in 93 steps since start of marking, biggest step 11.5 ms, walltime since start of marking 1051 ms) (average mu = 0.108, current mu = 0.024)[23632:000001C536715940] 65636 ms: Mark-sweep 20 50.3 (2061.7) -> 2048.9 (2058.5) MB, 1578.8 / 0.1 ms (+ 122.3 ms in 28 steps since start of marking, biggest step 8.6 ms, walltime since start of marking 1709 ms) (average mu = 0.047, current mu = 0.005)

<--- JS stacktrace --->

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

0: ExitFrame [pc: 00007FF6B851993D]
1: StubFrame [pc: 00007FF6B851A86D]
2: StubFrame [pc: 00007FF6B8556A86]

Security context: 0x001ef44c08d1 3: replace [0000001EF44CCC71](this=0x016d094be4b9 <String[101]: C:\Users\m.gratt\WebstormProjects\testplotly\my-project\node_modules\plotly.js-dist-min\plotly.min.js>,0x039ef0859851 <JSRegExp <String[#2]: \>>,0x004e9f652361 <String[#1]: />) 4: mark [0000019C44496599] [...

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory 1: 00007FF6B78E035F napi_wrap+119615 2: 00007FF6B7887666 v8::internal::OrderedHashTable<v8::internal::OrderedHashSet,1>::NextTableOffset+38102 3: 00007FF6B7888466 v8::internal::OrderedHashTable<v8::internal::OrderedHashSet,1>::NextTableOffset+41686 4: 00007FF6B80C451E v8::Isolate::ReportExternalAllocationLimitReached+94 5: 00007FF6B80AC6C1 v8::SharedArrayBuffer::Externalize+833 6: 00007FF6B7F5DE9C v8::internal::Heap::EphemeronKeyWriteBarrierFromCode+1436 7: 00007FF6B7F690E0 v8::internal::Heap::ProtectUnprotectedMemoryChunks+1312 8: 00007FF6B7F65BF4 v8::internal::Heap::PageFlagsAreConsistent+3204 9: 00007FF6B7F5B3F3 v8::internal::Heap::CollectGarbage+1283 10: 00007FF6B7F59A64 v8::internal::Heap::AddRetainedMap+2500 11: 00007FF6B7F7ADAD v8::internal::Factory::NewFillerObject+61 12: 00007FF6B7CDE381 v8::internal::interpreter::JumpTableTargetOffsets::iterator::operator=+1665 13: 00007FF6B851993D v8::internal::SetupIsolateDelegate::SetupHeap+546925 14: 00007FF6B851A86D v8::internal::SetupIsolateDelegate::SetupHeap+550813 15: 00007FF6B8556A86 v8::internal::SetupIsolateDelegate::SetupHeap+797110 16: 00007FF6B8506487 v8::internal::SetupIsolateDelegate::SetupHeap+467895 17: 000000B030FCAF9F npm ERR! code ELIFECYCLE npm ERR! errno 134 npm ERR! my-project@0.0.0 start: ng serve npm ERR! Exit status 134 npm ERR! npm ERR! Failed at the my-project@0.0.0 start script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in: npm ERR! C:\Users\m.gratt\AppData\Roaming\npm-cache_logs\2021-09-28T07_08_17_306Z-debug.log

Process finished with exit code 134

andrefarzat commented 3 years ago

Hello, @martingratt. This is very strange, for the issue is in the node's garbage collector. What is the nodejs' and npm's version you're using?

mherndon7 commented 3 years ago

I am having the same issue.

Angular 12.2.11 Node v14.18.1 npm v8.3.1

So I re-installed node modules and it seemed to fix the issue and loads correctly now