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

[email protected] changed:

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

--- Comment #3 from [email protected] ---
Hi, long time LO user but total newbie as far as bug reporting.
Overview: Because my PC is old this bug might have limited benefit for majority
of LO users. It might be lack of memory for auto save causing a conflict as it
affects text/word processing (Formatting)>[editting/cut/paste] and [fonts,
bold/itals, and highlights ] heavily used in calc.

PC: Lenovo Think Pad Yoga 11e (gen 4) 20DAS0TX00 
    SSD Samsung 118 TTL GB, 99.8 GB used, 18.7GB free
    Intel Celeron CPU N3150 @ 1.60Ghz
    RAM 4.00 GB
    Intel HD Graphics (114MB)
OS: Win 10 PRO 22H2 - Win 10 86_64 (build 19045) 
Latest Update" KB ID: 5126256           
<ESU Licensing Preparation Package (status: not enrolled)
 [non issue w/ this bug in my opinion-occurred before this update]

LO Version: 26.2.6.2 (X86_64)
Misc: Calc threaded (CPU threads: 4)

ISSUE verbal reconstruct attempt: 
NOTE: this bug does not involve an 'formula' usage [ = sum etc]
When editting text and associated modifiers LO crashes, might be be buggy/laggy
1st, but will stall/freeze then crash.
Possible issue: my template font is Arial. I manually replace all with
Liberation Serif [Note to self-please edit Master Template]
I tend to cut/paste cells heavily 'formatted', several c/p in succession tends
to increase more likeliness of crash. 
so my thinking is due to lack of/conflict of PC memory resources, LO cannot
execute its functions. This can happen though many times in succession though.

In conclusion, when I get a new laptop I hope this might solve my problem so I
totally understand LO volunteers' limited resources and the best use of their
time might not be on this limited bug. :-)

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

Reply via email to