Bug 119503 - Use of mouse scroll wheel then graphics work with Writer and Calc open then more scroll action causes Crash
Summary: Use of mouse scroll wheel then graphics work with Writer and Calc open then m...
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
6.1.0.3 release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-08-26 07:11 UTC by matthewnote
Modified: 2019-03-21 10:02 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description matthewnote 2018-08-26 07:11:01 UTC
Description:
Similar to Bug 106037 with LO 6.0.6.   With Lubuntu 18.04 and LO 6.10 the LO starts up fine.  When selecting the first field, data entry in one cell of a spreadsheet in Calc, the keyboard taps are shown some nine to ten seconds later.  After that wait the number or letters appear; all the further data entries or manipulations catch up and happen at usual speed.  After much graphics work or  copying and pasting to Writer, suddenly LO crashes.  With LO 6.0.6 a PC freeze needed restart;  with LO 6.10 the Lubuntu remains operational. 

Steps to Reproduce:
1.  A spreadsheet with many calculations and about 200 graphics, ten sheets.
2.  Move the view up or down using mouse thumbwheel (or slider)
3.  Data entry, modifications and more thumbwheel eventually may cause crash.
4.  The files were created with 6.0.6, about 15 MB and graphically complex.
5.  There's an impression at the crash (experience) that it was due to some mouse or keyboard action about ten seconds before, the same delay described as happening only at the first cell after opening the file for the first time.  Difficult to be sure, yet crash occurs at odd moments, the reproduceable cause which may be identical every time - occurred ten seconds earlier while working (it seems).  Much more difficult to say what it was.

Actual Results:
crashreport.libreoffice.org/stats/crash_details/3fcb915a-557e-42b4-808e-9fb5737c1d82

If LO 6.10 is used,without crash then left running for hours without further inputs, no crash occurs (no cumulative problem).  It seems to be provoked by panning the page.

Expected Results:
Document Recovery occurs successfully (always so far, yet versions are backed up manually frequently too).


Reproducible: Sometimes


User Profile Reset: No


OpenGL enabled: Yes

