Bug 160477 - DIRE UPDATE
Summary: DIRE UPDATE
Status: UNCONFIRMED
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
7.6.6.3 release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: QA:needsComment
Keywords:
Depends on:
Blocks:
 
Reported: 2024-04-02 11:22 UTC by alignedtraining
Modified: 2024-04-17 03:16 UTC (History)
0 users

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 alignedtraining 2024-04-02 11:22:44 UTC
Description:
opens up a blank document ok but the moment I try to open up one of my documents it seizes the processors .. beyond 5 mins and has a continual memory leak ..  up from 140Meg to over 1.8 Gig !!! Have to kill the process to regain control of the pc ...   seems to be this new accessibility stuff as everything started to go wrong a few updates ago when this appeared.  It should be turned it off normally and call it on demand...

Version: 7.6.6.3 (X86_64) / LibreOffice Community
Build ID: 60(Build:3)
CPU threads: 4; OS: Linux 5.5; UI render: default; VCL: gtk3
Locale: en-GB (en_GB.UTF-8); UI: en-US
Ubuntu package version: 4:7.6.6-0ubuntu0.20.04.1~lo1
Calc: threaded

Steps to Reproduce:
1. open document 
2. blank document opens normally 
3. select open chosen document from recent files list ..  (several of varying sizes than never had problems before)
4. hangs / seizes processor every time 
5. problem persists even after resetting user profile 

Actual Results:
Machine seized and have to kill off soffice.bin process 

Expected Results:
word document opens normally 


Reproducible: Always


User Profile Reset: Yes

Additional Info:
[Information automatically included from LibreOffice]
Locale: en-US
Module: TextDocument
[Information guessed from browser]
OS: Linux (All)
OS is 64bit: yes
Comment 1 alignedtraining 2024-04-02 11:23:53 UTC
Its critical ..  word is totally useless until this is fixed