Bug 1094275 - [abrt] libreoffice-core: ScFormulaCell::IsSharedTop(): soffice.bin killed by SIGSEGV
Summary: [abrt] libreoffice-core: ScFormulaCell::IsSharedTop(): soffice.bin killed by ...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: libreoffice
Version: 20
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: -RETIRED-
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:d3d0ecd3bbf3c1b6a7d92786d73...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-05-05 11:49 UTC by Jillian Morgan
Modified: 2014-06-09 13:37 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-06-05 10:42:26 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (59.41 KB, text/plain)
2014-05-05 11:49 UTC, Jillian Morgan
no flags Details
File: cgroup (159 bytes, text/plain)
2014-05-05 11:49 UTC, Jillian Morgan
no flags Details
File: core_backtrace (26.15 KB, text/plain)
2014-05-05 11:49 UTC, Jillian Morgan
no flags Details
File: dso_list (24.55 KB, text/plain)
2014-05-05 11:49 UTC, Jillian Morgan
no flags Details
File: environ (4.38 KB, text/plain)
2014-05-05 11:49 UTC, Jillian Morgan
no flags Details
File: exploitable (82 bytes, text/plain)
2014-05-05 11:49 UTC, Jillian Morgan
no flags Details
File: limits (1.29 KB, text/plain)
2014-05-05 11:49 UTC, Jillian Morgan
no flags Details
File: maps (118.03 KB, text/plain)
2014-05-05 11:49 UTC, Jillian Morgan
no flags Details
File: open_fds (430 bytes, text/plain)
2014-05-05 11:49 UTC, Jillian Morgan
no flags Details
File: proc_pid_status (826 bytes, text/plain)
2014-05-05 11:49 UTC, Jillian Morgan
no flags Details
File: var_log_messages (395 bytes, text/plain)
2014-05-05 11:49 UTC, Jillian Morgan
no flags Details

Description Jillian Morgan 2014-05-05 11:49:34 UTC
Description of problem:
Unknown. I was just cursoring between cells when it suddenly dissapeared.

Version-Release number of selected component:
libreoffice-core-4.2.3.3-4.fc20

Additional info:
reporter:       libreport-2.2.1
backtrace_rating: 4
cmdline:        /usr/lib64/libreoffice/program/soffice.bin --calc Fuel_Forte.xls --splash-pipe=5
crash_function: ScFormulaCell::IsSharedTop
executable:     /usr/lib64/libreoffice/program/soffice.bin
kernel:         3.14.1
runlevel:       N 5
type:           CCpp
uid:            500

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 ScFormulaCell::IsSharedTop at /usr/src/debug/libreoffice-4.2.3.3/sc/source/core/data/formulacell.cxx:4021
 #1 operator() at /usr/src/debug/libreoffice-4.2.3.3/sc/source/core/data/column.cxx:2376
 #2 for_each<mdds::__mtv::iterator_base<mdds::multi_type_vector<mdds::mtv::custom_block_func3<mdds::mtv::default_element_block<52, svl::SharedString>, mdds::mtv::noncopyable_managed_element_block<53, EditTextObject>, mdds::mtv::noncopyable_managed_element_block<54, ScFormulaCell> > >::iterator_trait, mdds::__mtv::private_data_forward_update<mdds::__mtv::iterator_value_node<unsigned long, mdds::mtv::base_element_block> > >, (anonymous namespace)::UpdateRefGroupBoundChecker> at /usr/include/c++/4.8.2/bits/stl_algo.h:4417
 #3 ScColumn::UpdateReference at /usr/src/debug/libreoffice-4.2.3.3/sc/source/core/data/column.cxx:2718
 #4 ScTable::UpdateReference at /usr/src/debug/libreoffice-4.2.3.3/sc/source/core/data/table1.cxx:1502
 #5 ScDocument::UpdateReference at /usr/src/debug/libreoffice-4.2.3.3/sc/source/core/data/documen3.cxx:1031
 #6 ScDocument::DeleteRow at /usr/src/debug/libreoffice-4.2.3.3/sc/source/core/data/document.cxx:1345
 #7 ScDocFunc::DeleteCells at /usr/src/debug/libreoffice-4.2.3.3/sc/source/ui/docshell/docfunc.cxx:2331
 #8 ScViewFunc::DeleteCells at /usr/src/debug/libreoffice-4.2.3.3/sc/source/ui/view/viewfunc.cxx:1537
 #9 ScCellShell::ExecuteEdit at /usr/src/debug/libreoffice-4.2.3.3/sc/source/ui/view/cellsh1.cxx:159

Comment 1 Jillian Morgan 2014-05-05 11:49:38 UTC
Created attachment 892497 [details]
File: backtrace

Comment 2 Jillian Morgan 2014-05-05 11:49:40 UTC
Created attachment 892498 [details]
File: cgroup

Comment 3 Jillian Morgan 2014-05-05 11:49:42 UTC
Created attachment 892499 [details]
File: core_backtrace

Comment 4 Jillian Morgan 2014-05-05 11:49:44 UTC
Created attachment 892500 [details]
File: dso_list

Comment 5 Jillian Morgan 2014-05-05 11:49:45 UTC
Created attachment 892501 [details]
File: environ

Comment 6 Jillian Morgan 2014-05-05 11:49:47 UTC
Created attachment 892502 [details]
File: exploitable

Comment 7 Jillian Morgan 2014-05-05 11:49:48 UTC
Created attachment 892503 [details]
File: limits

Comment 8 Jillian Morgan 2014-05-05 11:49:50 UTC
Created attachment 892504 [details]
File: maps

Comment 9 Jillian Morgan 2014-05-05 11:49:52 UTC
Created attachment 892505 [details]
File: open_fds

Comment 10 Jillian Morgan 2014-05-05 11:49:53 UTC
Created attachment 892506 [details]
File: proc_pid_status

Comment 11 Jillian Morgan 2014-05-05 11:49:55 UTC
Created attachment 892507 [details]
File: var_log_messages

Comment 12 David Tardon 2014-05-06 08:00:40 UTC
possibly a duplicate of bug 1092199

Comment 13 -RETIRED- 2014-05-08 14:24:05 UTC
Not exactly a duplicate of bug 1092199 but might be related (and fixed in the mean time).

@Ian:
"just cursoring between cells" and the backtrace under DeleteCells/DeleteRow somehow don't match ... apparently the crash happened when cells were deleted. Is the crash reproducible with the same action?

Comment 14 Jillian Morgan 2014-06-09 13:37:09 UTC
Despite the DeleteRow/DeleteCells calls in the trace, I could swear that I had not deleted anything at the time of the crash. At the best of my recollection now, I believe I was altering the contents of a cell (that contained a formula, I think), and then cursored right to go to the next cell, at which point oocalc crashed.

I did try to reproduce it after it happened and could not. Haven't had any other oocalc crashes since.

As the cause isn't evident from the traceback and I can't provide any more details about the surrounding events beyond the above, I suppose you can go ahead and close the bug. Can always re-open if it occurs again.

Cheers.


Note You need to log in before you can comment on or make changes to this bug.