Build instructions? about vscode-debug-visualizer HOT 9 CLOSED

See here for build instructions.
For some reason I got a JavaScript heap out of memory error when running yarn build on the root, but I guess that was just bad luck.

from vscode-debug-visualizer.

I'll improve that. Shouldn't require any global dependencies though.

from vscode-debug-visualizer.

I got the out of memory error too when running yarn build on the root

$ webpack
Starting type checking service...

<--- Last few GCs --->

[36868:000001E6E094CEF0]    67384 ms: Mark-sweep 1331.2 (1440.4) -> 1318.8 (1441.9) MB, 565.8 / 0.0 ms  (average mu = 0.128, current mu = 0.035) allocation failure scavenge might not succeed
[36868:000001E6E094CEF0]    67977 ms: Mark-sweep 1332.9 (1441.9) -> 1320.5 (1443.9) MB, 576.9 / 0.0 ms  (average mu = 0.080, current mu = 0.028) allocation failure scavenge might not succeed


<--- JS stacktrace --->

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

    0: ExitFrame [pc: 00000080E655C5C1]
Security context: 0x02a116b1e6e9 <JSObject>
    1: clone [000003C403A25789] [C:\dev\misc\vscode-debug-visualizer\node_modules\terser\dist\bundle.min.js:~1] [pc=00000080E7799508](this=0x025fe8a2e5c9 <AST_Binary map = 0000010E836C55F1>,e=0x01cd447828c9 <true>)
    2: /* anonymous */ [000002073C0BBA21] [C:\dev\misc\vscode-debug-visualizer\node_modules\terser\dist\bundle.min.js:~1] [pc=00000080E779D913]...

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
 1: 00007FF7F10EF04A v8::internal::GCIdleTimeHandler::GCIdleTimeHandler+5114
 2: 00007FF7F10CA0C6 node::MakeCallback+4518
 3: 00007FF7F10CAA30 node_module_register+2032
 4: 00007FF7F13520EE v8::internal::FatalProcessOutOfMemory+846
 5: 00007FF7F135201F v8::internal::FatalProcessOutOfMemory+639
 6: 00007FF7F1872BC4 v8::internal::Heap::MaxHeapGrowingFactor+9556
 7: 00007FF7F1869C46 v8::internal::ScavengeJob::operator=+24310
 8: 00007FF7F186829C v8::internal::ScavengeJob::operator=+17740
 9: 00007FF7F1870F87 v8::internal::Heap::MaxHeapGrowingFactor+2327
10: 00007FF7F1871006 v8::internal::Heap::MaxHeapGrowingFactor+2454
11: 00007FF7F142CDB7 v8::internal::Factory::NewFillerObject+55
12: 00007FF7F14C2CC6 v8::internal::WasmJs::Install+29414
13: 00000080E655C5C1

I tried running again and got the same error.

I tested all the build command and it is yarn build-ui that runs into the error, the rest of them work fine.

from vscode-debug-visualizer.

Thanks!

But can you please expound a bit more on architecture? What are the projects I am supposed to run "yard dev" inside? Why is there a web server involved? 😕

The immediate problem I am having is that when I open a new visualizer view while debugging, it comes up completely blank.

from vscode-debug-visualizer.

I'll improve the docs a little bit tomorrow, however I assume basic knowledge of webpack and other js technologies (without implying anything). The Webserver is from webpack dev server to enable hot releading the ui. This is not part of the deployed extension.

from vscode-debug-visualizer.

I've added an Architecture chapter to the root readme. I'll add more details over time.

from vscode-debug-visualizer.

It took a ridiculously long time (~4 minutes!!!) but yarn build-ui finally worked. The next build took ~2.4 minutes, which is somewhat better I guess lol. I have 16 gigs of memory and a new laptop so not sure what is taking so much time 🤔 . My OS is windows 10.

from vscode-debug-visualizer.

I did some more testing and found that yarn dev only takes 40 seconds to complete. yarn dev-playground takes a similar amount of time. Makes sense that it's faster given that it's not running in production mode I suppose. I tried removing all the plugins but that didn't seem to have much of a impact on the build time. That makes me more suspicious of ts-loader.

@hediet What version OS / node / yarn do you have? I wonder if it runs faster on linux or a updated version of node or something.

OS: Windows 10
C:\dev\vscode-debug-visualizer\webview>node -v
v10.16.3

C:\dev\vscode-debug-visualizer\webview>yarn -v
1.17.3

from vscode-debug-visualizer.

I restructured the project. All the visualizations & and an improved playground now live here.

Also, I configured github actions to build this extension on each master commit. That should make building reproducible. I'm getting heap errors now too, but fixed that by increasing the allowed memory usage for nodejs. I'm using windows/node v14.3.0 btw.

from vscode-debug-visualizer.