1. 01 Aug, 2020 12 commits
  2. 31 Jul, 2020 5 commits
  3. 30 Jul, 2020 18 commits
  4. 29 Jul, 2020 5 commits
    • Ell's avatar
      d11cbbbb
    • Ell's avatar
      tools: add performance-log-progressive-coalesce.py; use in performance-log-viewer · 76f9e5fe
      Ell authored
      Add a new performance-log-progressive-coalesce.py tool, which
      coalesces partial address maps in progressive performacne logs into
      a single global address map, suitable for processing by the rest of
      the tools.
      
      Use the new tool as part of the pipeline in performance-log-viewer.
      76f9e5fe
    • Ell's avatar
      tools: add performance-log-close-tags.py, use in performance-log-viewer · e5fe1ef1
      Ell authored
      Add a new performance-log-close-tags.py tool, which closes unclosed
      tags in incomplete performance logs, allowing the rest of the
      perofmance-log tools to process them.  This is necessary for
      unfinished progressive logs.
      
      Use the new tool as part of the pipeline in performance-log-viewer.
      e5fe1ef1
    • Ell's avatar
      app: add progressive performance logs · 146c2343
      Ell authored
      Add an option to record progressive performance logs.  Progressive
      logs contain complete information after each recorded sample, by
      writing partial address maps at each sample, containing all new
      addresses introduced by the sample.  Furthermore, when recording a
      progressive log, the output stream is flushed after each sample.
      
      This allows recording complete logs even in cases where they can't
      be properly terminated, such as when GIMP crashes or freezes in the
      middle of the log.
      
      Progressive logs are disabled by default, since they potentially
      increase the sampling cost.  They can be enabled through a toggle
      in the log file-dialog, or through the
      GIMP_PERFORMANCE_LOG_PROGRESSIVE environment varaible.
      146c2343
    • Ell's avatar
      app: allow controlling performance-log parameters through the UI · 126002c5
      Ell authored
      When recording a performance log, allow setting the log parametrs
      through the file dialog.  Currently, this includes the sample
      frequency, and the option to include backtraces.
      
      These options are still controllable through the
      GIMP_PERFORMANCE_LOG_SAMPLE_FREQUENCY and
      GIMP_PERFORMANCE_LOG_BACKTRACE environment variables.  When set,
      the variables override the values entered through the UI.
      126002c5