Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[bug] ueberzugpp probable synchronisation issue on slow machine #54

Closed
pirate486743186 opened this issue Jun 1, 2023 · 8 comments
Closed

Comments

@pirate486743186
Copy link

works fine with the old ueberzug method. But it quickly brakes with the new ueberzugpp method. Tested on Debian 11 64bits.

+ choice=
+ ueberzugpp cmd -s /tmp/ueberzugpp-21889.socket -a exit
terminate called after throwing an instance of 'std::system_error'
  what():  Connection refused
Aborted

the config bypasses the issue.

{
    "layer": {
        "no-opencv":true
    }
}
@jstkdng
Copy link
Owner

jstkdng commented Jun 1, 2023

Thanks for reporting, I'm gonna need a backtrace of the issue. Install debugsymbols if you don't have them. And fater that try to reproduce the issue. Once you have done it, run coredumpctl -1 dump and post the results here.

You can download the debug symbols from here. https://build.opensuse.org/package/binaries/home:justkidding/ueberzugpp/Debian_11

@pirate486743186
Copy link
Author

you mean this? i was expecting a large file.

Core was generated by `ueberzugpp layer --no-stdin --silent --use-escape-codes --pid-file /tmp/.479e4a'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x0000557181504e2d in Window::send_expose_event (this=0x0, xcoord=69, ycoord=420) at ./src/canvas/x11/window.cpp:132
132	./src/canvas/x11/window.cpp: No such file or directory.
[Current thread is 1 (Thread 0x7f582c71e700 (LWP 16386))]
(gdb) bt
#0  0x0000557181504e2d in Window::send_expose_event(int, int) (this=0x0, xcoord=69, ycoord=420)
    at ./src/canvas/x11/window.cpp:132
#1  0x0000557181502c41 in X11Canvas::clear() (this=0x557182b16df0)
    at /usr/include/c++/10/bits/unique_ptr.h:173
#2  0x000055718154eb4b in Application::execute(std::basic_string_view<char, std::char_traits<char> >)
    (this=0x7ffddb1e8880, cmd="{\"action\":\"add\",\"identifier\":\"fzfpreview\",\"max_width\":20,\"max_height\":17,\"x\":45,\"y\":3,\"path\":\"/tmp/lobster/lobster-images/  Building Star Trek [2016] (movie)  54044.jpg\"}") at ./src/application.cpp:108
#3  0x000055718154ef61 in Application::socket_loop() (this=0x7ffddb1e8880)
    at /usr/include/c++/10/string_view:133
#4  0x00007f583ee37ed0 in  () at /lib/x86_64-linux-gnu/libstdc++.so.6
#5  0x00007f583f6adea7 in start_thread (arg=<optimized out>) at pthread_create.c:477
#6  0x00007f583ec76a2f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

@pirate486743186
Copy link
Author

I read your edited message. Here it is. coredump.gz

@jstkdng
Copy link
Owner

jstkdng commented Jun 3, 2023

That coredump seems different from the first one, can you check ueberzugpp has crashed more than once? Just run coredumpctl | grep ueberzug

@pirate486743186
Copy link
Author

The second one is from an other test. I did some trial and error to get the coredump. I don't do this every day.

@jstkdng
Copy link
Owner

jstkdng commented Jun 3, 2023

I think I fixed the second issue you sent, it was indeed related to slow machines ,or rather, sending a lot of commands really fast, even on my PC it would crash, and it is a 5950X.

@pirate486743186
Copy link
Author

Normally, both are the same bug in two different tests.

@pirate486743186
Copy link
Author

I tried the latest from master. It seams solved for me. Most likely #53 is also solved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants