[Upstream] Writer consistently crashes when closing multi-hundred page documents with another LibreOffice file open -> soffice.bin crashed with SIGSEGV in SwFmt::~SwFmt()

Bug #753183 reported by Jason held
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
LibreOffice
Invalid
Critical
abiword (Ubuntu)
Invalid
Undecided
Unassigned
libreoffice (Ubuntu)
Fix Released
Medium
Björn Michaelsen

Bug Description

Binary package hint: libreoffice

1) lsb_release -rd
Description: Ubuntu Natty (development branch)
Release: 11.04

2) apt-cache policy libreoffice-writer
libreoffice-writer:
  Installed: 1:3.3.2-1ubuntu2
  Candidate: 1:3.3.2-1ubuntu2
  Version table:
 *** 1:3.3.2-1ubuntu2 0
        500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages
        100 /var/lib/dpkg/status

3) What is expected to happen is when one performs via the Terminal:

cd ~/Desktop && wget https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/753183/+attachment/2005949/+files/examplex1.odt && cp examplex1.odt examplex2.odt && lowriter -nologo examplex1.odt examplex2.odt

then closes examplex1.odt via File -> Close, LibreOffice Writer does not crash.

4) What happens instead is the program consistently greyscreens then crashes.

WORKAROUND: Use Abiword.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: libreoffice-core 1:3.3.2-1ubuntu2
ProcVersionSignature: Ubuntu 2.6.38-8.41-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic x86_64
NonfreeKernelModules: fglrx wl
Architecture: amd64
Date: Wed Apr 6 23:11:05 2011
Disassembly: => 0x2d: Cannot access memory at address 0x2d
ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110329.1)
ProcCmdline: /usr/lib/libreoffice/program/soffice.bin -writer -splash-pipe=5
ProcEnviron:
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x2d: Cannot access memory at address 0x2d
 PC (0x0000002d) not located in a known VMA region (needed executable region)!
SegvReason: executing NULL VMA
Signal: 11
SourcePackage: libreoffice
StacktraceTop:
 ?? ()
 SwFmt::~SwFmt() () from /usr/lib/libreoffice/program/../basis-link/program/libswlx.so
 ?? () from /usr/lib/libreoffice/program/../basis-link/program/libswlx.so
 ?? () from /usr/lib/libreoffice/program/../basis-link/program/libswlx.so
 SwDoc::~SwDoc() () from /usr/lib/libreoffice/program/../basis-link/program/libswlx.so
Title: soffice.bin crashed with SIGSEGV in SwFmt::~SwFmt()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Jason held (jasonsheld) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? ()
 ~SwFmt () from /usr/lib/libreoffice/program/../basis-link/program/libswlx.so
 ~SwCharFmt () from /usr/lib/libreoffice/program/../basis-link/program/libswlx.so
 DeleteAndDestroy () from /usr/lib/libreoffice/program/../basis-link/program/libswlx.so
 ~SwDoc () from /usr/lib/libreoffice/program/../basis-link/program/libswlx.so

