I have two different odt files. The problem is Writer hangs after a few minutes without any operation at all. Just open the document and wait for a few seconds. LibO becomes unresponsive, and shows hourglass for mouse pointer. After this point, it is not possible to do anything at all. I have to force LibO to close using Process Explorer. Even OOo behaves identically. However, the file can be opened without crashing in MS Word 2010. (But the formatting gets so messed up that I cannot use the file at all.) For some reason, LibO is not generating crash report. The issue was raised in OOo issue tracker (using the "Raindrops" user name), and I have submitted a lot of crash recovery reports. The original issue was split and combined by support team, but there is no solution so far. A lot of investigation has already taken place in OOo, and the issue is tracked down to a defective algorithm that recalculates page layout. I got the following information from the investigators: 1. The algorithm gets stuck when resolving placement of images in tables that run over several pages. It also faces problem when resolving complex layouts where placement conditions conflict with each other (e.g. nested tables, paragraphs with "keep with next" attribute, "with paragraph" image anchors) 2. The algorithm does not have a timeout or max number of tries; so it keeps trying endlessly. Out of the two files, one is 133 pages long, and the other is 380 pages long (A4 size paper). Here are some common characteristics: 1. Both files have a similar size: About 5 MB 2. Both contain headers, footers and TOC. 3. Both contain long tables spread over 3+ pages 4. Both have large number of images placed inside tables, anchored "as character" Dissimilar factor: The 380+ page file has tables that run for about 20 pages each. Further, there are nested inner tables in this file. Several tables have merged cells (rows/columns) The smaller file does not contain nested tables. Its tables are relatively shorter. I can share the files through DropBox, etc. Please let me know.
Hi narayanaras, please would you share your file :) Since it has some detailed analysis in the description, add Cedric to cc list. Thanks for reviewing!
Hi! Thanks for the rapid response. I will upload both files tonight in DropBox and post links here. I will also post links to the analysis done by the OOo support team, so that the team can check out what conclusions are drawn already. That should give a head start in this investigation. Some more observations: 1. Sometimes it is possible to delay the crash by pressing F9 or using the Tools>Update>Update all option. (This was suggested by the OOo design team, but it works only in some cases) 2. If I go rapidly up/down in the document, it surely triggers the seizure. 3. When LibO hangs, soffice.bin process starts hogging around 49% of CPU. So this may correspond to one core. (If you want specific figures, please let me know what figures to collect.) (This is a HP Compaq 6000 Pro MT PC, with Core 2 Duo E7500 CPU @2.93 GHz, with 2 GB RAM. Running Windows 7 32-bit.) The other figures are as follows: Virtual memory -Private bytes: 1,12,972 kB (88,696 kB) Virtual memory -peak Private bytes: 1,17,056 kB (89,040 kB) Virtual size: 8,45,300 KB (8,12,504 kB) page faults 1,96,844 (1,72,949) Handles: 482 (480) GDI Handles: 170 (105) User handles: 107 (105) Figures in brackets refer to a 7-page "average complexity" document, which does NOT crash.
Slightly reducing the severity. It is an older bug. It happens only with a particular and huge document => it can't block 3.4.0 release
Update: Here is the link to my original bug, raised for OOo. http://openoffice.org/bugzilla/show_bug.cgi?id=61557 (It was raised FIVE years ago, and nothing has happened since.) I do hope the bug-is given a due "seniority"! The two problematic files are shared here: 1. http://db.tt/Z2dn0y5 2. http://db.tt/24SoQVI After downloading, please confirm here, so that I can remove the sharing. Thanks!
An additional observation: LibO seems to hang if I paste some content from clipboard (especially text with some hyperlinks). To avoid hanging, I have to quickly save (CTRL+S) and then close LibO, and re-open the document.
It's a long time since I shared those files. Is there any progress on this issue? Would appreciate some comments/feedback.
The files aren't available any more, I get a 404 for both links.
Well, I kept them online for a week. I will put them again tonight (for one week). Thanks.
One week is a too short time. You can't expect *any* kind of service level guarantee (like bug reports being handled in a week, or some other time) here. If you want that, you need to buy a support contract from some suitable company.
You misunderstood me. Dropbox is just another way of transferring the file, in which I do not have to know the recipient's ID. However, since my free Dropbox account is too small to hold all my transferred files, I have to remove them as soon as I can. That is why I have to know whether someone picked up the file. In case of OOo, I used to send the file directly through email. (These files are not meant to be in public domain.) I can do that even now, if someone provides the email ID. Thanks for your understanding.
[This is an automated message.] This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it started right out as NEW without ever being explicitly confirmed. The bug is changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases. Details on how to test the 3.5.0 beta1 can be found at: http://wiki.documentfoundation.org/QA/BugHunting_Session_3.5.0.-1 more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html
needinfo keyword redundant by needinfo status.
@narayanaras Please, email those files to me.
Dear bug submitter! Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs. To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem. Yours! Florian