element-desktop creates /tmp/.org.chromium.Chromium.xxxxxx files when started, which are not deleted upon exit
See original GitHub issueDescription
Every time I start element-desktop there are /tmp/.org.chromium.Chromium.xxxxxx created and not deleted afterwards.
Steps to reproduce
- Start element-desktop
- Quit element-desktop
- See the contents of a
/tmpfolder
Electron always creates 2 files with ever changing names, but I suppose that they are essentially the same files every start, so I inspected them in a hex editor and to me it looks like electron unpacks keytar and seshat node modules. I also inspected the files generated during the build of element-desktop and only the gifwrap resides in app.asar.unpacked/node_modules/ everything else seems to be packed into app.asar. I also compare this to vscode, which keeps all the native modules outside app.asar. Could it be, that those modules should also be unpacked? And my suspicion is that if they are not, electron needs to unpack them every time it starts. Therefore I’m filling a bug here as it could be an issue with element-desktop build system. It could also happen to be electron issue. Anyway it would be nice not to generate extra temporary files.
Logs being sent: no
Version information
- Platform: desktop
For the desktop app:
- OS: Gentoo Linux
- Version: v1.7.26
Related issues I could find, but they didn’t help solve this issue: zulip/zulip-desktop#601 electron/electron#16097
Issue Analytics
- State:
- Created 2 years ago
- Reactions:2
- Comments:13 (2 by maintainers)

Top Related StackOverflow Question
yea been watching it past week, looks great