Summary: | FILEOPEN DOCX: Footnote with two character custom marker imported incorrectly | ||
---|---|---|---|
Product: | LibreOffice | Reporter: | Aleksei Nikiforov <darktemplar> |
Component: | Writer | Assignee: | Not Assigned <libreoffice-bugs> |
Status: | NEW --- | ||
Severity: | normal | CC: | kelemeng, telesto, vercha, xiscofauli |
Priority: | medium | ||
Version: | Inherited From OOo | ||
Hardware: | All | ||
OS: | All | ||
See Also: | https://bugs.documentfoundation.org/show_bug.cgi?id=152425 | ||
Whiteboard: | |||
Crash report or crash signature: | Regression By: | ||
Bug Depends on: | |||
Bug Blocks: | 109195 | ||
Attachments: |
issue.docx
Minimized example file from Word 2013 Footnote settings in Word and endless loop in LO The footnotes custom mark is **), The example file in Word 2016 and Writer |
Description
Aleksei Nikiforov
2022-02-09 09:26:57 UTC
Repro Version: 7.4.0.0.alpha0+ (x64) / LibreOffice Community Build ID: ca657b98e49eb2282775f7919827062a7a0b4bfe CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win Locale: nl-NL (nl_NL); UI: en-US Calc: CL Also in 6.1 and in Versie: 4.4.7.2 Build ID: f3153a8b245191196a4b6b9abd1d0da16eead600 Locale: nl_NL and in 4.1 also in 3.3.0.4 @Xisco I'm stuck how to prioritize this. In old win x32 builds this would eventually crash, because of memory of the limit (sane solution). Consuming all resources today is pretty bad, it freezes the whole system. There are not many cases of this happening (as far I know) an i have no clue why the document here causing this problem to appear.. but even if this is a broken bug doc, it should not consume all the system memory available Created attachment 178321 [details]
Minimized example file from Word 2013
Looks like this footnote causes the trouble, also all the way back to 3.5.
Removing this from the original document in Word does not reproduce the endless loop.
Created attachment 178322 [details]
Footnote settings in Word and endless loop in LO
This looks to have an interesting setup:
- in the document looks like it has a Custom mark of **
- but the Footnote and Endnote dialog has that field empty and considers it as a plainly numbered footnote.
Created attachment 178323 [details]
The footnotes custom mark is **),
(In reply to Telesto from comment #4) > @Xisco > I'm stuck how to prioritize this. In old win x32 builds this would > eventually crash, because of memory of the limit (sane solution). Consuming > all resources today is pretty bad, it freezes the whole system. > > There are not many cases of this happening (as far I know) an i have no clue > why the document here causing this problem to appear.. but even if this is a > broken bug doc, it should not consume all the system memory available Inherit from OOo times, I think it should not be high/major unless this has some duplicates (In reply to Xisco FaulĂ from comment #8) > Inherit from OOo times, I think it should not be high/major unless this has > some duplicates Totally freezing the OS by using all resources (available memory) isn't something I comfortable with. I would be already happy with fail save/ temporary hack to prevent all the system resources being used on a "simple document" There are couple more page looping DOCX files (maybe the same issue?) Created attachment 186463 [details] The example file in Word 2016 and Writer This no longer loops in master since: https://git.libreoffice.org/core/+/13d30067370353ae5a43c2f2cbd69bb824363815 author Mike Kaganski <mike.kaganski@collabora.com> Wed Jan 11 17:02:04 2023 +0300 committer Mike Kaganski <mike.kaganski@collabora.com> Thu Jan 12 04:34:27 2023 +0000 tdf#152425 Synchronize import and export style names mapping However the footnote is still a mess. Let's focus on that. |