Changed in libreoffice (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
penalvch (penalvch) wrote : Re: soffice.bin crashed with SIGSEGV in SwFmt::~SwFmt()

Jason held, thank you for reporting this bug and helping make Ubuntu better. Could you please attach the 2 files bzip compressed you were using when this issue occurred?

Changed in libreoffice (Ubuntu):
status: New → Incomplete
Revision history for this message
Jason held (jasonsheld) wrote : Re: [Bug 753183] Re: soffice.bin crashed with SIGSEGV in SwFmt::~SwFmt()

If I could replicate the error with different (meaningless) documents/files,
would that be okay? [?]

-Jason

On Thu, Apr 7, 2011 at 2:00 PM, Christopher M. Penalver
<email address hidden>wrote:

> Jason held, thank you for reporting this bug and helping make Ubuntu
> better. Could you please attach the 2 files bzip compressed you were
> using when this issue occurred?
>
> ** Changed in: libreoffice (Ubuntu)
> Status: New => Incomplete
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https://bugs.launchpad.net/bugs/753183
>
> Title:
> soffice.bin crashed with SIGSEGV in SwFmt::~SwFmt()
>
> Status in “libreoffice” package in Ubuntu:
> Incomplete
>
> Bug description:
> Binary package hint: libreoffice
>
> I had two documents open. They are over two hundred pages each. I
> closed one with File->Close. Then I did the same for the other, and
> the program blacked out and then quit. This happens QUITE often for
> larger documents. Any idea for fixes? Very annoying, and slightly
> scary.
>
> ProblemType: Crash
> DistroRelease: Ubuntu 11.04
> Package: libreoffice-core 1:3.3.2-1ubuntu2
> ProcVersionSignature: Ubuntu 2.6.38-8.41-generic 2.6.38.2
> Uname: Linux 2.6.38-8-generic x86_64
> NonfreeKernelModules: fglrx wl
> Architecture: amd64
> Date: Wed Apr 6 23:11:05 2011
> Disassembly: => 0x2d: Cannot access memory at address 0x2d
> ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
> InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110329.1)
> ProcCmdline: /usr/lib/libreoffice/program/soffice.bin -writer
> -splash-pipe=5
> ProcEnviron:
> LANGUAGE=en_US:en
> LANG=en_US.UTF-8
> SHELL=/bin/bash
> SegvAnalysis:
> Segfault happened at: 0x2d: Cannot access memory at address 0x2d
> PC (0x0000002d) not located in a known VMA region (needed executable
> region)!
> SegvReason: executing NULL VMA
> Signal: 11
> SourcePackage: libreoffice
> StacktraceTop:
> ?? ()
> SwFmt::~SwFmt() () from
> /usr/lib/libreoffice/program/../basis-link/program/libswlx.so
> ?? () from /usr/lib/libreoffice/program/../basis-link/program/libswlx.so
> ?? () from /usr/lib/libreoffice/program/../basis-link/program/libswlx.so
> SwDoc::~SwDoc() () from
> /usr/lib/libreoffice/program/../basis-link/program/libswlx.so
> Title: soffice.bin crashed with SIGSEGV in SwFmt::~SwFmt()
> UpgradeStatus: No upgrade log present (probably fresh install)
> UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
>
> To unsubscribe from this bug, go to:
>
> https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/753183/+subscribe
>

Revision history for this message
penalvch (penalvch) wrote : Re: soffice.bin crashed with SIGSEGV in SwFmt::~SwFmt()

Jason held, if you can reproduce this error with different files please attach them and describe how to reproduce this crash.

Revision history for this message
Jason held (jasonsheld) wrote : Re: [Bug 753183] Re: soffice.bin crashed with SIGSEGV in SwFmt::~SwFmt()

I haven't been able to reproduce the error with different files. Files with
lorem ipsum content.
So, I tested out the problem with one of the original files, and three times
it occurred (all three times). Basically, if I Close the file or Exit, it
becomes unresponsive, and then shuts off the program.

This is actually an early draft of a story I'm getting published VERY soon,
so if you could delete this as soon as you know what the problem might be,
that'd be much appreciated. I'd like to see LibreOffice become amazing. I
hope this helps. And, I hope it's not just my problem (well, I do hope
that).

-Jason

On Fri, Apr 8, 2011 at 10:57 PM, Christopher M. Penalver
<email address hidden>wrote:

> Jason held, if you can reproduce this error with different files please
> attach them and describe how to reproduce this crash.
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https://bugs.launchpad.net/bugs/753183
>
> Title:
> soffice.bin crashed with SIGSEGV in SwFmt::~SwFmt()
>
> Status in “libreoffice” package in Ubuntu:
> Incomplete
>
> Bug description:
> Binary package hint: libreoffice
>
> I had two documents open. They are over two hundred pages each. I
> closed one with File->Close. Then I did the same for the other, and
> the program blacked out and then quit. This happens QUITE often for
> larger documents. Any idea for fixes? Very annoying, and slightly
> scary.
>
> ProblemType: Crash
> DistroRelease: Ubuntu 11.04
> Package: libreoffice-core 1:3.3.2-1ubuntu2
> ProcVersionSignature: Ubuntu 2.6.38-8.41-generic 2.6.38.2
> Uname: Linux 2.6.38-8-generic x86_64
> NonfreeKernelModules: fglrx wl
> Architecture: amd64
> Date: Wed Apr 6 23:11:05 2011
> Disassembly: => 0x2d: Cannot access memory at address 0x2d
> ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
> InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110329.1)
> ProcCmdline: /usr/lib/libreoffice/program/soffice.bin -writer
> -splash-pipe=5
> ProcEnviron:
> LANGUAGE=en_US:en
> LANG=en_US.UTF-8
> SHELL=/bin/bash
> SegvAnalysis:
> Segfault happened at: 0x2d: Cannot access memory at address 0x2d
> PC (0x0000002d) not located in a known VMA region (needed executable
> region)!
> SegvReason: executing NULL VMA
> Signal: 11
> SourcePackage: libreoffice
> StacktraceTop:
> ?? ()
> SwFmt::~SwFmt() () from
> /usr/lib/libreoffice/program/../basis-link/program/libswlx.so
> ?? () from /usr/lib/libreoffice/program/../basis-link/program/libswlx.so
> ?? () from /usr/lib/libreoffice/program/../basis-link/program/libswlx.so
> SwDoc::~SwDoc() () from
> /usr/lib/libreoffice/program/../basis-link/program/libswlx.so
> Title: soffice.bin crashed with SIGSEGV in SwFmt::~SwFmt()
> UpgradeStatus: No upgrade log present (probably fresh install)
> UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
>
> To unsubscribe from this bug, go to:
>
> https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/753183/+subscribe
>

