View Issue Details [ Jump to Notes ] | [ Print ] | ||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||
0004777 | ParaView | (No Category) | public | 2007-04-03 14:27 | 2007-04-16 13:30 | ||||
Reporter | Ken Moreland | ||||||||
Assigned To | Utkarsh Ayachit | ||||||||
Priority | high | Severity | major | Reproducibility | always | ||||
Status | closed | Resolution | fixed | ||||||
Platform | OS | OS Version | |||||||
Product Version | |||||||||
Target Version | Fixed in Version | ||||||||
Summary | 0004777: Histogram filter deadlocks on parallel server | ||||||||
Description | When you apply a probe filter when connected to a parallel server, it locks up PV. To replicate, simply do the following. 1. Connect to a server with at least 2 processes. 2. Create the Wavelet source. 3. Apply the Probe filter withe the default values. Once you hit apply on the probe filter, the GUI becomes unresponsive. It never comes back. | ||||||||
Tags | No tags attached. | ||||||||
Project | |||||||||
Topic Name | |||||||||
Type | |||||||||
Attached Files | |||||||||
Relationships | |
Relationships |
Notes | |
(0007125) Ken Moreland (manager) 2007-04-03 20:16 |
I just ran into the same problem with the histogram filter. |
(0007131) Utkarsh Ayachit (administrator) 2007-04-04 11:49 |
Reduction filter was executing only on the 0th node since the output piece information was incorrect. Fixed that. /cvsroot/ParaView3/ParaView3/Servers/Filters/vtkReductionFilter.cxx,v <-- vtkReductionFilter.cxx new revision: 1.13; previous revision: 1.12 |
(0007190) Ken Moreland (manager) 2007-04-09 11:10 |
Did this issue get fixed and then unfixed? I just got around to trying it now, and I'm still getting the same deadlock. |
(0007196) Utkarsh Ayachit (administrator) 2007-04-09 14:43 |
Yup, this was "unfixed". It has been fixed, again. Number of partitions was getting set incorrectly on the client side update suppressor. This bug was exposed by recent changes. /cvsroot/ParaView3/ParaView3/Qt/Components/pqExtractSelectionPanel.cxx,v <-- pqExtractSelectionPanel.cxx new revision: 1.9; previous revision: 1.8 /cvsroot/ParaView3/ParaView3/Qt/Core/pqPipelineSource.cxx,v <-- pqPipelineSource.cxx new revision: 1.16; previous revision: 1.15 /cvsroot/ParaView3/ParaView3/Servers/Common/vtkPVProgressHandler.cxx,v <-- vtkPVProgressHandler.cxx new revision: 1.6; previous revision: 1.5 /cvsroot/ParaView3/ParaView3/Servers/Common/vtkProcessModule.cxx,v <-- vtkProcessModule.cxx new revision: 1.67; previous revision: 1.66 /cvsroot/ParaView3/ParaView3/Servers/Common/vtkProcessModule.h,v <-- vtkProcessModule.h new revision: 1.54; previous revision: 1.53 /cvsroot/ParaView3/ParaView3/Servers/ServerManager/vtkSMCompositeDisplayProxy.cxx,v <-- vtkSMCompositeDisplayProxy.cxx new revision: 1.32; previous revision: 1.31 /cvsroot/ParaView3/ParaView3/Servers/ServerManager/vtkSMDataObjectDisplayProxy.cxx,v <-- vtkSMDataObjectDisplayProxy.cxx new revision: 1.39; previous revision: 1.38 /cvsroot/ParaView3/ParaView3/Servers/ServerManager/vtkSMGenericViewDisplayProxy.cxx,v <-- vtkSMGenericViewDisplayProxy.cxx new revision: 1.22; previous revision: 1.21 /cvsroot/ParaView3/ParaView3/Servers/ServerManager/vtkSMIceTMultiDisplayProxy.cxx,v <-- vtkSMIceTMultiDisplayProxy.cxx new revision: 1.8; previous revision: 1.7 /cvsroot/ParaView3/ParaView3/Servers/ServerManager/vtkSMLODDisplayProxy.cxx,v <-- vtkSMLODDisplayProxy.cxx new revision: 1.18; previous revision: 1.17 /cvsroot/ParaView3/ParaView3/Servers/ServerManager/vtkSMPWriterProxy.cxx,v <-- vtkSMPWriterProxy.cxx new revision: 1.3; previous revision: 1.2 /cvsroot/ParaView3/ParaView3/Servers/ServerManager/vtkSMPointLabelDisplayProxy.cxx,v <-- vtkSMPointLabelDisplayProxy.cxx new revision: 1.20; previous revision: 1.19 /cvsroot/ParaView3/ParaView3/Servers/ServerManager/vtkSMTextDisplayProxy.cxx,v <-- vtkSMTextDisplayProxy.cxx new revision: 1.3; previous revision: 1.2 |
(0007213) Ken Moreland (manager) 2007-04-10 12:00 |
The probe filter now seems to work fine, but the histogram filter is freezing now. It deadlocks when I do the following: 1. Connect to a server with 2 or more processes. 2. Load disk_out_ref. 3. Run the histogram filter. The deadlock does not occur when I use the wavelet source. Maybe it has to do with the exodus reader only outputting data on processes 0. |
(0007227) Utkarsh Ayachit (administrator) 2007-04-10 14:45 |
Berk said he'll look into it. |
(0007239) Berk Geveci (administrator) 2007-04-11 10:33 |
Histogram filter does not work well in parallel: 1. it deadlocks 2. it does not produce the right result vtkPExtractHistogram should change to: 1. Compute the array range in parallel to determine bounds - ignore empty datasets 2. vtkExtractHistogram should use the given bounds and produce 0 if the array does not exist (no error!) |
(0007252) Utkarsh Ayachit (administrator) 2007-04-12 08:56 |
Fixed as per recommendations. /cvsroot/ParaView3/ParaView3/Servers/Filters/vtkExtractHistogram.cxx,v <-- vtkExtractHistogram.cxx new revision: 1.17; previous revision: 1.16 /cvsroot/ParaView3/ParaView3/Servers/Filters/vtkExtractHistogram.h,v <-- vtkExtractHistogram.h new revision: 1.6; previous revision: 1.5 /cvsroot/ParaView3/ParaView3/Servers/Filters/vtkPExtractHistogram.cxx,v <-- vtkPExtractHistogram.cxx new revision: 1.2; previous revision: 1.1 /cvsroot/ParaView3/ParaView3/Servers/Filters/vtkPExtractHistogram.h,v <-- vtkPExtractHistogram.h new revision: 1.2; previous revision: 1.1 Fixed build on non-MPI builds." Servers/Filters/vtkPExtractHistogram.cxx /cvsroot/ParaView3/ParaView3/Servers/Filters/vtkPExtractHistogram.cxx,v <-- vtkPExtractHistogram.cxx new revision: 1.3; previous revision: 1.2 |
Notes |
Issue History | |||
Date Modified | Username | Field | Change |
2011-06-16 13:10 | Zack Galbreath | Category | => (No Category) |
Issue History |
Copyright © 2000 - 2018 MantisBT Team |