MantisBT - ParaView |
| View Issue Details |
|
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0013403 | ParaView | (No Category) | public | 2012-08-27 23:55 | 2012-10-29 17:04 |
|
| Reporter | Alan Scott | |
| Assigned To | Utkarsh Ayachit | |
| Priority | high | Severity | minor | Reproducibility | have not tried |
| Status | closed | Resolution | fixed | |
| Platform | | OS | | OS Version | |
| Product Version | git-master | |
| Target Version | | Fixed in Version | 3.98.0 | |
| Project | Sandia |
| Topic Name | 13403_cube_axis_in_parallel |
| Type | crash |
|
| Summary | 0013403: Crash with Whipple Shield and Cube Axis |
| Description | There is a wicked crash with Whipple Shield. Here is how I replicated it.
* 8 remote servers, linux client, master.
* whipple_shield.exo.32.[0-31]. All vars on, Apply. (Ask Utkarsh for this one, or me.)
* Cell to Point filter. Apply.
* Turn on Cube axis. Notice how this shows incorrectly, with lots of cube axes all over the place. I suspect this is a clue.
* Turn off cube axis.
* Clip. Type: Scalar. Scalars: VolFrac2. 0.5. Apply.
* Clip. Y Normal. Apply.
Crash.
Probably a client side crash. The server just died saying that the socket had closed, where the client said Qt caught an exception.
|
| Steps To Reproduce | |
| Additional Information | |
| Tags | No tags attached. |
| Relationships | |
| Attached Files | |
|
| Issue History |
| Date Modified | Username | Field | Change |
| 2012-08-27 23:55 | Alan Scott | New Issue | |
| 2012-08-28 11:26 | Utkarsh Ayachit | Note Added: 0029084 | |
| 2012-08-29 09:43 | Utkarsh Ayachit | Note Added: 0029086 | |
| 2012-08-30 15:20 | Utkarsh Ayachit | Topic Name | => 13403_cube_axis_in_parallel |
| 2012-08-30 15:20 | Utkarsh Ayachit | Note Added: 0029093 | |
| 2012-08-30 15:20 | Utkarsh Ayachit | Status | backlog => gatekeeper review |
| 2012-08-30 15:20 | Utkarsh Ayachit | Fixed in Version | => git-next |
| 2012-08-30 15:20 | Utkarsh Ayachit | Resolution | open => fixed |
| 2012-08-30 15:20 | Utkarsh Ayachit | Assigned To | => Utkarsh Ayachit |
| 2012-09-03 13:30 | Utkarsh Ayachit | Status | gatekeeper review => customer review |
| 2012-09-03 13:30 | Utkarsh Ayachit | Note Added: 0029115 | |
| 2012-09-19 21:13 | Alan Scott | Note Added: 0029226 | |
| 2012-09-19 21:13 | Alan Scott | Status | customer review => closed |
| 2012-10-06 07:03 | Utkarsh Ayachit | Fixed in Version | git-next => git-master |
| 2012-10-29 17:04 | Utkarsh Ayachit | Fixed in Version | git-master => 3.98.0 |
|
Notes |
|
|
(0029084)
|
|
Utkarsh Ayachit
|
|
2012-08-28 11:26
|
|
|
Can be reproduced with just a sphere source. Need to run in parallel with remote rendering enabled. |
|
|
|
(0029086)
|
|
Utkarsh Ayachit
|
|
2012-08-29 09:43
|
|
commit 0ab305d121a52cfd3d2511bfd35489256d4c667a
Author: Utkarsh Ayachit <utkarsh.ayachit@kitware.com>
Date: Tue Aug 28 11:36:32 2012 -0400
BUG 0013403: Ensure cube-axes gets reduced bounds on all processes.
Cube-axes was using only local bounds when doing server-side rendering. That was
causing the problem with multiple axes being shown when in parallel. This fixes
that issue. |
|
|
|
(0029093)
|
|
Utkarsh Ayachit
|
|
2012-08-30 15:20
|
|
commit adc5455f2adea2de34e617b977afc0bf0c23bbf3
Author: Utkarsh Ayachit <utkarsh.ayachit@kitware.com>
Date: Thu Aug 30 15:18:00 2012 -0400
BUG 0013403: Fixed invalid bounds being passed in parallel.
When running in parallel with some processes having empty data, the
vtkCubeAxesRepresentation ended up delivering invalid outline geometry to all
processes. This was causing segfaults due to invalid bounds. Fixed that by
ensuring that vtkCubeAxesRepresentation delivery polydata with valid bounds or
simply empty polydata correctly. |
|
|
|
(0029115)
|
|
Utkarsh Ayachit
|
|
2012-09-03 13:30
|
|
|
merged into master, if applicable. |
|
|
|
(0029226)
|
|
Alan Scott
|
|
2012-09-19 21:13
|
|
|
Tested remote server, Linux, master. |
|