https://bugs.documentfoundation.org/show_bug.cgi?id=89783
--- Comment #13 from Christoph Lutz <chrl...@googlemail.com> --- In this comment I try to specify little bit more concrete what needs to be done to solve this issue completely: The current state regarding the above test files is: * 32 frames --> LO freezes after 2048 datasets (tested with master) * 32 sections --> freezes after 2048 datasets (tested with master) * 32 draw lines --> freezes after 2048 datasets (tested with master) * 32 (different) Headers --> segfault somewhen >2000 datasets processed (tested with LO 4.2 on Win) * 32 lists --> behaves like O(n2) but seems to run successfully (tested with LO 4.2 on Win). It is not yet tested what happens if there are actions done on the created document * 32 tables --> mailmerge runs successfully. Changing some of the tables in the result document seems to work, but saving the result seems to freeze/hang LO The expected behaviour is: 1) mail merge on the above document can be executed successfully (= no more freeze). This should be ensured for all possible ways to start mail merge in LibreOffice: mail merge printing via "File->Print", mail merge via "Tools->Mail Merge Wizard", mail merge via UNO-Service. 2) Test and fix roundtripping and further processing actions on the generated (big) document: 2a) Change some of the elements in the generated document - at least test with some elements on the first pages, some elements from the middle of the document and some elements on the last pages. Possible change actions are: - add some (new) text - change some formatting attributes 2b) Remove some elements from the document - again from the beginning, middle and end 2c) Add some new elements at the begin, middle and end 2d) In particular ensure that copy & paste works - I got hints that this could be a problematic cornercase: test doing CTRL+a, CTRL+c and CTRL+v at the end of the generated document. 2e) Save and close the result document 2f) reopening the document works fine and changes like in 2a) can be done successfully In order to make testing more efficient, It could be useful to write the corresponding unit tests very early. This could for example be done like in http://cgit.freedesktop.org/libreoffice/core/tree/sw/qa/extras/mailmerge/mailmerge.cxx -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
