[Libreoffice-bugs] [Bug 146944] Crash in: lcl_Regist

2022-01-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=146944

Albrecht Müller  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|UNCONFIRMED |RESOLVED

--- Comment #5 from Albrecht Müller  ---


*** This bug has been marked as a duplicate of bug 146845 ***

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

[Libreoffice-bugs] [Bug 146944] Crash in: lcl_Regist

2022-01-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=146944

--- Comment #4 from Albrecht Müller  ---
I uploaded  attachment 177914 that shows the "strange effect". But I was not
able to use this document to create any crash. I did expect that as I assume
that the crash reported here is independent from this particular document and
occurs at random for reasons I don't know. That's why I let LibreOffice upload
three crash reports. For the other two see bug 146845 and bug 146943.

The crashes occurred in pretty different situations but showed a similar
behaviour. First there is a "common" crash which does not produce a crash
report. If you start LibreOffice after this kind of crashes it usually launches
a recovery process. This process is intended to restore all open documents to
in state they were when last saved automatically. According to the settings of
my autosave option the last 10 minutes of work may get lost.

What is different here is that the recovery process crashes or runs into an
endless loop. LibreOffice proposes to send a crash report when the recovery
process crashes or when you abort the process that shows the endless loop.

Common symptoms are:

At start LibreOffice usually shows a splash screen before it opens the first
window. This splash screen appears and disappears in varying rates ranging from
more than one cycle per second to one cycle every few seconds. This process may
finish either by crashing or because you abort it. If you start LibreOffice
again then the recovery process usually seems to work but you have to repair
the user profile. I have couple of extensions that cease to work until the user
profile is fixed.

This said – here are the steps to reproduce the strange effect as I think it is
interesting by itself:

Open the attached document in some environment that does not allow to execute
macros. Writer will report that the document contains macros, that it will not
execute them and that therefore the document may not work as expected. There
are no macros in the document and it seems to be empty. Copy the complete
content of this document into the clipboard, e.g. by using Ctrl+A to select the
content and Ctrl+C to copy it in the clipboard.

Create some new, empty document and paste the content there. Save it. Reopen
it: LibreOffice will warn you about macros in the document.

How come? My explanation: This warning seems to be triggered by a field that
executes a macro when clicked. This macro does not exist and the field is not
visible as it does not contain any description. Once you know what's going on
you can make the field visible by telling Writer to show field names (Ctrl+F9)
and/or to show fields on a grey background (Ctrl+F8, shortcuts valid for German
UI, don't know if they are the same in other languages).

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

[Libreoffice-bugs] [Bug 146944] Crash in: lcl_Regist

2022-01-30 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=146944

--- Comment #3 from Albrecht Müller  ---
Created attachment 177914
  --> https://bugs.documentfoundation.org/attachment.cgi?id=177914=edit
File that seems to be empty but lets Writer produce a macro warning

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

[Libreoffice-bugs] [Bug 146944] Crash in: lcl_Regist

2022-01-27 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=146944

Telesto  changed:

   What|Removed |Added

 CC||tele...@surfxs.nl

--- Comment #2 from Telesto  ---
Crashing is not OK, even though there is some corruption, IMHO
But well an example file would be needed to fix the crash

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

[Libreoffice-bugs] [Bug 146944] Crash in: lcl_Regist

2022-01-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=146944

Albrecht Müller  changed:

   What|Removed |Added

 CC||albrecht.muel...@astrail.de

--- Comment #1 from Albrecht Müller  ---
Found the cause of the strange effect: The document contained a field referring
to a non-existent macro located in the document. After removing this field
Writer stopped to complain about macros in the document.

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