View Issue Details [ Jump to Notes ] [ Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0014561VTK(No Category)public2014-02-07 16:192015-08-05 07:34
Reportercrupp 
Assigned ToT.J. Corona 
PrioritynormalSeverityminorReproducibilityhave not tried
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Version6.0.0 
Target VersionFixed in Version6.3.0 
Summary0014561: vtkScalarBarActor layout is incorrect when title is null or empty
DescriptionIn VTK 6.1.0, if the title of a vtkScalarBarActor is not set before first render then the scalar bar length will sometimes be wrong.

In vtkScalarBarActor::ComputeScalarBarLength(), the computation of this->P->ScalarBarBox.Size[1] references this->P->TitleBox.Size[1]. If Title is null or zero length (per vtkScalarBarActor::LayoutTitle()), then this->P->TitleBox.Size[1] does not get initialized and therefore can have arbitrary value. As a result, the size of the scalar bar is also arbitrary.

The current reasonable workaround is to set the title to " ".

Similar behavior may occur due to uninitialized layout sizes for other scalar bar properties, although this has not been verified.
TagsNo tags attached.
ProjectTBD
Typeincorrect functionality
Attached Files

 Relationships

  Notes
(0034313)
dabearca (reporter)
2015-03-17 14:13
edited on: 2015-03-17 14:56

 Setting the title to " " produces strange memory problems where on Update the application memory can grow to up to 1GB (70MB baseline). It usually shrinks down to the baseline but it slows down the application tremendously. [tested under Windows 7 64bit] Setting the title to some string and setting the opacity to 0 seems to work as a workaround.

Additional to the description above, this problem also occurs in the source packages for 6.0 and 6.2.

This memory problem seems to be with vtkTextActor::SetConstrainedFontSize. The 2nd while loop seems to grow the font to huge numbers.
(0034867)
Tim Hutton (reporter)
2015-08-01 16:50

 Confirmed that using vtkScalarBarActor without a title is an issue in 6.0 and 6.2. And the suggested workaround works.
(0034887)
T.J. Corona (developer)
2015-08-05 07:34

 This issue was resolved by Julien Jomier in commit a0a1fda1df6a851e8a277ccf6a4d3b64244513e5 on July 15, 2015.

 Issue History
Date Modified Username Field Change
2014-02-07 16:19 crupp New Issue
2015-03-17 14:13 dabearca Note Added: 0034313
2015-03-17 14:55 dabearca Note Added: 0034314
2015-03-17 14:55 dabearca Note Deleted: 0034314
2015-03-17 14:56 dabearca Note Edited: 0034313
2015-08-01 16:50 Tim Hutton Note Added: 0034867
2015-08-05 07:34 T.J. Corona Note Added: 0034887
2015-08-05 07:34 T.J. Corona Status backlog => closed
2015-08-05 07:34 T.J. Corona Assigned To => T.J. Corona
2015-08-05 07:34 T.J. Corona Resolution open => fixed
2015-08-05 07:34 T.J. Corona Fixed in Version => 6.3.0

Copyright © 2000 - 2018 MantisBT Team