Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tunnelblick 3.0b9 crashes when "Details" window is resized #13

Closed
GoogleCodeExporter opened this issue Jul 13, 2015 · 1 comment
Closed

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
1. Install Tunnelblick 3.0b9
2. Define two VPN's, each to a different OpenVPN server.
3. Launch Tunnelblick and open both VPN's.
4. Open the Tunnelblick "Details..." window and resize it.  Tunnelblick crashes.

What is the expected output? What do you see instead?

I expect the Details window to resize and properly display the log contents for 
each of the VPN connections.

Instead, Tunnelblick crashes.

8/11/08 9:47:25 AM Tunnelblick[53030] *** -[NSConcreteTextStorage 
attribute:atIndex:longestEffectiveRange:inRange:]: Range or index out of bounds 
8/11/08 9:47:26 AM Tunnelblick[53030] *** -[NSConcreteTextStorage 
attribute:atIndex:longestEffectiveRange:inRange:]: Range or index out of bounds 
8/11/08 9:47:28 AM Tunnelblick[53030] *** -[NSConcreteTextStorage 
attribute:atIndex:longestEffectiveRange:inRange:]: Range or index out of bounds 
8/11/08 9:47:31 AM Tunnelblick[53030] <NSATSTypesetter: 0x15622c70>: Exception 
*** NSRunStorage (0x15624150), _replaceElements(): replaced range {76, 2570} 
extends 
beyond current run storage size 2645. raised during typesetting layout manager 
<NSLayoutManager: 0x15693290>
    1 containers, text backing has 2645 characters
    selected character range {3143, 4294964229} affinity: upstream granularity: character
    marked character range {2645, 0}
    Currently holding 2645 glyphs.
    Glyph tree contents:  2645 characters, 2645 glyphs, 1 nodes, 32 node bytes, 4096 storage bytes, 4128 total bytes, 1.56 bytes per character, 1.56 bytes per glyph
    Layout tree contents:  2645 characters, 2645 glyphs, 76 laid glyphs, 1 laid line fragments, 3 nodes, 96 node bytes, 792 storage bytes, 888 total bytes, 0.34 bytes per 
character, 0.34 bytes per glyph, 76.00 laid glyphs per laid line fragment, 
888.00 bytes per laid line fragment
, glyph range {76 2569}. Ignoring... 
8/11/08 9:47:31 AM Tunnelblick[53030] <NSATSTypesetter: 0x15622c70>: Exception 
*** NSRunStorage (0x15624150), _replaceElements(): replaced range {76, 2570} 
extends 
beyond current run storage size 2645. raised during typesetting layout manager 
<NSLayoutManager: 0x15693290>
    1 containers, text backing has 2645 characters
    selected character range {3143, 4294964229} affinity: upstream granularity: character
    marked character range {2645, 0}
    Currently holding 2645 glyphs.
    Glyph tree contents:  2645 characters, 2645 glyphs, 1 nodes, 32 node bytes, 4096 storage bytes, 4128 total bytes, 1.56 bytes per character, 1.56 bytes per glyph
    Layout tree contents:  2645 characters, 2645 glyphs, 76 laid glyphs, 1 laid line fragments, 3 nodes, 96 node bytes, 792 storage bytes, 888 total bytes, 0.34 bytes per 
character, 0.34 bytes per glyph, 76.00 laid glyphs per laid line fragment, 
888.00 bytes per laid line fragment
, glyph range {76 2569}. Ignoring... 
8/11/08 9:47:38 AM Tunnelblick[53030] *** NSLayoutManager, _getGlyphBuffer(): 
NSZoneMalloc failed! 
8/11/08 9:47:38 AM [0x0-0x807807].com.openvpn.tunnelblick[53030] signal 10 
caught! 
8/11/08 9:47:38 AM [0x0-0x807807].com.openvpn.tunnelblick[53030] Received fatal 
signal. Cleaning up... 

What version of the product are you using? On what operating system?

Tunnelblick 3.0b9 on Mac OS X 10.5.4

Please provide any additional information below.

Tunnelblick has several related bugs which are apparent when you use it to open 
two VPN's simultaneously.

Original issue reported on code.google.com by jeff.ste...@gmail.com on 11 Aug 2008 at 4:56

@GoogleCodeExporter
Copy link
Author

This is fixed. Not sure when, 3.0b10, maybe. Doesn't happen on 3.0b16.

Original comment by jkbull...@gmail.com on 30 Aug 2009 at 12:01

  • Changed state: Fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant