Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
  • Sign in / Register
iterm2
iterm2
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 2,242
    • Issues 2,242
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Requirements
    • Requirements
    • List
  • Security & Compliance
    • Security & Compliance
    • Dependency List
    • License Compliance
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • George Nachman
  • iterm2iterm2
  • Issues
  • #4976

Closed
Open
Opened Jul 21, 2016 by Farruco Sanjurjo@madtrick

Performance issues with Tmux on nightly iTerm2-3_0_20160720-nightly

Thanks for filing an issue! Please answer the questions below so I can help you.

  • iTerm2 version: Build 3.0.20160720-nightly
  • OS version: 10.11.3
  • Attach ~/Library/Preferences/com.googlecode.iterm2.plist here (drag-drop from finder into this window) (I'm executing the nightly build directly from the Downloads folder so I don't know if the ~/Library/Preferences/com.googlecode.iterm2.plist belongs to the nightly build or to the other version I have installed. Please advise)
  • Attach a debug log, if possible. Instructions at https://iterm2.com/debuglog
  • Are you reporting a performance issue or a hang? Yes. Sample Sample_of_iTerm2.txt

Detailed steps to reproduce the problem:

  1. Launch iterm2
  2. Do a git log (git log og --graph --pretty=format:'%Cred%h%Creset - %C(bold blue)%an%Creset %Cgreen(%cr) %C(yellow)%d%Creset %s ' --abbrev-commit --date=relative)

What happened: The output lags as if tmux/iterm2 couldn't keep with the log. Also the CPU usage for iterm2 spikes close to 50%

What should have happened: The output should be smooth as in the stable version of iterm2 Build 3.0.4

Assignee
Assign to
Feature Complete 3.1
Milestone
Feature Complete 3.1 (Past due)
Assign milestone
Time tracking
None
Due date
None
Reference: gnachman/iterm2#4976