Bug 119225 - Impress: Crash by moving chart in chart area and then closing Impress (regression 6.1 vs. 6.0)
Summary: Impress: Crash by moving chart in chart area and then closing Impress (regres...
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Impress (show other bugs)
Version:
(earliest affected)
6.1.0.3 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: wantBacktrace
Depends on:
Blocks:
 
Reported: 2018-08-12 07:01 UTC by Mike
Modified: 2018-08-12 10:31 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:

Attachments
Screencast (1.74 MB, video/avi)
2018-08-12 10:08 UTC, Mike 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Mike 2018-08-12 07:01:55 UTC 
Description:
Impress 6.1 displays a crash notice, if you move a chart in a chart area and then close Impress.
This is a regression of 6.1 to 6.0.5.

Steps to Reproduce:
1. Create new presentation
2. Insert chart.
3. Move chart in chart area.
4. Close Impress (doesn't matter, if you save)
→ LO displays a crash notice, offers a (empty) document recovery and restarts.

If you *undo* step 3 and then close Impress, you get a crash notice, too.

You can save in step 4, but the format is 'Open Document Chart'. After the restart of LO, saved ODC has a thumbnail in the Start Center.
If you open that ODC, 'LibreOffice Chart' starts. But it doesn't show a chart at all.

Actual Results:
Crash notice and restart

Expected Results:
No crash notice


Reproducible: Always


User Profile Reset: No



Additional Info:
Safe mode affected
Linux & Win affected

Crashes:

Version: 6.1.0.3 (x64)
Build ID: efb621ed25068d70781dc026f7e9c5187a4decd1
CPU threads: 4; OS: Windows 10.0; UI render: GL; 
Locale: de-DE (de_DE); Calc: group threaded

Version: 6.1.0.3
Build ID: efb621ed25068d70781dc026f7e9c5187a4decd1
CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk2; 
Locale: en-US (en_US.UTF-8); Calc: group threaded

Version: 6.2.0.0.alpha0+
Build ID: 8e9d43546c8e46ea635472ddf07f5c183dc13360
CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk2; 
TinderBox: Linux-rpm_deb-x86_64@70-TDF, Branch:master, Time: 2018-07-12_01:06:03
Locale: en-US (en_US.UTF-8); Calc: group threaded

Does not crash:

Version: 6.0.5.2
Build-ID: 54c8cbb85f300ac59db32fe8a675ff7683cd5a16
CPU-Threads: 4; BS: Windows 10.0; UI-Render: GL; 
Gebietsschema: de-DE (de_DE); Calc: CL



Reports:

crashreport.libreoffice.org/stats/crash_details/bf584260-65d0-449c-a0ac-6f1fa91dd2fb

crashreport.libreoffice.org/stats/crash_details/eef387cc-d520-4245-8dae-135ab70b207f

crashreport.libreoffice.org/stats/crash_details/1e6dce56-3dc9-430d-b859-39721ec36904
Comment 1 raal 2018-08-12 08:30:32 UTC 
Don't reproduce with Version: 6.2.0.0.alpha0+
Build ID: ea59fc4831b9d2430de51faa8c3e0a24e6d90cd1
CPU threads: 4; OS: Linux 4.4; UI render: default; VCL: gtk3;
Comment 2 Julien Nabet 2018-08-12 09:49:03 UTC 
On pc Debian x86-64 with master sources updated yesterday and gtk or gtk3 rendering, I don't reproduce this.

The 3 links of crashreports give "Not found" page.
Any chance to have a backtrace?
Comment 3 Mike 2018-08-12 10:08:40 UTC 
Created attachment 144123 [details]
Screencast

This is a screencast from the crash.
It referes to

crashreport.libreoffice.org/stats/crash_details/3f8ab52d-493b-4308-a69c-b79e9940ced4
Comment 4 Mike 2018-08-12 10:26:37 UTC 
Sorry for this false alarm :-( I tested it with a more recent release of 6.2alpha and I could not replicate the issue.