On start-up of a freshly downloaded preview release (no extensions, no extra modules added, no actions taken within Slicer after opening), I get a number of errors saying “setViewLabel should be called before setViewNode”. Here is the full log file:
[DEBUG][Qt] 01.06.2021 17:49:20 (unknown:0) - Session start time …: 2021-06-01 17:49:20
[DEBUG][Qt] 01.06.2021 17:49:20 (unknown:0) - Slicer version …: 4.13.0-2021-05-29 (revision 29934 / 7cce89a) win-amd64 - installed release
[DEBUG][Qt] 01.06.2021 17:49:20 (unknown:0) - Operating system …: Windows / Professional / (Build 19041, Code Page 65001) - 64-bit
[DEBUG][Qt] 01.06.2021 17:49:20 (unknown:0) - Memory …: 32499 MB physical, 55027 MB virtual
[DEBUG][Qt] 01.06.2021 17:49:20 (unknown:0) - CPU …: GenuineIntel , 12 cores, 12 logical processors
[DEBUG][Qt] 01.06.2021 17:49:20 (unknown:0) - VTK configuration …: OpenGL2 rendering, TBB threading
[DEBUG][Qt] 01.06.2021 17:49:20 (unknown:0) - Qt configuration …: version 5.15.1, with SSL, requested OpenGL 3.2 (compatibility profile)
[DEBUG][Qt] 01.06.2021 17:49:20 (unknown:0) - Developer mode enabled …: yes
[DEBUG][Qt] 01.06.2021 17:49:20 (unknown:0) - Prefer executable CLI …: yes
[DEBUG][Qt] 01.06.2021 17:49:20 (unknown:0) - Application path …: C:/Users/mikeb/AppData/Local/NA-MIC/Slicer 4.13.0-2021-05-29/bin
[DEBUG][Qt] 01.06.2021 17:49:20 (unknown:0) - Additional module paths …: (none)
[CRITICAL][Qt] 01.06.2021 17:49:24 (unknown:0) - setViewLabel should be called before setViewNode !
[CRITICAL][Qt] 01.06.2021 17:49:24 (unknown:0) - setViewLabel should be called before setViewNode !
[DEBUG][Python] 01.06.2021 17:49:25 [Python] (C:\Users\mikeb\AppData\Local\NA-MIC\Slicer 4.13.0-2021-05-29\lib\Slicer-4.13\qt-scripted-modules\SubjectHierarchyPlugins\AbstractScriptedSubjectHierarchyPlugin.py:36) - Scripted subject hierarchy plugin registered: Annotations
[CRITICAL][Qt] 01.06.2021 17:49:25 (unknown:0) - setViewLabel should be called before setViewNode !
[CRITICAL][Qt] 01.06.2021 17:49:25 (unknown:0) - setViewLabel should be called before setViewNode !
[CRITICAL][Qt] 01.06.2021 17:49:25 (unknown:0) - setViewLabel should be called before setViewNode !
[CRITICAL][Qt] 01.06.2021 17:49:25 (unknown:0) - setViewLabel should be called before setViewNode !
[CRITICAL][Qt] 01.06.2021 17:49:25 (unknown:0) - setViewLabel should be called before setViewNode !
[CRITICAL][Qt] 01.06.2021 17:49:25 (unknown:0) - setViewLabel should be called before setViewNode !
[CRITICAL][Qt] 01.06.2021 17:49:25 (unknown:0) - setViewLabel should be called before setViewNode !
[CRITICAL][Qt] 01.06.2021 17:49:25 (unknown:0) - setViewLabel should be called before setViewNode !
[CRITICAL][Qt] 01.06.2021 17:49:25 (unknown:0) - setViewLabel should be called before setViewNode !
[DEBUG][Python] 01.06.2021 17:49:26 [Python] (C:\Users\mikeb\AppData\Local\NA-MIC\Slicer 4.13.0-2021-05-29\lib\Slicer-4.13\qt-scripted-modules\SubjectHierarchyPlugins\AbstractScriptedSubjectHierarchyPlugin.py:36) - Scripted subject hierarchy plugin registered: SegmentEditor
[DEBUG][Python] 01.06.2021 17:49:26 [Python] (C:\Users\mikeb\AppData\Local\NA-MIC\Slicer 4.13.0-2021-05-29\lib\Slicer-4.13\qt-scripted-modules\SubjectHierarchyPlugins\AbstractScriptedSubjectHierarchyPlugin.py:36) - Scripted subject hierarchy plugin registered: SegmentStatistics
[CRITICAL][Qt] 01.06.2021 17:49:26 (unknown:0) - setViewLabel should be called before setViewNode !
[CRITICAL][Qt] 01.06.2021 17:49:26 (unknown:0) - setViewLabel should be called before setViewNode !
[CRITICAL][Qt] 01.06.2021 17:49:26 (unknown:0) - setViewLabel should be called before setViewNode !
[DEBUG][Qt] 01.06.2021 17:49:26 (unknown:0) - Switch to module: “Welcome”
[CRITICAL][Qt] 01.06.2021 17:49:27 (unknown:0) - setViewLabel should be called before setViewNode !
[CRITICAL][Qt] 01.06.2021 17:49:27 (unknown:0) - setViewLabel should be called before setViewNode !
I get these errors on the stable release, but had assumed they had probably been fixed in the preview. I just updated to the preview and still see them. They don’t seem to have any effect in the stable I have been using for months, but they also seem like they should be easy to fix, for someone who knows where to look.