https://bugs.documentfoundation.org/show_bug.cgi?id=106122
Bug ID: 106122
Summary: Writer sometimes crashes with std::bad alloc dialog
Product: LibreOffice
Version: 5.2.5.1 release
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: UNCONFIRMED
Severity: critical
Priority: medium
Component: Writer
Assignee: [email protected]
Reporter: [email protected]
Created attachment 131378
--> https://bugs.documentfoundation.org/attachment.cgi?id=131378&action=edit
Screenshot of what LO looked like as it crashed
Since upgrading from LO 5.1.x to 5.2.5.1, I have had two hard crashes with a
dialog pop-up that says std::bad_alloc.
See attached screen shot.
I had just typed Ctrl-Z, IIRC, while editing a comment. I'm pretty sure that's
correct, looking at all the typos. Strangely, I have a crystal clear memory of
fixing all those, just before it crashed, despite the evidence of the
screenshot. In fact, I'm certain I fixed "cybered", "mage", "sort",
"stimulant", "running", "and", "test", and was fixing something further down
in the comment when I used Undo. I'd even added the text ";she's not a
shape-shifter" and I think I had also reduced the comment's font size from 12
to 11. I'm 100% certain I made all those edits. Yet the screen snapshot doesn't
agree! Could the screen buffer grabbed by the gnome screen shot be "out of
date"?! (Taken from some un-refreshed back-buffer?)
I have attached a (non-debug, sorry) gdb backtrace FWIW.
(gdb) attach 32009
Attaching to process 32009
[New LWP 32010]
[New LWP 32016]
[New LWP 32017]
[New LWP 32018]
[New LWP 32030]
[New LWP 32071]
[New LWP 32643]
[New LWP 425]
[New LWP 2936]
[New LWP 2937]
[New LWP 2938]
[New LWP 2939]
where
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
warning: File "/opt/libreoffice5.2/program/libpython3.5m.so-gdb.py"
auto-loading has been declined by your `auto-load safe-path' set to
"$debugdir:$datadir/auto-load".
To enable execution of this file add
add-auto-load-safe-path
/opt/libreoffice5.2/program/libpython3.5m.so-gdb.py
line to your configuration file "/root/.gdbinit".
To completely disable this security protection add
set auto-load safe-path /
line to your configuration file "/root/.gdbinit".
For more information about this security protection see the
"Auto-loading safe path" section in the GDB manual. E.g., run from the shell:
info "(gdb)Auto-loading safe path"
0x00007fb5af226b5d in poll () at ../sysdeps/unix/syscall-template.S:84
84 ../sysdeps/unix/syscall-template.S: No such file or directory.
(gdb) where
#0 0x00007fb5af226b5d in poll () at ../sysdeps/unix/syscall-template.S:84
#1 0x00007fb5ad35738c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x00007fb5ad357712 in g_main_loop_run ()
from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x00007fb59e0fdb83 in gtk_dialog_run ()
from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#4 0x00007fb59e6cf88c in GtkSalSystem::ShowNativeDialog(rtl::OUString const&,
rtl::OUString const&, std::list<rtl::OUString, std::allocator<rtl::OUString> >
const&, int) () from /opt/libreoffice5.2/program/libvclplug_gtklo.so
#5 0x00007fb5b22e9084 in SalGenericSystem::ShowNativeMessageBox(rtl::OUString
const&, rtl::OUString const&) () from
/opt/libreoffice5.2/program/libmergedlo.so
#6 0x00007fb5b12f6fa4 in desktop::(anonymous
namespace)::FatalError(rtl::OUString const&) () from
/opt/libreoffice5.2/program/libmergedlo.so
#7 0x00007fb5b1304d68 in desktop::Desktop::Main() ()
from /opt/libreoffice5.2/program/libmergedlo.so
#8 0x00007fb5b2217c86 in ImplSVMain() ()
from /opt/libreoffice5.2/program/libmergedlo.so
#9 0x00007fb5b2217d72 in SVMain() ()
from /opt/libreoffice5.2/program/libmergedlo.so
#10 0x00007fb5b132748d in soffice_main ()
from /opt/libreoffice5.2/program/libmergedlo.so
#11 0x000000000040075b in main ()
(gdb) detach
Detaching from program: /opt/libreoffice5.2/program/soffice.bin, process 32009
(gdb) q
It also crashed exactly the same way two days before, but this time while I was
simply typing in new text. Note that LO is struggling with this file because
the number of comments have grown. So sometimes I have to wait for what I type
to appear. I don't know if that's relevant or not. It's the reason for all
the typos: I was typing fast on this occasion, adding the comment, and typing
blind, since I had to wait about 30 seconds for the text to appear. So then I
started fixing it, and then... boom!
This seems different, to me, from what is described in 95957. I have reopened
the files and
--
You are receiving this mail because:
You are the assignee for the bug._______________________________________________
Libreoffice-bugs mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
