[Paraview-developers] slowness getting even slower

Wed Apr 20 05:39:47 EDT 2011

Utkarsh.

Thanks. Panels in singular form now.

Question : To fix this bug - you created a bug report, committed a fix to the 'Collaboration' branch referring to the bug, then merged the collaboration branch into master again.

Suppose I find a bug in some class (and yes, I have many small patches in my local clone), do I have to go through this rather lengthy process for each small bug?

JB

-----Original Message-----
From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] 
Sent: 19 April 2011 17:22
To: Jérôme
Cc: Biddiscombe, John A.; paraview-developers at paraview.org
Subject: Re: [Paraview-developers] slowness getting even slower

Just committed a fix for this bug
(http://www.paraview.org/Bug/view.php?id=12107)

commit d4b46307742e184a5577939d6c957b1464a4f692
Author: Utkarsh Ayachit <utkarsh.ayachit at kitware.com>
Date:   Tue Apr 19 11:18:20 2011 -0400

    Fixed BUG #12107. Gui plugins were loaded twice.

    The problem was with the order of initialization of the
pqInterfaceTracker and
    pqPluginManager. The pqInterfaceTracker ended up "re-reading"
plugin interfaces
    that were loaded during initialization of the pqPluginManager. fixed that.

Feel free to give it a try. Thanks for catching this :).

Utkarsh

