I discovered that packaged in Sparrow HWI 2.1.1 binary, doesn't always removes it's temporary directory.
It's not obvious what causes that behavior but I suspect it happens when there is USB communication error.
I was playing around and running both Ledger Live and Sparrow and after a few hours there were a few dozen copies of HWI temporary directories (usually named /tmp/_MEIXXXXXX). Each instance takes ~50MB and since most Linux installations limit /tmp to free space on root partition, it can cause issues pretty quickly.
At least in one instance, HWI obviously crashed and left it's temporary directory:
kernel: [201989.142012] hwi-2.1.1127641[261498]: segfault at 200 ip 00007f9c2a20a28b sp 00007f9c261fdd20 error 4 in libusb-1-150b88da.0.so.0.1.0[7f9c2a200000+17000]
I see no corresponding entries in sparrow.log
I can think of the following workaround:
- Run HWI binary with the following environment variable: TMPDIR=/tmp/HWI-123
- When execution is finished, make sure /tmp/HWI-123 is empty
I discovered that packaged in Sparrow HWI 2.1.1 binary, doesn't always removes it's temporary directory.
It's not obvious what causes that behavior but I suspect it happens when there is USB communication error.
I was playing around and running both Ledger Live and Sparrow and after a few hours there were a few dozen copies of HWI temporary directories (usually named /tmp/_MEIXXXXXX). Each instance takes ~50MB and since most Linux installations limit /tmp to free space on root partition, it can cause issues pretty quickly.
At least in one instance, HWI obviously crashed and left it's temporary directory:
kernel: [201989.142012] hwi-2.1.1127641[261498]: segfault at 200 ip 00007f9c2a20a28b sp 00007f9c261fdd20 error 4 in libusb-1-150b88da.0.so.0.1.0[7f9c2a200000+17000]
I see no corresponding entries in sparrow.log
I can think of the following workaround: