gws,
@gws@mstdn.social avatar

Note to self: Disassembling a 1.4GB module inside devtools is a bad idea. It can do it - it just can't display the result:

https://github.com/ChromeDevTools/devtools-frontend/blob/ca54fd164e5c1c4d395180594a116ec29a280b39/front_end/core/sdk/Script.ts#L220C43-L220C43

Welp. Time to hack devtools to discard the first gigabyte of text I guess...

zobier,
zobier avatar

@gws :thinking: it doesn't need to disassemble the whole thing just the symbol table and the page of code you're currently looking at, could be an interesting perf improvement to experiment with

voxpelli,
@voxpelli@mastodon.social avatar

@gws Sorry, I got stuck on the ”a 1.4GB wasm module”, that sounds like quite a big individual file?

gws,
@gws@mstdn.social avatar

@voxpelli Yes, I'm experimenting with something large. Though I did exaggerate a little, it's just the text disassembly that's over a GB, the wasm itself is smaller and compresses fairly well.

$ du -h module.wasm
160M module.wasm

$ wasm-dis module.wasm > module.txt
$ du -h module.txt
1.4G module.txt

$ gzip -k module.wasm
$ du -h module.wasm.gz
18M module.wasm.gz

voxpelli,
@voxpelli@mastodon.social avatar

@gws Ah, makes sense, text representation is for sure not very efficient

How easy is it to split a big WASM file into smaller ones that are maybe even loaded dynamically?

  • All
  • Subscribed
  • Moderated
  • Favorites
  • webassembly
  • DreamBathrooms
  • everett
  • InstantRegret
  • magazineikmin
  • thenastyranch
  • rosin
  • GTA5RPClips
  • Durango
  • Youngstown
  • slotface
  • khanakhh
  • kavyap
  • ngwrru68w68
  • tacticalgear
  • JUstTest
  • osvaldo12
  • tester
  • cubers
  • cisconetworking
  • mdbf
  • ethstaker
  • modclub
  • Leos
  • anitta
  • normalnudes
  • megavids
  • provamag3
  • lostlight
  • All magazines