On Tue, Apr 19, 2011 at 9:49 AM, Utkarsh Ayachit
<utkarsh.ayachit at kitware.com> wrote:
> Thanks for the info guys, I could reproduce this. I will have the
> issue fixed today.
>
> Utkarsh
>
> On Tue, Apr 19, 2011 at 9:37 AM, Jérôme <jerome.velut at gmail.com> wrote:
>> Hi Utkarsch,
>>
>> I also noticed the "double loading" behaviour. In my case, it occurs
>> only when starting ParaView after having set my plugin to be
>> autoloaded. Adding a new plugin does not trigger this problem.
>> Please the PV_PLUGIN_DEBUG output after.
>>
>> HTH
>> Jerome
>>
>> [euHeart at euHeart-z800 Chiron]$ export PV_PLUGIN_DEBUG=1
>> [euHeart at euHeart-z800 Chiron]$ paraview
>> Locate and load distributed plugin list.
>>
>> Loading plugin configuration xml: /usr/local/lib/paraview-3.11/.plugins
>>
>> Trying to locate plugin with name: Moments
>>
>> --- Found /usr/local/lib/paraview-3.11/libMoments.so
>>
>> Trying to locate plugin with name: PrismServerPlugin
>>
>> --- Found /usr/local/lib/paraview-3.11/libPrismServerPlugin.so
>>
>> Trying to locate plugin with name: PrismClientPlugin
>>
>> --- Found /usr/local/lib/paraview-3.11/libPrismClientPlugin.so
>>
>> Trying to locate plugin with name: PacMan
>>
>> --- Found /usr/local/lib/paraview-3.11/libPacMan.so
>>
>> Trying to locate plugin with name: PointSprite_Plugin
>>
>> --- Found /usr/local/lib/paraview-3.11/libPointSprite_Plugin.so
>>
>> Trying to locate plugin with name: pvblot
>>
>> --- Found /usr/local/lib/paraview-3.11/libpvblot.so
>>
>> Trying to locate plugin with name: SierraPlotTools
>>
>> --- Found /usr/local/lib/paraview-3.11/libSierraPlotTools.so
>>
>> Trying to locate plugin with name: SLACTools
>>
>> --- Found /usr/local/lib/paraview-3.11/libSLACTools.so
>>
>> Trying to locate plugin with name: StreamingView
>>
>> --- Found /usr/local/lib/paraview-3.11/libStreamingView.so
>>
>> Trying to locate plugin with name: SurfaceLIC
>>
>> --- Found /usr/local/lib/paraview-3.11/libSurfaceLIC.so
>>
>> Trying to locate plugin with name: H5PartReader
>>
>> --- Found /usr/local/lib/paraview-3.11/libH5PartReader.so
>>
>> Trying to locate plugin with name: AnalyzeReader
>>
>> --- Found /usr/local/lib/paraview-3.11/libAnalyzeReader.so
>>
>> Trying to locate plugin with name: AnalyzeWriter
>>
>> --- Found /usr/local/lib/paraview-3.11/libAnalyzeWriter.so
>>
>> Trying to locate plugin with name: NIfTIReader
>>
>> --- Found /usr/local/lib/paraview-3.11/libNIfTIReader.so
>>
>> Trying to locate plugin with name: NIfTIWriter
>>
>> --- Found /usr/local/lib/paraview-3.11/libNIfTIWriter.so
>>
>> Loading Plugins from standard PLUGIN_PATHS
>> /usr/local/lib/paraview-3.11/plugins
>> Loading plugins in Path: /usr/local/lib/paraview-3.11/plugins
>> Invalid directory: /usr/local/lib/paraview-3.11/plugins
>> Trying to locate plugin with name: Moments
>>
>> --- Found /usr/local/lib/paraview-3.11/libMoments.so
>>
>> Trying to locate plugin with name: PrismServerPlugin
>>
>> --- Found /usr/local/lib/paraview-3.11/libPrismServerPlugin.so
>>
>> Trying to locate plugin with name: PrismClientPlugin
>>
>> --- Found /usr/local/lib/paraview-3.11/libPrismClientPlugin.so
>>
>> Trying to locate plugin with name: PacMan
>>
>> --- Found /usr/local/lib/paraview-3.11/libPacMan.so
>>
>> Trying to locate plugin with name: PointSprite_Plugin
>>
>> --- Found /usr/local/lib/paraview-3.11/libPointSprite_Plugin.so
>>
>> Trying to locate plugin with name: pvblot
>>
>> --- Found /usr/local/lib/paraview-3.11/libpvblot.so
>>
>> Trying to locate plugin with name: SierraPlotTools
>>
>> --- Found /usr/local/lib/paraview-3.11/libSierraPlotTools.so
>>
>> Trying to locate plugin with name: SLACTools
>>
>> --- Found /usr/local/lib/paraview-3.11/libSLACTools.so
>>
>> Trying to locate plugin with name: StreamingView
>>
>> --- Found /usr/local/lib/paraview-3.11/libStreamingView.so
>>
>> Trying to locate plugin with name: SurfaceLIC
>>
>> --- Found /usr/local/lib/paraview-3.11/libSurfaceLIC.so
>>
>> Trying to locate plugin with name: H5PartReader
>>
>> --- Found /usr/local/lib/paraview-3.11/libH5PartReader.so
>>
>> Trying to locate plugin with name: AnalyzeReader
>>
>> --- Found /usr/local/lib/paraview-3.11/libAnalyzeReader.so
>>
>> Trying to locate plugin with name: AnalyzeWriter
>>
>> --- Found /usr/local/lib/paraview-3.11/libAnalyzeWriter.so
>>
>> Trying to locate plugin with name: NIfTIReader
>>
>> --- Found /usr/local/lib/paraview-3.11/libNIfTIReader.so
>>
>> Trying to locate plugin with name: NIfTIWriter
>>
>> --- Found /usr/local/lib/paraview-3.11/libNIfTIWriter.so
>>
>> Trying to locate plugin with name: Chiron
>>
>> --- Found /home/euHeart/Softwares/Chiron/bin/libChiron.so
>>
>>
>> ***************************************************
>> Attempting to load /home/euHeart/Softwares/Chiron/bin/libChiron.so
>> Loaded shared library successfully. Now trying to validate that it's a
>> ParaView plugin.
>> Plugin's signature: paraviewplugin|GNU|3.11
>> Plugin signature verification successful. This is definitely a
>> ParaView plugin compiled with correct compiler for correct ParaView
>> version.
>> Updating Shared Library Paths:
>> /usr/local/lib/paraview-3.11:/usr/local::/home/euHeart/Softwares/Gimias-1.1.0/thirdParty/Release/lib:/usr/local/lib/paraview-3.9:/home/euHeart/Softwares/Paraview/VTK/Wrapping/Python:/usr/local/lib/vmtk:/home/euHeart/Softwares/Gimias-1.1.0/thirdParty/Release/lib:/usr/local/lib/paraview-3.11:/home/euHeart/Softwares/Paraview/VTK/Wrapping/Python:/usr/local/lib/vmtk:/home/euHeart/Softwares/Chiron/bin
>> Plugin instance located successfully. Now loading components from the
>> plugin instance based on the interfaces it implements.
>> ----------------------------------------------------------------
>> Plugin Information:
>>  Name        : Chiron
>>  Version     : 1.0
>>  ReqOnServer : 1
>>  ReqOnClient : 1
>>  ReqPlugins  :
>>  ServerManager Plugin : Yes
>>  Python Plugin : No
>>
>>
>>
>>
>> 2011/4/19 Utkarsh Ayachit <utkarsh.ayachit at kitware.com>:
>>> John,
>>>
>>>> I notice also that all plugins are actually loaded twice. I'm trying to debug that now because I get two of every dock window/panel etc.
>>>
>>> Try this, set PV_PLUGIN_DEBUG environment variable to 1 and then run
>>> ParaView. Then post the log that was dumped out. I may have missed
>>> something about the plugin loading because of which they are getting
>>> loaded twice.
>>>
>>> Utkarsh
>>> _______________________________________________
>>> Paraview-developers mailing list
>>> Paraview-developers at paraview.org
>>> http://public.kitware.com/mailman/listinfo/paraview-developers
>>>
>>
>