Revision history for this message
penalvch (penalvch) wrote : Re: soffice.bin crashed with SIGSEGV in SwFmt::~SwFmt()

Jason held, this is reproducible in Ubuntu 11.04 via downloading TWM1.odt, copying and renaming to TWM2.odt, opening both up simultaneously, then try to close TWM1.odt, LibreOffice Writer crashes. This crash does not occur if one uses Abiword. Marking Confirmed.

lsb_release -rd
Description: Ubuntu Natty (development branch)
Release: 11.04

apt-cache policy libreoffice-writer
libreoffice-writer:
  Installed: 1:3.3.2-1ubuntu2
  Candidate: 1:3.3.2-1ubuntu2
  Version table:
 *** 1:3.3.2-1ubuntu2 0
        500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages
        100 /var/lib/dpkg/status

apt-cache policy abiword
abiword:
  Installed: 2.8.6-0.3build1
  Candidate: 2.8.6-0.3build1
  Version table:
 *** 2.8.6-0.3build1 0
        500 http://us.archive.ubuntu.com/ubuntu/ natty/universe i386 Packages
        100 /var/lib/dpkg/status

Changed in libreoffice (Ubuntu):
status: Incomplete → Confirmed
description: updated
tags: added: lo33
Revision history for this message
penalvch (penalvch) wrote :

216 pages of lowercase x with a few returns scattered throughout.

penalvch (penalvch)
visibility: private → public
description: updated
Revision history for this message
penalvch (penalvch) wrote :

Jason held, since this bug has enough information provided for a developer to begin work, I'm going to mark it as Triaged and let them handle it from here. Thanks for taking the time to make Ubuntu better!

Changed in libreoffice (Ubuntu):
status: Confirmed → Triaged
Revision history for this message
In , penalvch (penalvch) wrote :

Created attachment 45441
examplex1.odt 216 pages of lowercase x with a few returns scattered throughout.

Downstream bug may be found at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/753183

1) lsb_release -rd
Description: Ubuntu Natty (development branch)
Release: 11.04

2) apt-cache policy libreoffice-writer
libreoffice-writer:
  Installed: 1:3.3.2-1ubuntu2
  Candidate: 1:3.3.2-1ubuntu2
  Version table:
 *** 1:3.3.2-1ubuntu2 0
        500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages
        100 /var/lib/dpkg/status

3) What is expected to happen is when one performs via the Terminal:

cd ~/Desktop && wget https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/753183/+attachment/2005949/+files/examplex1.odt && cp examplex1.odt examplex2.odt && lowriter -nologo examplex1.odt examplex2.odt

then closes examplex1.odt via File -> Close, LibreOffice Writer does not crash.

4) What happens instead is the program consistently greyscreens then crashes.

summary: - soffice.bin crashed with SIGSEGV in SwFmt::~SwFmt()
+ Writer consistently crashes when closing multi-hundred page documents
+ with another LibreOffice file open -> soffice.bin crashed with SIGSEGV
+ in SwFmt::~SwFmt()
Changed in df-libreoffice:
importance: Unknown → Critical
status: Unknown → Confirmed
Revision history for this message
In , Kendy-k (kendy-k) wrote :

Can you please provide us with a backtrace?

http://wiki.documentfoundation.org/BugReport#How_to_get_backtrace_.28on_Linux.29

Thank you!

Revision history for this message
In , penalvch (penalvch) wrote :

Jan Holesovsky, thank you for following up. Regarding the link on how to produce a backtrace, unfortunately it needs to be updated as the first step does not work:

cd /opt/libreoffice/program
bash: cd: /opt/libreoffice/program: No such file or directory

