Bug 155487 - Crash when zoomed too much at the flow chart
Summary: Crash when zoomed too much at the flow chart
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Draw (show other bugs)
Version:
(earliest affected)
7.4.6.2 release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-05-25 11:37 UTC by anedroid
Modified: 2023-12-29 03:12 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
Screenshot of the objects that cause crash (122.49 KB, image/png)
2023-05-30 12:55 UTC, anedroid
Details

Note You need to log in before you can comment on or make changes to this bug.
Description anedroid 2023-05-25 11:37:28 UTC
Description:
LibreOffice crash cause whole desktop environment to crash.

Steps to Reproduce:
1. Create new document
2. Add two elements of block scheme from gallery
3. Connect them with arrow
4. Zoom to the maximum
5. Scroll around the created scheme

Actual Results:
LibreOffice crashes together with the whole desktop environment.

Expected Results:
Nothing special should happen.


Reproducible: Always


User Profile Reset: No

Additional Info:
[Information automatically included from LibreOffice]
Locale: pl
Module: DrawingDocument
[Information guessed from browser]
OS: Linux (All)
OS is 64bit: yes

[Information copied from "about" window]
Version: 7.4.6.2 / LibreOffice Community
Build ID: 40(Build:2)
CPU threads: 4; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: pl-PL (pl_PL.UTF-8); UI: pl-PL
Trisquel package version: 1:7.4.6-0ubuntu0.20.04.1~lo1+10.0trisquel4
Calc: threaded

[Other information that might be relevant]
Desktop environment: Cinnamon v. 5.2.7-4
Xorg
Happens on both GPU and software rendering
Comment 1 Xisco Faulí 2023-05-25 11:46:21 UTC
Desktop enviroment crashes? It looks like a problem in the OS rather than in LibreOffice
Comment 2 Stéphane Guillou (stragu) 2023-05-25 12:01:54 UTC
I can reproduce with:

Version: 7.6.0.0.alpha1+ (X86_64) / LibreOffice Community
Build ID: f3aab159f1c1e00c25e6b4ca1e50813bc343f4f3
CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: en-AU (en_AU.UTF-8); UI: en-US
Calc: threaded

Can you please:
- update to LO 7.5 and test again, as 7.4 shouldn't see further updates
- If you can still reproduce, please test with Help > Restart in Safe Mode
- explain what exactly you mean by "block scheme"? Please use the English interface if possible, so we have the correct name.

Thank you!
Comment 3 anedroid 2023-05-30 12:26:50 UTC
(In reply to Xisco Faulí from comment #1)
> Desktop enviroment crashes? It looks like a problem in the OS rather than in
> LibreOffice

I think you are right, desktop environment should never crash by an error in some application. Even if this problem is not LibreOffice's fault, it still exists. I would like to know what cause this crash and report it to... I don't know – Xorg? Cinnamon? If I only knew better how this stuff work and affect each other!
Comment 4 anedroid 2023-05-30 12:50:05 UTC
(In reply to Stéphane Guillou (stragu) from comment #2)
> I can reproduce with:
> 
> Version: 7.6.0.0.alpha1+ (X86_64) / LibreOffice Community
> Build ID: f3aab159f1c1e00c25e6b4ca1e50813bc343f4f3
> CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3
> Locale: en-AU (en_AU.UTF-8); UI: en-US
> Calc: threaded
> 
> Can you please:
> - update to LO 7.5 and test again, as 7.4 shouldn't see further updates
> - If you can still reproduce, please test with Help > Restart in Safe Mode
> - explain what exactly you mean by "block scheme"? Please use the English
> interface if possible, so we have the correct name.
> 
> Thank you!

I reproduced this bug on version 7.5.0.3 AppImage in both normal and safe mode. I meant "flow chart" – that's how these objects are described in english interface.
To reproduce:
1. Create new empty drawing
2. On the bar on the right, open "gallery" tab
3. Section "Flow chart"
4. Drag two rectangles (processes)
5. Connect them with arrow
6. Zoom to the maximum
7. Scroll around inserted objects
8. At some point, everything crashes
Comment 5 anedroid 2023-05-30 12:55:42 UTC
Created attachment 187606 [details]
Screenshot of the objects that cause crash
Comment 6 Stéphane Guillou (stragu) 2023-05-30 17:57:26 UTC
(In reply to Stéphane Guillou (stragu) from comment #2)
> I can reproduce with:

And by "I can", I mean – of course – "I can't" :)

(In reply to anedroid from comment #4)
> 1. Create new empty drawing
> 2. On the bar on the right, open "gallery" tab
> 3. Section "Flow chart"
> 4. Drag two rectangles (processes)
> 5. Connect them with arrow
> 6. Zoom to the maximum
> 7. Scroll around inserted objects
> 8. At some point, everything crashes

Still can't reproduce with 7.5.3.2, both installed from deb amd with AppImage.

Can you please try with the latest 7.5 version, not 7.5.0.3 ? Various crashes were fixed since then.
Comment 7 anedroid 2023-05-31 09:08:48 UTC
(In reply to Stéphane Guillou (stragu) from comment #6)
> (In reply to Stéphane Guillou (stragu) from comment #2)
> > I can reproduce with:
> 
> And by "I can", I mean – of course – "I can't" :)
> 
> (In reply to anedroid from comment #4)
> > 1. Create new empty drawing
> > 2. On the bar on the right, open "gallery" tab
> > 3. Section "Flow chart"
> > 4. Drag two rectangles (processes)
> > 5. Connect them with arrow
> > 6. Zoom to the maximum
> > 7. Scroll around inserted objects
> > 8. At some point, everything crashes
> 
> Still can't reproduce with 7.5.3.2, both installed from deb amd with
> AppImage.
> 
> Can you please try with the latest 7.5 version, not 7.5.0.3 ? Various
> crashes were fixed since then.

7.5.3.2 is affected as well. I also done clean test on Linux Mint 21.0 Live CD in case something is wrong with my setup. It is 7.3.7.2 but I also downloaded and runned the latest LibreOffice AppImage. I have 2.8 GiBs of RAM, it looks like system is running out of memory. Dmesg says:

oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=/,mems_allowed=0,global_oom,task_memcg=/system.slice/system-systemd\x2dcoredump.slice/systemd-coredump@0-2579-0.service,task=systemd-coredum,pid=2580,uid=0
Out of memory: Killed process 2580 (systemd-coredum) total-vm:25896kB, file-rss:0kB, UID=0 pgtables:84kB oom_score_adj:500
Comment 8 anedroid 2023-05-31 09:38:30 UTC
Fun fact: as I just checked, this does not happen if run OpenRC. The exact same version of LibreOffice, neither LibreOffice nor DE crashes or freeze. I think systemd is to blame with all its unneccessary complexity.
Comment 9 Elias Probst 2023-05-31 10:15:43 UTC
I could reproduce it once on the first try, but failed to do so on any further attempts on NixOS using
- LibreOffice 7.5.2.2 50(Build:2)
- KDE Plasma 5.27.4 (Wayland)

This has unlikely something to do with OpenRC vs systemd - the fact that you're seeing systemd show up in your messages is based on the fact, that systemd-coredump tries to capture the coredump of your crashed application, so it can be later debugged.
Comment 10 QA Administrators 2023-11-28 03:13:06 UTC Comment hidden (obsolete)
Comment 11 QA Administrators 2023-12-29 03:12:06 UTC
Dear anedroid,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp