MantisBT - ParaView
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0011592ParaViewBugpublic2010-12-09 11:112011-01-20 22:09
ReporterNicolas Niclausse 
Assigned ToUtkarsh Ayachit 
PrioritynormalSeveritycrashReproducibilityalways
StatusclosedResolutionfixed 
PlatformOSLinuxOS Versionfedora-12
Product Version3.8.1 
Target VersionFixed in Version3.10 
Project
Topic Name
Type
Summary0011592: pvrenderserver segfault with more than 2 servers
DescriptionI have the following setup: 1 node with 12 cores and 4 GPU (tesla C2050). I
want to start 8 dataserver and 4 renderserver on this host (paraview 3.8.1,
fedora-12 x86_64, openmpi 1.4.3, nvidia drivers)

It works if i start only 2 renderserver; however with 3 or 4 renderservers,
it fails (segfault)

Logs:

Listen on port: 22221
RenderServer: Waiting for client...
Client connected.
Connect: id :1 host: localhost Port:52065
Connect: id :2 host: localhost Port:52975
Connect: id :3 host: localhost Port:29181760
Connect: id :0 host: localhost Port:53883

a port number > 65535 is a bug
Steps To Reproducethe renderserver segfault as soon as the client tries to connect to the servers.
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2010-12-09 11:11Nicolas NiclausseNew Issue
2011-01-19 11:20Utkarsh AyachitNote Added: 0024918
2011-01-19 11:20Utkarsh AyachitStatusbacklog => @80@
2011-01-19 11:20Utkarsh AyachitFixed in Version => 3.10
2011-01-19 11:20Utkarsh AyachitResolutionopen => fixed
2011-01-19 11:20Utkarsh AyachitAssigned To => Utkarsh Ayachit
2011-01-20 22:09Alan ScottNote Added: 0024982
2011-01-20 22:09Alan ScottStatus@80@ => closed

Notes
(0024918)
Utkarsh Ayachit   
2011-01-19 11:20   
commit d3f7da173de4186dca8e6a0409145a75f210e5c5
Author: Utkarsh Ayachit <utkarsh.ayachit@kitware.com>
Date: Wed Jan 19 11:16:19 2011 -0500

    Fixed BUG 0011592. Information was added up incorrectly.
    
    This was resulting in information from child processes being lost and hence we
    ended up with invalid port numbers when number of processes is > 2. This bug
    must have surfaced when we switched to using the "tree" for gather information.
(0024982)
Alan Scott   
2011-01-20 22:09   
Trusting Utkarsh's fix. If this is still a problem, please reopen.