Despite this I performed via the Terminal:

cd ~/Desktop && wget https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/753183/+attachment/2005949/+files/examplex1.odt && cp examplex1.odt examplex2.odt && lowriter -nologo examplex1.odt examplex2.odt && sudo gdb 2>&1 | tee backtrace.txt

Attached gdb to the process id via the Terminal:

attach 15131
Attaching to process 15131
Reading symbols from /bin/dash...(no debugging symbols found)...done.
Reading symbols from /lib/i386-linux-gnu/libc.so.6...(no debugging symbols
found)...done.
Loaded symbols for /lib/i386-linux-gnu/libc.so.6
Reading symbols from /lib/ld-linux.so.2...(no debugging symbols found)...done.
Loaded symbols for /lib/ld-linux.so.2
0x00ce8416 in __kernel_vsyscall ()
(gdb) continue

Continued the process via the Terminal:

continue

Closed examplex1.odt by clicking File -> Exit, both files closed but gdb notes it did not crash as per Terminal output:

Program exited normally.

The same procedure outside of gdb did not produce a crash. I recently updated a ton of packages so seems fixed now...

lsb_release -rd
Description: Ubuntu Natty (development branch)
Release: 11.04

apt-cache policy libreoffice-writer
libreoffice-writer:
  Installed: 1:3.3.2-1ubuntu2
  Candidate: 1:3.3.2-1ubuntu2
  Version table:
 *** 1:3.3.2-1ubuntu2 0
        500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages 100
/var/lib/dpkg/status

Changed in df-libreoffice:
status: Confirmed → Invalid
Revision history for this message
In , Björn Michaelsen (bjoern-michaelsen) wrote :

@Christopher: I updated the instructions -- it is /usr/lib/libreoffice/program on Ubuntu/Debian.
Its important to run gdb on the soffice.bin executable, not any of the wrapper scripts.

Revision history for this message
Björn Michaelsen (bjoern-michaelsen) wrote :

Marking invalid in packaging. This needs to be fixed upstream. If the problem persists, the upstream bug needs to be reopened.

summary: - Writer consistently crashes when closing multi-hundred page documents
- with another LibreOffice file open -> soffice.bin crashed with SIGSEGV
- in SwFmt::~SwFmt()
+ [Upstream] Writer consistently crashes when closing multi-hundred page
+ documents with another LibreOffice file open -> soffice.bin crashed with
+ SIGSEGV in SwFmt::~SwFmt()
Changed in libreoffice (Ubuntu):
status: Triaged → Invalid
Revision history for this message
penalvch (penalvch) wrote :

Björn Michaelsen, I closed it upstream as I could no longer reproduce it in either Ubuntu 10.10 or 11.04. However, I am using a proxy file (same # of pages, different content) which caused the same crash in comparison to the one Jason held used to create this bug originally that I could reproduce the problem with.

Jason held, could you please try to reproduce the bug with your private file or follow the below procedure to see if it is still reproducible? If so, please mark the status of this bug to New. If not, please mark to Invalid.

cd ~/Desktop && wget https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/753183/+attachment/2005949/+files/examplex1.odt && cp examplex1.odt examplex2.odt && lowriter -nologo examplex1.odt examplex2.odt

in examplex1.odt click File -> Close

Changed in libreoffice (Ubuntu):
status: Invalid → Incomplete
penalvch (penalvch)
Changed in abiword (Ubuntu):
status: New → Invalid
Revision history for this message
Charlie Kravetz (cjkgeek) wrote :

Please stop adding Abiword to every LibreOffice/OpenOffice bug. It is generating a lot of un-necessary email. Every time you do this, you generate an email to every person subscribed to abiword bugs. To add a package just to mark it invalid is not needed.

Revision history for this message
In , Björn Michaelsen (bjoern-michaelsen) wrote :

Still cant reproduce with upstream master,

Changed in libreoffice (Ubuntu):
assignee: nobody → Björn Michaelsen (bjoern-michaelsen)
milestone: none → ubuntu-12.04
Revision history for this message
Björn Michaelsen (bjoern-michaelsen) wrote :

Cant reproduce in upstream master, if we have it in ubuntus LO 3.5 release (in precise), we broke it.

Revision history for this message
Björn Michaelsen (bjoern-michaelsen) wrote :

Cant reproduce it in 3.5.0-1ubuntu4 on precise either.

Changed in libreoffice (Ubuntu):
status: Incomplete → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.