You are not logged in.
After my last full systeem update (Saturday 2021/27/02) Libreoffice Calc crashes when manipulating filters with.
double free or corruption (!prev)
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = soffice.bin path = /usr/lib/libreoffice/program pid = 49025
KCrash: Arguments: /usr/lib/libreoffice/program/soffice.bin --nocrashhandlerAny idea what this error means? I use KDE.
Last edited by firewalker (2021-03-09 10:21:24)
Γίνε ρεαλιστής, μείνε ονειροπόλος ...
Offline
Now it crashed with corrupted size vs. prev_size
corrupted size vs. prev_size
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = soffice.bin path = /usr/lib/libreoffice/program pid = 51940
KCrash: Arguments: /usr/lib/libreoffice/program/soffice.bin --nocrashhandlerΓίνε ρεαλιστής, μείνε ονειροπόλος ...
Offline
Now, with corrupted double-linked list.
What could be the common on those errors? Glibc?
Γίνε ρεαλιστής, μείνε ονειροπόλος ...
Offline
stackoverflow
Is this really the entire backtrace/crashlog you can get? coredumpctl?
Do you use the KDE/plasma SAL and what if you don't?
Offline
coredumpctl list, doesn't show any coredump for libreoffice. I will try to crash contisniously and check for a coredump. I am trying to attach gdb but it doesn't seem to work.
Γίνε ρεαλιστής, μείνε ονειροπόλος ...
Offline
You need to
a) attach it to soffice.bin (libreoffice etc. are scripts)
b) "echo 0 | sudo tee /proc/sys/kernel/yama/ptrace_scope" in order to be allowed to
Edit: "doesn't seem to work" is usually not a helpful problem description, see the stickies ![]()
Last edited by seth (2021-03-01 14:46:22)
Offline
I tried to attach gdb to soffice.bin but it would freeze it. Not just libreoffice. It will freeze anything gui related until I kill gdb. It;s been a while since I had to debug a program.
GNU gdb (GDB) 10.1
Copyright (C) 2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-pc-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word".
Attaching to process 6026
[New LWP 6033]
[New LWP 6034]
[New LWP 6035]
[New LWP 6037]
[New LWP 6041]
[New LWP 6042]
[New LWP 6043]
[New LWP 6044]
[New LWP 6045]
[New LWP 6046]
[New LWP 6047]
[New LWP 6048]
[New LWP 6049]
[New LWP 6050]
[New LWP 6051]
[New LWP 6052]
[New LWP 6053]
[New LWP 6054]
[New LWP 6066]
[New LWP 6562]
Error while reading shared library symbols for /usr/lib/libpthread.so.0:
Cannot find user-level thread for LWP 6562: generic error
0x00007fe8f43dc37f in poll () from /usr/lib/libc.so.6
(gdb) c
Continuing.
Cannot find user-level thread for LWP 6906: generic error
Quit) Γίνε ρεαλιστής, μείνε ονειροπόλος ...
Offline
OK... The same happens to a windows version of Libreoffice. I will try to generate a coredump on Arch and report it upstream.
Γίνε ρεαλιστής, μείνε ονειροπόλος ...
Offline
I don't think stopping soffice.bin in the debugger could somehow freeze the entire GUI - did you maybe attach to kwin?
You could also edit the libreoffice script to "gdb soffice.bin" where you'd need to "run", cause the crash and then "bt".
Offline
I can move the mouse but I can't click anything. If I attach gdb from a terminal (Ctrl+Shift+F2), when the "GUI freezes", pressing "c" on gdb it says
Cannot execute this command while the selected thread is running.
It is like an invisible open file dialog or a message box that takes all focus. I really don't know how to describe it. I will try to screen capture it.
Γίνε ρεαλιστής, μείνε ονειροπόλος ...
Offline
Do you attach gdb to soffice.bin *after* it has crashed and drkonqi is already presenting your a crash dialog?
Offline
No. I attach it before the crash. Dr doesn't presents a dialog. After several tries, only the GUI of libreoffice locked. See the following video. I found some references for a gdb bug?
Γίνε ρεαλιστής, μείνε ονειροπόλος ...
Offline
This looks like a glibc mismatch and would fit your overall libreoffice issues.
I don't see a preloaded glibc in the general libreoffice-fresh package, but did you do anthing itr. or something as terrible as symlinking libc/libpthread versions around?
pacman -Qkk glibc
ls -l /usr/lib/libc.* /usr/lib/libpthread*Offline
I don;t remember messing with glibc. An the crash of libreoffice also happens in a Windows 10 system.
[11:43 - firewalker@laptop ~]$ pacman -Qkk glibc
backup file: glibc: /etc/locale.gen (Modification time mismatch)
backup file: glibc: /etc/locale.gen (Size mismatch)
glibc: 1578 total files, 0 altered files
[11:43 - firewalker@laptop ~]$ ls -l /usr/lib/libc.* /usr/lib/libpthread*
-rw-r--r-- 1 root root 5285168 Feb 13 23:39 /usr/lib/libc.a
-rw-r--r-- 1 root root 255 Feb 13 23:39 /usr/lib/libc.so
lrwxrwxrwx 1 root root 12 Feb 13 23:39 /usr/lib/libc.so.6 -> libc-2.33.so
-rwxr-xr-x 1 root root 154032 Feb 13 23:39 /usr/lib/libpthread-2.33.so
-rw-r--r-- 1 root root 420330 Feb 13 23:39 /usr/lib/libpthread.a
lrwxrwxrwx 1 root root 15 Feb 13 23:39 /usr/lib/libpthread.so -> libpthread.so.0
lrwxrwxrwx 1 root root 18 Feb 13 23:39 /usr/lib/libpthread.so.0 -> libpthread-2.33.soI submitted an upstream bug report. I included the file that causes the crash and a video demonstrating the crash.
Γίνε ρεαλιστής, μείνε ονειροπόλος ...
Offline
I can no logger reproduce the issue on Windows 10. It seems that the crash on windows was unrelated. After a system restart no more crashes. Back to square one...
Γίνε ρεαλιστής, μείνε ονειροπόλος ...
Offline
It seems more people corfimd it. On GNU/Linux and on Windows.
https://bugs.documentfoundation.org/sho … ?id=140754
Still dont;t know what the issue with gdb is.
Γίνε ρεαλιστής, μείνε ονειροπόλος ...
Offline
An early stackoverflow or some preloaded lib or a static link … or something else ![]()
Try to run soffice.bin in gdb by editing the libreoffice script (you'll have to run it from an interactive shell and "run" it to make it do anything.
Offline
The fix will be available on version 7.2.0.
As a workaround someone could disable the "Enable multi-threaded calculation" option.
https://i.imgur.com/dWZxdUP.png
moderator edit -- replaced oversized image with link.
Pasting pictures and code
Last edited by 2ManyDogs (2021-03-09 13:27:44)
Γίνε ρεαλιστής, μείνε ονειροπόλος ...
Offline