Bug 159885 - the latest text editing version hangs unexpectedly in the middle of writing
Summary: the latest text editing version hangs unexpectedly in the middle of writing
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.6.5.2 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-02-25 17:52 UTC by PAUL HOFSETH
Modified: 2024-03-11 01:39 UTC (History)
2 users (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 PAUL HOFSETH 2024-02-25 17:52:50 UTC
Description:
the windows10 64bit versions event description simply states "unknown error" and that the program stopped communicating with windows. The previous stable vesion never crashed on this machine (HP i-5 something). Crashes happen with short as well as long texts without any unusual keyboard input

Steps to Reproduce:
1.starting to edit an existing text
2.working while constanty saving so as to mimimize ill effects
3.continuing to write

Actual Results:
program hangs and offers alternatives of closing og waiting. Waiting takes forever, so I close. on opening the saved bits are present and the file is unharmed but continuing to write repeats the crash

Expected Results:
normal behaviour expected, but hang repeats (especially if I try to use the "save as" command which is a certain way to crash the program


Reproducible: Always


User Profile Reset: No

Additional Info:
the program should behave reliably like previous stable versions
Comment 1 m_a_riosv 2024-02-25 21:03:33 UTC
Please test in safe mode, Menu/Help/Restart in Safe Mode
Comment 2 PAUL HOFSETH 2024-02-26 10:57:57 UTC
(In reply to m_a_riosv from comment #1)
> Please test in safe mode, Menu/Help/Restart in Safe Mode

safe mode worked continuously this morning. But it should not be necessary.
Comment 3 m_a_riosv 2024-02-27 00:19:03 UTC
It is not a matter of necessary. If it is working in safe mode, something on the profile is broken.

When restarting in safe mode, there are options to clean the profile, total or partially. See in the Reset to factory options.
Comment 4 PAUL HOFSETH 2024-02-27 07:54:03 UTC
thanks for good advice, The only thing I ahve ever used the profile for is to put in my name, all versions since star office has wiroked perfectly with one or 200 pages. I keep using the "7 something" version which by now has been stable, but hesistate to work on longer manuscripts until stability is proven by experience.

p.
Comment 5 ady 2024-03-09 00:54:29 UTC
I am tempted to change this report back from WFM to unconfirmed. The fact that Miguel cannot reproduce the problem does not mean that the problem is not there or that it cannot be replicated by anyone else, or that the problem is uniquely related to one corrupted profile.

@Paul,

Anyone trying to replicate this would need more info about your system. Please open LO and go to menu Help > About; use the icon in the middle to copy the info to the clipboard and then post a new comment here and paste the copied info. There is more than just a version number.

Additionally, when you go to menu Help > Restart in Safe Mode, there is an option to completely reset your user profile to "factory defaults", with 2 sub-items. Please check those 2 sub-items too, but BEWARE that any customization you have had until that moment will be lost. There are also an advance option in the same dialogue that allows you to save a backup of your current profile before resetting it.

The reason to ask you to reset your profile is because you are able to work normally in LO's Safe Mode, which suggests some kind of profile corruption, at least potentially. There might be some other cause for your problem. In any case, your situation might not be easy to replicate by other users, and therefore not easy to resolve by a developer.

One potential semi-random test is to go to menu Tools > Options > Lode/Save > General > Save AutoRecovery information every 10 minutes and disable that check box.

An additional possible test could be to uninstall the current version of LO you currently have, and re-install the latest 7.6. version (ATM 7.6.5). I am not suggesting this as a real solution, but as a possible test (only if resetting your profile and providing your info here has no positive results). If using version 7.6 again would not generate the same crashes as your current 24.2 version, it would suggest that there is something unique in LO 24.2 that is not present in 7.6 that crashes. Please use this as a last resort and only after providing the requested info of your current version, and possibly additional other steps that might be suggested in later comments.
Comment 6 PAUL HOFSETH 2024-03-09 07:02:55 UTC
Thanks for your exytensive reply. i have changed the version and still have hangs

Version: 7.6.5.2 (X86_64) / LibreOffice Community
Build ID: 38d5f62f85355c192ef5f1dd47c5c0c0c6d6598b
CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Vulkan; VCL: win
Locale: nb-NO (nb_NO); UI: nb-NO

This version also hangs unexectedly even with empty profile & profile clened of all annoying textcorrecting prechoices.BUT it was stable this morning when running mye standard tests where "save as" leads to hang:  even with  momory hogginmg programs like firefox running qt the same time. Whwn crashing Windows still claims that the cause of "not communicating ewith windows" is unknown. So far I am using the very stable Apache Oo version for my manuscripts
Comment 7 ady 2024-03-09 07:55:45 UTC
I thought you said that LO 7.x used to work for you.

Please check whether there are driver updates available for your system. Some Skia issues are sometimes solved with that.

You comment 6 sounds as your whole OS crashing, not just LO. That was not the impression from comment 0. Please clarify.

Please also test using LO menu Help > Restart in Safe Mode, with the version you have now.

Additionally, please remember not to run 2 versions of LO simultaneously – you can have 2 versions installed in parallel, but it is recommended not to run them both at the same time. The same goes for LO and AOO; run only one of them at a time.

Please report back about all these points, including about updating your (graphic) drivers.

In the mean time, I am setting this report back to unconfirmed.
Comment 8 PAUL HOFSETH 2024-03-09 10:06:34 UTC

thanks for patient advice. 

Now I ran another test. I did update the Intel garphics driver and other matters that HP imagines must be corrected AND started editing a manusctipt of a few pages in ormal mode.

 The entire somputer has never crashed, but LO just did when I tried to save. No duplicate programs ever running (and I never run the computer as administrator with net connection, but usually as user "NET" without privileges) this is the latest useless windows event description

soffice.bin 
   7.6.5.2 
   32ec 
   01da72047738d699 
   18 
   C:\Program Files\LibreOffice\program\soffice.bin 
   2296c056-0f47-4941-83cd-ddd975c6799b
Comment 9 ady 2024-03-09 10:40:20 UTC
Is there some particular characteristic of the place/directory in which you are trying to save the file?

Please reset your profile again, as I described before. Then...

Please test disabling Skia:
1. Open LO, menu Tools > Options > LibreOffice > View > (Graphics Output)
2. Uncheck "Use Skia for all rendering" in order to disable it. Press OK, accept to restart LO.

Now please re-test whether the crash happens again.

Please report back.
Comment 10 PAUL HOFSETH 2024-03-09 11:22:57 UTC
Still hangs, this time when asking for LO-updates: and  no sensible explanation ,however, other data indicate that Windows is trying to execute unaanounced updates

still empty profile and graphics choice made as advised. 

I use a diredctory named "1 orden" to appear at the top of the list on drive c: All pictures and text is saved there so as not to have to search through the windows stupidly named directories. Windows has to be forceed to list it in my Altap.cz filewiever. 

I will try to work with the net turned off to avoid OS meddling. OR if necessaary fire up my big linux machine physically far fom the books i refer to while working.

p.
Comment 11 ady 2024-03-10 14:01:17 UTC
(In reply to ady from comment #5)
> One potential semi-random test is to go to menu Tools > Options > Lode/Save
> > General > Save AutoRecovery information every 10 minutes and disable that
> check box.

@Paul,

Please test while other software is closed (e.g. web browser, or anything else), in order to minimize potential interference.

Have you tested the AutoRecovery setting (that I just quoted)?

Please set it to ON (enabled), press "apply", and then OFF (disabled) and apply the setting (again to OFF). I know this might sound ridiculous, but with this "double-check" I am hoping this setting will be OFF for sure (not just in the UI).

After making that change, please test with a _new_ _empty_ document (and no other document opened, all closed), whether you can "Save as". Is the crash happening again in that case?

The reason to ask for this test is because the automatic AutoRecovery setting was re-instated in LO 24.2, and I wonder whether this change could have affected the normal behavior under some context / circumstances. This could also be relevant after you have reinstalled an older version, as you have.

An additional related setting to test would be "Always create backup copy", located in the same dialogue window as the AutoRecovery setting. In any case, these should be tested independently from each other.
Comment 12 PAUL HOFSETH 2024-03-10 14:59:45 UTC
thanks for your immense patience with my amateurish, desperate, efforts to continue working. 

By now I have a posible diagnosis. Windows does not like my systematic directory labelling "1-orden". Windows refuses to list that diretory except if forced. 

It has classified it so that it does not appear in the catalogue easily available as "my computer" hence creates difficulties when saving. 

L.O. does its routine saving with well timed intervals and hence hangs unexopectedly and independent of my input instead of only when i try to save. Hence I have now  moved important amnuscripts to the windows approved "documents" directory.

The seemingly random crashes have stopped without further massaging of your program.

p.
Comment 13 ady 2024-03-11 01:39:17 UTC
(In reply to PAUL HOFSETH from comment #12)

> The seemingly random crashes have stopped without further massaging of your
> program.

I am setting this report as Works For Me, as we don't even know whether there is some repeatable bug (by others) somewhere. If the problem shows up again, or additional information can be gathered in order to replicate the problem, please set the report back to "unconfirmed" while adding the relevant (new) info.