Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
ParaView
ParaView
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1,666
    • Issues 1,666
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 62
    • Merge Requests 62
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ParaView
  • ParaViewParaView
  • Issues
  • #15080

Closed
Open
Created Oct 26, 2014 by Kitware Robot@kwrobotOwner

Timer Log: not initialized with buffer size on startup

This issue was created automatically from an original Mantis Issue. Further discussion may take place here.


  • Start paraview
  • Tools, Timer Log : change buffer length to 9000. And Time Threshold to "Show All". Interact with the view, and hit "Refresh". You'll see the timer log update as expected.
  • Restart ParaView and do the interactions without opening the "Timer Log" dialog. Now open the timer log dialog -- the timer log is clipped!

Looks like the buffer lenght threshold was not set until the dialog is opened.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None