Apache OpenOffice (AOO) Bugzilla – Issue 75285
RTF: Writer takes too long on opening 3rd party (Axapta) consisting of many frames
Last modified: 2017-05-20 11:17:49 UTC
Writer hungs when trying to open file axaptareport.rtf (sent to MRU, because the file is somewhat confidential). Priority P2 because of loop and because such files are generated by at least one major Russian retailer, which makes the problem widespread. Please consider targeting for 2.2.1. Thanks a lot.
MRU->OD: the RTF document consists of many frames (tables, that have been generated by placing frames next to each other). This will cause a loop in Writer.
Dear developers, any news on this issue? Thank you very much for your attention. WBR, K. Palagin.
OD->kpalagin: Sorry. Until now I haven't got found time to look at this issue. Probably, I'll have some time next week.
Oliver, that would be great! Fixing the problem in 2.3 would be absolutely terrific! Thanks a lot for response! WBR, KP.
Any progress? Fixing RTF problems will be quite important starting from 2.3 as we are becoming default handler for .rtf (see http://www.openoffice.org/issues/show_bug.cgi?id=15220). Thank you very much for your attention!
OD->kpalagin: Sorry, but I still haven't got time to look at this issue. Please stay tuned.
Is there still a chance of fixing this in 2.3? Thanks a lot for your attention.
OD->kpalagin: I have to admit, that I've lost the focus on this issue - thx for the reminder. I will retarget it to OOo 2.3 in order to keep an eye on it in the next weeks. I think, until the end of June I will make up my mind, which of the issues I'm owning and are on target OOo 2.3 are fixable for OOo 2.3
Oliver, please try fixing this for 2.3 - this issue is indeed very important if your biggest customer sends such files every day. Thanks a lot. WBR, KP.
A bit of competitive analisys - in Russia Microsoft grows by leaps and bounds (100% per year). This means that 1. files that cause loop will be more common (as they are generated by MS Axapta). 2. we have to address our problems faster to remain competitive against competing Office product. Thans a lot in advance.
First investigation reveals, that it isn't an endless loop and that it isn't a layout loop. But, it's takes very long to load this document and very long to paint this document. Please check in OOo 2.2.1.
2.2.1 (released), 2.3m217 also do not open that doc in reasonable time.
Any progress with this problem?
This issue is still on my list to my list for OOo 2.3. But, I've to fix five issues in advance. I can't promise, that I manage it to fix it in time for OOo 2.3
due to lack of resources I have to re-target this issue to OOo 2.4
Sample Axapta report in RTF, shows 2 major problems: 1. hideously slow doc rendering: about 1 minute on Athlon64-2800+, 512 RAM 2. doc formatting is broken, only 1 page shows
Created attachment 47645 [details] sample
Oliver, are we on track for 2.4 with this issue? WBR, KP.
OD->kpalagin: Currently, this issue is the on position 6 in my issue queue for OOo 2.4 Next week I'll clean up my issue queue for OOo 2.4, which currently contains 12 issues. Then, I will know, if I can work on a fix for this issue for OOo 2.4
due to limited resources I have to re-target this issue to OOo 3.0
Oliver, what is the current status of this issue? Thansk a lot for your attention. WBR, KP.
This issue is in my queue for OOo 3.0. Until OOo 3.0 Beta (currently planned code freeze for OOo 3.0 Beta is at the beginning of April 2008), I will work on new features and enhancements for OOo 3.0. Afterwards I will work on fixing defects and currently this issue belongs to the issues I want to fix then.
Thanks for your answer. Hopefully it would not miss 3.0. Regards, K. Palagin.
Yes, I also have this hope, because I do not like shifting a defect again and again to a later target. But due to the limited resources and more important issues it have to happen again and again.
Due to limited resources re-target to OOo 3.x - sorry for again shifting this issue
*** Issue 89865 has been marked as a duplicate of this issue. ***
3.x seems to be too far away for this voted crasher. Maybe 3.1?
OD->kpalagin: Yes, you are right. OOo 3.1 is better. When I re-target this issue in April target OOo 3.1 did not exist. But, as I already figured out this is not a loop or a crash, but it takes too long for formatting and painting. Thus, adjusting the summary.
Oliver, are on track for 3.1 with the fix for this issue? Thanks a lot. Regards, KP.
OD->kpalagin: Thanks for the reminder. My current defect in-tray for OOo 3.1 contains 45 issues. Until end of mid of November I will be working on metadata support for OOo 3.1 and OOo 3.0.1 bug fixing. At the beginning of November I will attend the OOoCon 2008 in Beijing. Code freeze for OOo 3.1 is mid of December. Thus, I think that a fix for OOo 3.1 is on risk. Currently, I can not say, if a fix will be available for OOo 3.1 or not.
I am sorry. Again I have to shift a fix for this issue to the next target.
Evaluating this issue reveals the following: ad "wrong layout" issue: This one would be quite hard to fix, because the complete document does not contain any regular content. Even an empty paragraph does not exist. There are only many many text frames and lines. Checking the document in Microsoft Word 2003 reveals that a page break at an empty paragraph in a certain text frame on page two causes that this text frame and all the following are on another page. This page break attribute needs to be evaluated during the RTF import to create also a "page break" in Writer. For a stripped document it works, but not for the given one. Further investigation needed. ad "performance" issue: Currently, the Writer layout is not optimized for such documents, because it is not the purpose of a word processor to handle hundreds of objects one each page without any other content. Thus a fix of this problem has a low priority. Thus, I will submit a new issue for "layout wrong" issue. By this issue the "performance" issue will be handled.
New issue for the wrong layout is issue 103610. Adjusting priority to P3 and target to OOo 3.x
Reset assigne to the default "issues@openoffice.apache.org".