To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=57657
                  Issue #:|57657
                  Summary:|OOo completely breaks layout, sometimes even results
                          |in crash
                Component:|Word processor
                  Version:|OOo 2.0
                 Platform:|All
                      URL:|
               OS/Version:|All
                   Status:|UNCONFIRMED
        Status whiteboard:|
                 Keywords:|
               Resolution:|
               Issue type:|DEFECT
                 Priority:|P1
             Subcomponent:|formatting
              Assigned to:|mru
              Reported by:|whiteangel





------- Additional comments from [EMAIL PROTECTED] Thu Nov 10 02:18:16 -0800 
2005 -------
I'm writing down my school notes using stable OOo2.0 on Debian. Take a look at
my document:
http://193.95.242.3/tmp/APS-I-zapiski.odt

As you can see, the document consists of many drawings, paragraph styles,
formulas and tables. If this were a few pages long document, OOo handled it
fine. But when document became 20+ pages long, I began experiencing some *very*
critical issues:
1) Having OOo session opened for more than 3 hours and editing the document,
copying&pasting from draw component etc. usually results in crash (memory leak?)
2) Some of the vector drawings (arrows, rectangles, drawn in OOo Draw component)
randomly loose vertical positions. They look anchored at the correct paragraph,
but the Y offset is completely messed up (eg. they appear on a 2000th page, or
at the beginning of the document?!?)
3) Switching from web layout -> page view also results in unexpected behaviours.
Elements randomly loose their Y offset (rerendering of the document?).
4) When you load the document, it's imperative to wait for 30 or so seconds, go
slowly from top to the bottom of the document so the OOo aligns things as they
should be (and some are not!) and only then proceed to the end of the docuemnt
and start writing. Shouldn't the complete layout be calculated and stable when
you open the document? Now, if you don't follow the rules I mentioned, you get
elements randomly loosing their anchors and jumping up and down.
5) When undoing in the mentioned document, every undo becomes composited of 5 or
so steps. One of them is your actual action. The other four are the new
automatic alignmnents of the drawings that jump from a for me unrelated random
page to another unrelated place. This appears no matter where I'm making the
document change. (maybe some elements are at the end of the document and I don't
see them and they're related somehow?)
6) Today, OOo2 crashed when I wanted to save my document and the recovery
program was only able to recover the original document (this resulted in a 30
minutes of lost data!). I really don't know why the AutoSaveRecovery function
isn't enabled by default in the configuration. It's obvious that OOo2 isn't
stable enough IMO for this option being turned off.

All of the issues are very obvious in the document I'm reffering to. I'm
personally really dissapointed about these issues: I was using OOo1.1beta 3
years ago with similar document complexity and I was encountering the same bugs.
This points out that the internal formatting&typesetting code wasn't touched a
bit for so much time... and it's obvious that it needs fixing, if not a complete
rewrite. Am I the only one experiencing this?

---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to