[Paraview] Clip filter bogs down after repeated Clip Type changes

[Utkarsh Ayachit]

I had your email lying in my inbox for follow up. I don't think I've
seen it on the bug tracker.

Utkarsh

On Thu, Feb 11, 2010 at 12:48 PM, Eric E. Monson <emonson at cs.duke.edu> wrote:
> Hey Utkarsh,
>
> That seems to work great now -- good job! Thanks for getting back to this.
>
> It's weird, though, I could have sworn I filed a bug report on this at the time, but I can't find the listing for it... Did you just keep track of this through the mailing list, or did it show up on the bug tracker? Maybe I screwed something up...
>
> Anyway, it looks like it's working fine now.
> -Eric
>
>
> On Feb 10, 2010, at 10:19 AM, Utkarsh Ayachit wrote:
>
>> Nice catch. There was a bug in the pqAnimatablePropertiesComboBox.
>> I've committed a fix to the CVS. Feel free to try it out.
>>
>> /cvsroot/ParaView3/ParaView3/Qt/Components/pqAnimatablePropertiesComboBox.cxx,v
>> <--  Qt/Components/pqAnimatablePropertiesComboBox.cxx
>> new revision: 1.7; previous revision: 1.6
>>
>> Utkarsh
>>
>> On Wed, Jan 13, 2010 at 4:54 PM, Eric E. Monson <emonson at cs.duke.edu> wrote:
>>> Hello,
>>>
>>> I noticed something strange when debugging a variation on the clip filter as a plugin, but found that it happens with the standard Clip filter, too. If you switch repeatedly back and forth between Clip Types (Applying in between), the filter starts getting slower and slower and eventually bogs downs completely. To demonstrate:
>>>
>>> Create a default Wavelet Source
>>> Clip Filter -> Apply
>>> Switch from Plane to Box Clip Type -> Apply
>>> Switch back to Plane Clip Type -> Apply
>>> Repeat last two...
>>>
>>> After switching clip types about a dozen times I can see a few second delay before the new clipped data shows up in the render view, and by 13 it takes many seconds to show up. Memory use seems to increase on each iteration, but from about 85 to 110 Mb over those steps, so it's not enormous by the end... If you delete the Clip filter and create a new one, it starts over fresh (w/o memory usage drop) and you can repeat the same eventual slowdown.
>>>
>>> (I can get this to happen both on Mac OS X 10.6.2 x86_64 Cocoa CVS Paraview built with CVS CMake, as well as on today's Ubuntu 9.10 32-bit PV 3.6.2 binary download -- haven't tried any others yet.)
>>>
>>> Any ideas?
>>>
>>> Thanks,
>>> -Eric
>>>
>>> ------------------------------------------------------
>>> Eric E Monson
>>> Duke Visualization Technology Group
>>>
>>> _______________________________________________
>>> Powered by www.kitware.com
>>>
>>> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html
>>>
>>> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView
>>>
>>> Follow this link to subscribe/unsubscribe:
>>> http://www.paraview.org/mailman/listinfo/paraview
>>>
>
>