Skip to content

iTerm2 hanging in -[LineBlock getNumLinesWithWrapWidth:]

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

  • iTerm2 version: Build 3.1.6
  • OS version: 10.13.4 (17E199)

Preferences: com.googlecode.iterm2.plist Sample: Sample_of_iTerm2.txt Problem Report: iTerm2_Problem_Report.txt

What happened:

iTerm2 appears to be hanging indefinitely (spinning beach ball) trying to resize itself:

  10  -[PseudoTerminal windowDidResize:] + 1037 (iTerm2 + 2432769) [0x105e64f01]
  10  -[PseudoTerminal fitTabsToWindow] + 270 (iTerm2 + 2510586) [0x105e77efa]
  10  -[PseudoTerminal fitTabToWindow:] + 237 (iTerm2 + 2504175) [0x105e765ef]
  10  -[PTYTab setSize:] + 234 (iTerm2 + 617532) [0x105ca9c3c]
  10  -[NSSplitView setFrameSize:] + 147 (AppKit + 691091) [0x7fff45d50b93]
  10  -[NSView setFrameSize:] + 1672 (AppKit + 411382) [0x7fff45d0c6f6]
  10  -[NSSplitView resizeSubviewsWithOldSize:] + 352 (AppKit + 691517) [0x7fff45d50d3d]
  10  -[NSNotificationCenter postNotificationName:object:userInfo:] + 66 (Foundation + 26823) [0x7fff4a8238c7]
  10  _CFXNotificationPost + 599 (CoreFoundation + 358919) [0x7fff48720a07]
  10  -[_CFXNotificationRegistrar find:object:observer:enumerator:] + 1664 (CoreFoundation + 362704) [0x7fff487218d0]
  10  ___CFXNotificationPost_block_invoke + 225 (CoreFoundation + 633649) [0x7fff48763b31]
  10  _CFXRegistrationPost + 458 (CoreFoundation + 634362) [0x7fff48763dfa]
  10  __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 12 (CoreFoundation + 634668) [0x7fff48763f2c]
  10  -[PTYTab splitViewDidResizeSubviews:] + 367 (iTerm2 + 682319) [0x105cb994f]
  10  -[PTYTab _splitViewDidResizeSubviews:] + 848 (iTerm2 + 683224) [0x105cb9cd8]
  10  -[PTYTab resizeSession:toSize:] + 354 (iTerm2 + 623477) [0x105cab375]
  10  -[PTYSession setSize:] + 1039 (iTerm2 + 1248291) [0x105d43c23]
  10  -[VT100Screen setSize:] + 5335 (iTerm2 + 2194613) [0x105e2acb5]
  10  RawNumLines + 153 (iTerm2 + 1633300) [0x105da1c14]
  7  -[LineBlock getNumLinesWithWrapWidth:] + 600 (iTerm2 + 1061300) [0x105d161b4] (running)

Detailed steps to reproduce the problem:

  1. I suspect the first step is to resize the display (e.g. by plugging into an external monitor)
  2. ???