4 ms·
This isn't Electron's fault. This is slacks fault. Look at the memory footprint of VS Code opening hundreds of files. A much much more substantial application t
by nerpderp83 9y ago
This isn't Electron's fault. This is slacks fault. Look at the memory footprint of VS Code opening hundreds of files. A much much more substantial application than slack that uses a small fraction of the memory. On my machine, VS code with hundreds of open files is using just over 200MB.
- jsnar 9y agoElectron could still be faulty: its multi process architecture makes application developer easier to write memory leaking code.