> I am unable to reproduce the ods save issue. It does use a lot of cpu > for a short > while, but then finishes as expected. Your stack trace suggests that it did > finish.
I had to press Ctrl-C and then used to the command bt to obtain the trace. I then promptly exited gdb and killed gnumeric with it. I had to do this because the saving process was taking a very very long time. I'll give it another try. > I am unclear on how to reproduce the the BadAlloc crash. Could you please > spell > out the steps in detail? I.e., what is selected and what is dragged. I tried to simplify the steps (skip the fourier analysis part) and got the same issue: 1. Open the ods file attached 2. In an adjacent column type: =imabs( complex ( B2 , C2 ) ) 3. Drag downward about 2000 cells 4. Now select the whole new column, i.e. go to the first cell then hold shift, press end and then the downward arrow. 5. Drag this column selection to the right 6. BadAlloc crash... > If I read things right, you are using gtk+ 2.20.x Around that time, > gtk+ underwent > serious changes in its window handling switching to "client side > windows". It was quite > buggy for a while. Is it possible for you to upgrade gtk+? You are correct, I'm using gtk+ 2.20.1, which is in the standard debian repositories. I'm hesitant to upgrade a core library in my Squeeze system for one in the experimental repository (gtk+ 2.22.0), but if you are not able to reproduce the issue after my detailed explanation then I'll give it a try. Thanks Andres -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
