Bug 115034 - Crash in: ScTransferObj::~ScTransferObj()
Summary: Crash in: ScTransferObj::~ScTransferObj()
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
5.3.7.2 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-01-16 08:14 UTC by Stephen Cannan
Modified: 2018-10-18 15:55 UTC (History)
4 users (show)

See Also:
Crash report or crash signature: ["ScTransferObj::~ScTransferObj()"]


Attachments
This is exactly the spreadsheet that was open at the time of the crash (47.34 KB, application/vnd.oasis.opendocument.spreadsheet)
2018-01-16 09:33 UTC, Stephen Cannan
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Stephen Cannan 2018-01-16 08:14:01 UTC
This bug was filed from the crash reporting server and is br-539e729c-1124-4b67-ac2e-cf6c8d9d985d.
=========================================

Was simply closing Calc having saved the spreadsheet.
Comment 1 tommy27 2018-01-16 09:23:59 UTC
did you try upgrading to 5.4.4? is that bug still reproducible with the latest LibO release?
Comment 2 Xisco Faulí 2018-01-16 09:24:59 UTC
Thank you for reporting the bug. Please attach a sample document, as this makes it easier for us to verify the bug. 
(Please note that the attachment will be public, remove any sensitive information before attaching it. 
See https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F for help on how to do so.)

I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested document is provided.
Comment 3 Xisco Faulí 2018-01-16 09:25:47 UTC
The crash signature is the same as in bug 104969, however, I still see crash reports with the latest versions -> http://crashreport.libreoffice.org/stats/signature/ScTransferObj::~ScTransferObj()
Comment 4 Stephen Cannan 2018-01-16 09:33:07 UTC
Created attachment 139120 [details]
This is exactly the spreadsheet that was open at the time of the crash
Comment 5 Xisco Faulí 2018-01-16 09:34:56 UTC
Hi Stephen,
Thanks for sharing the document. Do you remember if you copy&paste something before you hit the crash? have you reproduced the crash again ?
Comment 6 Stephen Cannan 2018-01-16 09:45:31 UTC
Yes, I copied what was cell L5 (contents =L$1) I think, but it may have been another of the date cells - they all have the same structure: col$1.
I then pasted it into I77 and executed the macro with Alt-S which resorts the rows bringing row 77 to be row 2.
I then saved the spreadsheet and closed the program with the top righthand "x".
Comment 7 Xisco Faulí 2018-01-16 10:44:41 UTC
Have you been able to reproduce it again?
Did you create/delete/move/copy any sheet before the crash ?
Comment 8 Stephen Cannan 2018-01-16 12:01:26 UTC
(In reply to Xisco Faulí from comment #7)
> Have you been able to reproduce it again?
> Did you create/delete/move/copy any sheet before the crash ?

No, I know no way of reproducing it.
I can process the same spreadsheet now without problem.
I did not create/delete/move/copy any sheet before the crash. The only actions were those that I described.
Comment 9 Telesto 2018-01-16 14:43:16 UTC
I'm not able to reproduce
Version: 6.1.0.0.alpha0+
Build ID: 80fb8d406ced47e6a2089f0c8ba5c103d2fec91f
CPU threads: 4; OS: Windows 6.3; UI render: default; 
TinderBox: Win-x86@42, Branch:master, Time: 2018-01-15_05:18:42
Locale: nl-NL (nl_NL); Calc: CL

Except for bug 115045
Comment 10 Xisco Faulí 2018-10-18 15:06:55 UTC
Dear Stephen Cannan,
Have you ever reproduced the crash since you reported this issue?
Otherwise, I would suggest to close this one as RESOLVED INSUFFICIENTDATA