Issue 71999 - Saving an odt-document impossible, without error
Summary: Saving an odt-document impossible, without error
Alias: None
Product: Writer
Classification: Application
Component: save-export (show other issues)
Version: OOo 2.0.4
Hardware: PC Windows XP
: P3 Trivial with 2 votes (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Keywords: oooqa
: 101877 (view as issue list)
Depends on:
Reported: 2006-11-26 20:38 UTC by uscholz
Modified: 2017-05-20 11:18 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

file which is not savable with writer since short time (974.98 KB, application/vnd.sun.xml.writer)
2006-11-26 20:44 UTC, uscholz
no flags Details
Warning upon opening the document (33.51 KB, image/png)
2007-01-29 00:30 UTC, shahid_sorkhabi
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description uscholz 2006-11-26 20:38:42 UTC
I've got a 1 MB odt-document containing some tables, pictures, text. Since short
time, without having done anything specific, when saving the document, the
process indicator stops at about 70 % and thats it, task manager says "no
response", no real error message occurs. I'm using the newest writer version
2.0.4 and my RAM is 2 GB. I would make available this document for other guys to
help me, but don't know where to upload it. - Is there a way to track the
document, to see where exactly in it (at which position or text-element) the
problem occurs?
Thank you for helping me, Ulli (uscholz)
Comment 1 uscholz 2006-11-26 20:44:19 UTC
Created attachment 40923 [details]
file which is not savable with writer since short time
Comment 2 michael.ruess 2006-11-28 09:32:37 UTC
Reassigned to ES.
Comment 3 shahid_sorkhabi 2007-01-29 00:30:12 UTC
Created attachment 42534 [details]
Warning upon opening the document
Comment 4 shahid_sorkhabi 2007-01-29 00:30:37 UTC
When trying to open the file Oo displays a message regarding macros being
present in this document which might potentially contain viruses. (see attachment)

Clicking on "Disable Macros", the document opens with no problems.
Clicking on "Enable Macros", the document opens with no problems.

Changing some text and saving takes a huge amount of time, but it _does_ save in
the end. I did _not_ notice a high amount of CPU usage. RAM allocated to Oo
while saving this document hovers around 70MB.

Bug not reproducible on my machine (Win XP SP1, 512MB RAM Oo 2.0.4).
Comment 5 Rainer Bielefeld 2007-02-25 08:33:28 UTC
I checked with "2.0.2  German version WIN XP: [680m5(Build9011)]" and can
confirm the reported effect: save process seems to stop at 75% save progress,
but after app. 1/4 hour the save process will come to an end. 

I checked with "2.2.0  Dev. Snapshot  WIN XP: [680m7(Build9118)]" and it still
takes a long time to save the document, but not as long as with 2.0.2.

Strange observations;
When I open '' with 2.0.2 the Macro warning box will appear 2
times, the second one 1-2 seconds after the first one.

In the Macro dialogues I see listed a Python macro 'C:Programme\Microsoft

The document contains 2 linked contents (pls. test 'Edit > Links') what do not
exist, (2. Foil MAD / look at Foil #4?).

Currently It seems that the document is damaged, but of course, it should be
possible to save it within a normal time.
Comment 6 eric.savary 2007-02-26 08:38:18 UTC
ES->MBA: I think about a duplicate of issue 7553 but this time while saving. The
document contains a lot of hyperlinks (among them, Server or local Windows-like
links). Reproduced on Windows. No problem on Linux.
Please have a look.
Comment 7 Mathias_Bauer 2007-12-03 17:16:31 UTC
target 3.0
Comment 8 Mathias_Bauer 2008-07-08 16:46:41 UTC
not fixed until code freeze, moved to next possible target
Comment 9 Mathias_Bauer 2008-12-03 16:43:42 UTC
Saving the document takes so long because the export filter tries to check if
URLs respect case sensitivity. This requires to get volume information for each
and every part of a URL. In case of UNC pathes this is quite expensive (and
takes even longer if the path does not exist).

There is no simple way to fix that. The right way would be not touching URLs on
loading and saving at all. But that would require a lot of other changes in the
code to make sure that URLs respect case sensitivity and relative or absolute

Honestly speaking, I doubt that this will happen soon. The only reason why I set
the target to 3.x and not to "OOoLater" is that it might be possible to fix that
in our planned effort for better performance.
Comment 10 michael.ruess 2009-05-14 10:01:31 UTC
*** Issue 101877 has been marked as a duplicate of this issue. ***
Comment 11 Marcus 2017-05-20 11:18:11 UTC
Reset assigne to the default "".