Closed mark2185 closed 2 years ago
I managed to get something out:
vifm: background.c:224: bg_check: Assertion `bg_jobs == NULL && "Job list shouldn't be used by anyone."' failed.
/usr/bin/vifmrun: line 21: 1778844 Aborted (core dumped) vifm "$@" 3>&-
Mine randomly crashes too when I try preview images using the e
or w
keys in vifm.
You might want to try the fresh commits (6 hours ago).
Or create an issue at vifm/vifm
. It doesn't seem like this is a vifmimg
problem.
You might want to try the fresh commits (6 hours ago).
Or create an issue at
vifm/vifm
. It doesn't seem like this is avifmimg
problem.You might want to try the fresh commits (6 hours ago).
Or create an issue at
vifm/vifm
. It doesn't seem like this is avifmimg
problem.
I just downloaded the latest commit on master, I will report back to see if anything changes. I doubt that this is a vifm/vifm problem because it only ever occurs when I try to preview images using vifmimg
Judging by error message, vifm
is crashing. Even if it is because of
vifmimg
, it is not vifm
ready for such a case.
Besides, it is an assert, specifically to catch such cases.
Judging by error message,
vifm
is crashing. Even if it is because ofvifmimg
, it is notvifm
ready for such a case.Besides, it is an assert, specifically to catch such cases.
To be clear, im not OP. I have no error message when vifm crashes on image preview. It just freezes forever until I have to kill and restart the app.
Sorry my fault, I was looking at the post @mark2185's message.
Then you may have a different reason. I sometimes also have
something similar to yours. vifmimg clear
hangs and vifm
waits
for it to complete. But this usually happens when the ueberzug
is dead.
There is nobody to subtract the message from FIFO_UEBERZUG
.
Sorry my fault, I was looking at the post @mark2185's message.
Then you may have a different reason. I sometimes also have something similar to yours.
vifmimg clear
hangs andvifm
waits for it to complete. But this usually happens when theueberzug
is dead. There is nobody to subtract the message fromFIFO_UEBERZUG
.
Oh okay, im glad im not the only one experiencing such an issue. any ideas for a workaround?
Nope. A named pipe is better than a regular pipe because it is possible to recreate a channel if it is cut off. But I don’t have the ability to catch this case, it is very rare.
Probably enough wait
or trap
to wait for ueberzug
to succeed.
You might want to try the fresh commits (6 hours ago).
Or create an issue at
vifm/vifm
. It doesn't seem like this is avifmimg
problem.
It seems to be gone, I'll close this and reopen if need be.
Thanks!
I can consistently make it crash by doing the following:
Minimal
vifmrc
:I don't see if there are any logs, and I'm not certain how to run it all under
gdb
.