Issue 29842 - Documents freezing OOo
Summary: Documents freezing OOo
Alias: None
Product: Writer
Classification: Application
Component: ui (show other issues)
Version: OOo 1.0.1
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Keywords: needmoreinfo, oooqa
Depends on:
Reported: 2004-06-03 18:30 UTC by
Modified: 2013-08-07 14:38 UTC (History)
3 users (show)

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

Document freezing OOo (388.07 KB, application/vnd.sun.xml.writer)
2004-06-03 18:33 UTC,
no flags Details
another one freezing OOo too (30.12 KB, application/vnd.sun.xml.writer)
2004-06-03 18:35 UTC,
no flags Details
Recovered document (18.32 KB, application/vnd.sun.xml.writer)
2004-06-04 17:34 UTC, eric.savary
no flags Details
some other corrupted files (433.17 KB, application/x-compressed)
2004-06-04 18:21 UTC,
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description 2004-06-03 18:30:43 UTC

OOo freeze any time I tried to open these files. They have been created under
OOo 1.1.0. I've tried with OOo 1.1.0, 1.1.1, 1.1.2rc3 and 680m38.

Kind regards - Sophie
Comment 1 2004-06-03 18:33:43 UTC
Created attachment 15664 [details]
Document freezing OOo
Comment 2 2004-06-03 18:35:00 UTC
Created attachment 15665 [details]
another one freezing OOo too
Comment 3 2004-06-03 18:38:30 UTC
I forgot to say that I'm not the author of those documents. The user said that
it seems to appear any time she moves large part of text inside the document.
For her, sometime the document open after several minutes and sometime it
doesn't open at all. If needed, I have other files to attach.
Kind regards
Comment 4 michael.ruess 2004-06-04 09:49:31 UTC
MRU->ES: freezes while loading, pls have a look.
Comment 5 eric.savary 2004-06-04 17:33:34 UTC
Well, very strange..
2 or 3 pieces of text have about 9880 (!!) alphabetical index entry marks for
each of them. I don't think it really freezes but the performance tends to go to
- infinity...

The first file has on top a lot of change tracking information, which makes the
things worst.

It would be very interessant to know what the user did while marking some word
as alphabetical index entries.
Sophie, can you ask?
Did something strange happened during the work? Did she use a macro tool or

I attach a recovered version of the second file

ES->Daniel (just CC): any idea?
Comment 6 eric.savary 2004-06-04 17:34:24 UTC
Created attachment 15686 [details]
Recovered document
Comment 7 eric.savary 2004-06-04 17:34:51 UTC
Changed target
Comment 8 eric.savary 2004-06-04 17:35:19 UTC
Comment 9 2004-06-04 18:03:52 UTC
Hi Eric,

In fact this is my publisher (Eyrolles Editions) who sent those documents to me
because they are migrating to OOo and all the authors are writing their books
under OOo now. 
I have a bunch of those corrupted files, if you want to play with them, I'll
attach a zip here.
What I know is that the author was re-writing his chapter after being corrected
by the publisher. Index entries are for the book index, but I'll ask for more
infos and keep you update.
Eric, thanks a lot for the recovered file, I'll send it back to the publisher. 
Kind regards - Sophie
Comment 10 2004-06-04 18:21:12 UTC
Created attachment 15687 [details]
some other corrupted files
Comment 11 openoffice 2004-09-06 19:11:02 UTC
dvo->es, sgauti: The time is indeed spent while reading those many alphabetical
index marks. I personally am of the opinion that reading a ridiculous number of
alphabetical index marks may also take a ridiculous amount of time, so *that*
isn't the primary problem. The primary problem is how all of those index marks
got there in the first place.

I assume some bug causes duplication of index marks. I'd guess some combination
of redlines + alphabetical index marks since those are the two special things
noticeable in the document. Unfortunately this kind of problem is a bit hard to
diagnose, since we only see the result of the bug, but not the bug itself. So
I'm thankful for any hints. :-)

(There was once a similar problem where a bug caused duplication of certain
elements with each save, so the number of items grew enormously over time and
caused massive performance problems. This case sounds quite similar.)

dvo->es: Please assign the bug to me. I'm not sure about the target; I would
have expected something sooner than 'OOo later'.
Comment 12 eric.savary 2004-09-07 11:22:49 UTC
ES->DVO: "OOo later" was set to give me time analyzing. Indeed, I'd like to have
it fixed for 2.0. I'll try to reproduce the duplication of index marks.
Comment 13 andreas.martens 2004-12-03 08:39:24 UTC
Changed prio to 4
Comment 14 andreas.martens 2005-03-30 13:27:19 UTC
We will not find a solution for OOo2.0, but we have to have another look at this
issue for OOo2.0.1. So I raise the priority again.
Comment 15 andreas.martens 2005-05-25 13:46:02 UTC
Considering the effort, the priority, the risk and our resource planning I've to
retarget this issue to OOo Later.
Comment 16 ace_dent 2008-05-14 23:32:13 UTC
This Issue requires more information ('needmoreinfo'), but has not been updated
within the last year. Please pre-test with one of the latest versions of OOo -
the problem(s) may already be addressed. Either use the latest stable version:
or consider trying the new OOo 3 BETA (still in testing):

Please report back the outcome of your testing, so this Issue may be closed or
progressed as necessary - otherwise the issue may be Resolved as Invalid in the
future. You may also wish to search for (and note) any duplicates of this Issue
that may have progressed further :


Cleaning-up and Closing old Issues as part of:
~ The Grand Bug Squash, pre v3 ~
Comment 17 2008-05-15 05:20:10 UTC

The needmoreinfo keyword is wrong here, it should be needmoretime. So please
don't close this issue, read the dev comments.

Kind regards
Comment 18 orcmid 2012-05-12 19:28:45 UTC
The change-tracking symptoms that were also mentioned for the publishing use case in this bug report may be related to those just demonstrate in this issue:
Comment 19 Rob Weir 2013-07-30 02:24:12 UTC
Reset assignee on issues not touched by assignee in more than 2000 days.