https://bugs.documentfoundation.org/show_bug.cgi?id=159848

Tom Luoma <tomlu...@yahoo.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEEDINFO                    |UNCONFIRMED
     Ever confirmed|1                           |0

--- Comment #6 from Tom Luoma <tomlu...@yahoo.com> ---
huh -- odd and odder
When I started LO there was a thumbnail of the file in ods format. It opens and
appears complete. I guess when I opened it in safe mode the file got saved -- I
did not save it.  The ods loads fast-- maybe too fast -- I'm quite sure
everything is there. 

However I happened on two tabs with display artifacts -- a tab labeled SCH1
Line20 and the next tab over. They are random vertical lines.
So I launched AOO and opened the xlsx version (at the same time) - it has the
exact same lines.
I don't expect you see anything like that.  Any ideas about this?

At that point 33% of 16GB ram in use with both apps running and the file
loaded.

I then tried to load the xlsx again (LO only) and got the original crash.

The drive is partitioned and these two apps are not on the root.

Version: 24.2.0.3 (X86_64) / LibreOffice Community
Build ID: da48488a73ddd66ea24cf16bbc4f7b9c08e9bea1
CPU threads: 8; OS: Windows 6.1 Service Pack 1 Build 7601; UI render:
Skia/Raster; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: CL threaded

I built this system a while back but it is quick enough.  MSI MB, Samsung 960
M.2 500GB SSD, GTX 1060 6GB graphics, good box plenty cool.

While watching Resource Monitor I loaded it all again -- no strain. It is a
very complex spreadsheet. The guy did a hell of a job.

I had been using earlier versions of this spreadsheet since 2018 on Office 2010
Pro. I never had a problem. But suddenly MS doesn't like my license after I
moved stuff around on the disk and reloaded Office.  I did load a version of
this file late last year to estimate my taxes.

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to