View Issue Details

IDProjectCategoryView StatusLast Update
0004497Slicer4Core: Renderingpublic2018-03-22 01:49
ReporterDavideAssigned Tojohan.andruejol 
PriorityhighSeverityblockReproducibilityalways
Status assignedResolutionopen 
PlatformLinuxOSUbuntuOS Version17.10
Product VersionSlicer 4.9.0 
Target VersionSlicer 4.9.0Fixed in Version 
Summary0004497: Rendering block/freeze the GUI if the startup layout has not both a 3D and 2D view LINUX QT5/VTK9
Description

the GUI behave oddly (button not working anymore) or black windows when trying to set the volume in the volume rendering module if the startup layout has not both a 3D and 2D views.

The bug seems occur when the this method is called: volumeRenderingWidget->setMRMLVolumeNode

Steps To Reproduce

A) Black window for 2D view
1) Start 3DSlicer
2) choose Red only layout
3) close and reopen 3DSlicer
4) navigate to volume rendering module
5) load the dataset MRhead
6) set the new volume
(or 4) load to sample data module 5) load the dataset MRhead 6) navigate to volume rendering module)

7) got black window

B) Odd behaviors with 3D view:
1) Start 3DSlicer
2) choose 3D only layout
3) close and reopen 3DSlicer
4) navigate to volume rendering module
5) load the dataset MRhead
6) try the new volume
(or 4) load to sample data module 5) load the dataset MRhead 6) try to navigate to volume rendering module)

7) interface not working anymore

no error or warning is reported by Slicer.

TagsNo tags attached.

Activities

Davide

Davide

2018-01-19 09:04

developer   ~0015487

@jcfr is this issue connected with some initialization of the renders in anyway?

If I start 3DSlicer with the '3D only. layout, then I change to 'Conventional', then back to '3D only', I have no issue.

Davide

Davide

2018-03-12 04:29

developer   ~0015547

Update: with current Slicer master (https://github.com/Slicer/Slicer/commit/807688a9b2ee791a47d3cf9226d8d34dcfb151db) I can not reproduce anymore (B) (starting Slicer 3D view only). (A) (starting Slicer with red view only) is still there.

jcfr

jcfr

2018-03-22 01:49

administrator   ~0015597

@lassoan Is it something you could look into ?

Issue History

Date Modified Username Field Change
2018-01-19 08:59 Davide New Issue
2018-01-19 08:59 Davide Status new => assigned
2018-01-19 08:59 Davide Assigned To => jcfr
2018-01-19 09:04 Davide Note Added: 0015487
2018-02-07 02:07 jcfr Assigned To jcfr => johan.andruejol
2018-03-12 04:29 Davide Note Added: 0015547
2018-03-22 01:49 jcfr Note Added: 0015597