If I edit a report with some vertical lines (column separator) in a group section and select one vertical line one after another to change some properties, the report designer starts eating all my memory. I have to kill LO and all report editings are lost.
@Robert Do you remember if other bugreports describe the same behvior. If yes: which bugreports?
(In reply to comment #1) > @Robert > Do you remember if other bugreports describe the same behvior. If yes: which > bugreports? Jochen, Lines, as in fixed drawn lines, especially vertical ones, have been causing problems in reports for a while now, and even cause crashing in 3.6.0.4 and current master builds. However, manipulating objects on the section canvas is also known to cause LO to use up all available memory and then eventually either have to be killed or kills itself. So this report is a duplicate either of the lines problem, or the graphical object coordinates problem (which according to Thorsten is a ruler boundary code problem that has gone out of control). Personally, I would stick it as a dup of the line drawing problem. Alex
@Thorsten, (In reply to comment #2) > ... which according to Thorsten is a ruler boundary > code problem that has gone out of control. Please: have you time to look at this bugreport? What is your opinion: dup of another bugreport (which?)? Separate problem/bug? Do you need some further information?
(In reply to comment #3) > @Thorsten, > > (In reply to comment #2) > > ... which according to Thorsten is a ruler boundary > > code problem that has gone out of control. > > Please: have you time to look at this bugreport? What is your opinion: dup of > another bugreport (which?)? Separate problem/bug? Do you need some further > information? Sigh. Jochen, you could've looked these up for yourself : https://bugs.freedesktop.org/show_bug.cgi?id=53872#c16 https://bugs.freedesktop.org/show_bug.cgi?id=33617 https://bugs.freedesktop.org/show_bug.cgi?id=44721 Alex
Taking a stab and marking as duplicate of 33617 Alex *** This bug has been marked as a duplicate of bug 33617 ***