soffice.bin crashed with SIGSEGV in framework::LockHelper::acquireReadAccess()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
LibreOffice |
Invalid
|
High
|
|||
libreoffice (Ubuntu) |
Invalid
|
Medium
|
Unassigned |
Bug Description
Open then close sample document from:
https:/
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: libreoffice-core 1:3.4.3-1ubuntu3
ProcVersionSign
Uname: Linux 3.0.0-11-generic x86_64
NonfreeKernelMo
ApportVersion: 1.23-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Fri Sep 23 20:30:34 2011
ExecutablePath: /usr/lib/
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
ProcCmdline: /usr/lib/
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7ff3f84eb4dc <_ZN9framework1
PC (0x7ff3f84eb4dc) ok
source "(%rdi)" (0x00000000) not located in a known VMA region (needed readable region)!
destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: libreoffice
StacktraceTop:
framework:
?? () from /usr/lib/
VclEventListen
Window:
Window::~Window() () from /usr/lib/
Title: soffice.bin crashed with SIGSEGV in framework:
UpgradeStatus: Upgraded to oneiric on 2011-06-28 (87 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
Changed in df-libreoffice: | |
importance: | Unknown → High |
status: | Unknown → Confirmed |
Changed in libreoffice (Ubuntu): | |
status: | New → Triaged |
Changed in df-libreoffice: | |
status: | Confirmed → Invalid |
Created attachment 48543
Error message recieved upon crash
Some documents crash upon saving or closing in LibO Writer 3.4 in Ubuntu 11.4.
This happens in Ubuntu 11.04. It doen‘t happen in Windows 7 and not in Debian stable. The documents must be of some complexity. Newly created docs work as expected, but some, but not all, papers I have been working on for a while crashes.
I guess that there is something in some of my docs that doesn‘t work properly in LibO 3.4. I have not been able to pinpoint what it is. I have made a test document (2 pages) with the error present out of a much bigger document. If I shorten the document further or insert dummy text instead of real text the document does not crash.
I am reluctant to post even a small part of my document publicly. If I change to dummy text the error is gone so its the real thing. Perhaps I could mail the file to someone for further analysis?
How to recreate:
Open the document in LibO 3.4 on Ubuntu 11.04
Close the document
Writer crashes
When Writer is restarted you are prompted to recreate the document
The document works fine in LibO 3.3 (and earlier versions of OOo).
I get error reports in my home folder every time LibO crashes. I post one of them. It says something about Java. I have tested LibO 3.4 with SUN Java and Open JDK. The document crashes with either.
I have also tested with LibO 3.4.1 RC3 and the documents still crash.
This is a serious bug since data is lost upon crash, especially if you are working on several documents, since all open documents crash without saving.