Additional Info:
Version: 6.1.0.3
Build ID: efb621ed25068d70781dc026f7e9c5187a4decd1
CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk2; 
Locale: fr-FR (fr_FR.UTF-8); Calc: group threaded
Comment 1 Xisco Faulí 2018-08-28 10:49:51 UTC
Thank you for reporting the bug. To be certain the reported issue is not
related to corruption in the user profile, could you please reset your
Libreoffice profile ( https://wiki.documentfoundation.org/UserProfile ) and
re-test?

I have set the bug's status to 'NEEDINFO'. Please change it back to
'UNCONFIRMED' if the issue is still present
Comment 2 Xisco Faulí 2018-08-28 10:50:11 UTC
OTOT, does it work if you disable OpenGl ? -> https://wiki.documentfoundation.org/OpenGL
Comment 3 matthewnote 2018-08-30 09:34:27 UTC
Hello.  I found and used the bug reporting guide/instructions for LibreOffice.
The reset of the user profile was done already.  Problem unchanged.

I check GL and find since leaving the safe mode (back to normal working) the Open GL is disabled.  I don't know if that was off since installing LO 6.10 or changed to disabled by using safe mode for two days?  I didn't do it myself.   I'll be back to the project tomorrow with Open GL still off and see/report what happens.  Thankyou for the guidance.
Comment 4 Xisco Faulí 2018-08-31 19:40:10 UTC
(In reply to matthewnote from comment #3)
> Hello.  I found and used the bug reporting guide/instructions for
> LibreOffice.
> The reset of the user profile was done already.  Problem unchanged.
> 
> I check GL and find since leaving the safe mode (back to normal working) the
> Open GL is disabled.  I don't know if that was off since installing LO 6.10
> or changed to disabled by using safe mode for two days?  I didn't do it
> myself.   I'll be back to the project tomorrow with Open GL still off and
> see/report what happens.  Thankyou for the guidance.

Thanks.
Any Update?
Comment 5 matthewnote 2018-09-01 17:19:39 UTC
With Open GL disabled, the software works.  No crashes today during the usually intense graphics work (many lines, shapes, curves, transparencies).  It opens a 15MB ods file while doing work to paste graphics into a LO Writer document.  soffice.bin at RSS 2.3 GB and virtual memory at 5.1 GB.  

It is very much slower. Panning the spreadsheet left to right or up/down functions yet it is very difficult to work with. Is that to be expected without Open GL?

The more work done, the slower it seems to get.  This desktop is Lubuntu with an ultra 4K monitor on display port using Intel i7 HD graphics which is already on the limit.  I'll double the RAM memory from 4 to 8 GB on this desktop next week.

I've ordered a brand new Shuttle desktop Intel i7 Kaby Lake dual core each at 2.7 GHz with 16 GB of RAM (delivery in two weeks).  The new desktop will be with Intel HD 620 graphics.  It's intended to install Ubuntu gnome 18.04.  Question.  The Intel HD620 is without memory - it will use the RAM. What is best Libre Office experience or advice about Open GL and virtual memory swappiness to cause best spreadsheet operation with the new computer?

I'll keep working here and post another message.  I can modify the spreadsheet to cut it's size in half, but that will take me a week.  It's heavy on calculations in almost all cells.
Comment 6 matthewnote 2018-09-02 10:19:49 UTC
One freeze of Libre Office 6.10 with Open GL disabled (during one day).   This occasion Lubuntu froze also.

The event occurred while panning a large sheet left and right with about fifty graphics with multiple lines and shapes of varying transparencies and colours on a 4K monitor.  The work was simply to delete as many graphics as possible.  .ods file size reduced (after reboot) from 15MB to 9MB.

Using safe mode, the factory reset (the furthest down the menu of options) has been done since the freeze to see what happens next.
Comment 7 matthewnote 2018-09-05 14:28:31 UTC
Two half days running - only one ultra 4K monitor, one document text and one spreadsheet open, 1GB of 4GB RAM used by soffice.bin.

One crash - UUID d9e250db-f50b-4a01-893f-ef73bcf18bac 

Both documents are heavy with graphics, lines, areas of varying transparency. 
After saving the text document, reselecting the Calc window, Calc was blank, white.  This can happen while waiting for Autosave, so I waited.  However, neither application came back.  Task Manager showed 1% processor load, about 1.5GB of RAM involved.  By terminating the LO soffice.bin it was possible to resume use of the LUbuntu.   However, I chose restart.   Open GL was disabled and is still disabled.  After restart the crash report was offered.

With Open GL enabled, similar events were about once per hour.
With Open GL disabled, it seems about once per day.

That's quite alright and, as always, Libre Office is marvellous!
Comment 8 matthewnote 2018-09-05 14:52:26 UTC
After restarting the desktop, working again on the text document, five minutes later the cursor remained as if ready to click to add text, but no reaction from soffice.bin.  After three minutes waiting, stopping soffice using task manager and then restarting (Open GL still disabled, normal mode), this crash report was offered:

UUID  f6941804-9c30-49da-9492-102277ee2f66

This time I'm going to recover the documents, then shutdown and electrically off the desktop PC.
Comment 9 Xisco Faulí 2019-03-13 18:51:29 UTC
A new major release of LibreOffice is available since this bug was reported.
Could you please try to reproduce it with the latest version of LibreOffice
from https://www.libreoffice.org/download/libreoffice-fresh/ ?
I have set the bug's status to 'NEEDINFO'. Please change it back to
'UNCONFIRMED' if the bug is still present in the latest version.
Comment 10 matthewnote 2019-03-17 13:57:12 UTC
In november I chose to order a new PC, more RAM and leave Light Ubuntu in favour of Bionic Beaver, now at

Libreoffice Calc Version: 6.0.7.3
Build ID: 1:6.0.7-0ubuntu0.18.04.2
CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; 
Locale: en-US (en_US.UTF-8); Calc: group

Wonderful.   Three months without any stoppages.  Bionic Beaver first install was available with a very much earlier LibreOffice than the 6.0.6/6.10.  There were editting limitations yet everything works and runs without stopping, any amount of work, any challenge in logic or maths and with any number of ods files expanding up to 15 GB (as far as I've tested) - still working and rapidly updated to 6.0.7.  Wonderful is the right word.

My view as user was that it seemed to prove the Bionic Beaver choice for Gnome was the correction necessary rather than LibreOffice bugs.  Yet I didn't know to comment here if Light Ubuntu still receives support nor am I qualified to claim it as a fact. It looks that way in review.  

Two machines here (Bionic Beaver) with three UltraHD monitors using Display Port and HDMI to do the research dual monitor is quite amazing.  Without the prior configuration nor Light Ubuntu I can't comment further here, yet I hope the comparison of the conversion helps.
Comment 11 Xisco Faulí 2019-03-21 10:02:56 UTC
probably it was a problem with your old distribution or your old computer. it's hard to tell.
Anyway, I'm happy LibreOffice works great for you now.
Closing as RESOLVED WORKSFORME