Crash in (NSRange)_effectiveRangeOfOutermostTextBlocksInRange:(NSRange)range #606

brovador · 2013-09-19T09:33:57Z

Versions tested: pod 'DTCoreText', '~>1.6.6' and pod 'DTCoreText', :head

We are rendering text in columns inside a collection view. When we build the cell with the column layout (sometimes, with more frequency on simulator), we receive a crash in DTCoreTextLayoutFrame in the method:

-(NSRange)_effectiveRangeOfOutermostTextBlocksInRange:(NSRange)range

Stacktrace:

In Xcode5, the console shows the following stacktrace:

2013-09-19 10:53:20.970 App[3116:2a8b] +[__NSCFString objectForKey:]: unrecognized selector sent to class 0x3bd933c
2013-09-19 10:53:20.973 App[3116:2a8b] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '+[__NSCFString objectForKey:]: unrecognized selector sent to class 0x3bd933c'
*** First throw call stack:
(
    0   CoreFoundation                      0x03a945e4 __exceptionPreprocess + 180
    1   libobjc.A.dylib                     0x02f508b6 objc_exception_throw + 44
    2   CoreFoundation                      0x03b317a3 +[NSObject(NSObject) doesNotRecognizeSelector:] + 275
    3   CoreFoundation                      0x03a8490b ___forwarding___ + 1019
    4   CoreFoundation                      0x03a844ee _CF_forwarding_prep_0 + 14
    5   Foundation                          0x00cb5119 -[NSConcreteMutableAttributedString attribute:atIndex:effectiveRange:] + 82
    6   App                                 0x000ffc34 -[DTCoreTextLayoutFrame _effectiveRangeOfOutermostTextBlocksInRange:] + 276
    7   App                                 0x001013b7 -[DTCoreTextLayoutFrame _enumerateTextBlocksInRange:usingBlock:] + 103
    8   App                                 0x00101864 -[DTCoreTextLayoutFrame _drawTextBlocksInContext:inRange:] + 228
    9   App                                 0x00103043 -[DTCoreTextLayoutFrame drawInContext:options:] + 2019
    10  App                                 0x000e5dc1 -[DTAttributedTextContentView drawLayer:inContext:] + 785
    11  QuartzCore                          0x01834209 -[CALayer drawInContext:] + 123
    12  QuartzCore                          0x0184ca98 _ZL18tiled_layer_renderP16_CAImageProviderjjjjPv + 1660
    13  QuartzCore                          0x0172d1c3 _ZL21CAImageProviderThreadPjb + 908
    14  QuartzCore                          0x0172ce32 _ZL31CAImageProviderBackgroundThreadPv + 19
    15  libdispatch.dylib                   0x034ad4b0 _dispatch_client_callout + 14
    16  libdispatch.dylib                   0x0349bef1 _dispatch_root_queue_drain + 287
    17  libdispatch.dylib                   0x0349c13d _dispatch_worker_thread2 + 39
    18  libsystem_c.dylib                   0x037f5e72 _pthread_wqthread + 441
    19  libsystem_c.dylib                   0x037dddaa start_wqthread + 30
)
libc++abi.dylib: terminating with uncaught exception of type NSException

The text was updated successfully, but these errors were encountered:

odrobnik · 2013-09-20T09:45:09Z

@brovador Please add a category -[NSString objectForKey:] and set a breakpoint on that to determine what string this is that this is tried to be called on.

brovador · 2013-09-20T11:24:34Z

@Cocoanetics Added the category, printing on the debugger the instance that is receiving the selector we have this:

(lldb) po self
CTFont 
CTFontDescriptor {type = mutable dict, count = 1,
entries =>
    1 : {contents = "NSFontNameAttribute"} = {contents = "Palatino-Roman"}
}

And printing the value of key received in the selector:

(lldb) po key
DTTextBlocks
(lldb) po [key class]
__NSCFConstantString

The screenshot:

I hope it helps

odrobnik · 2013-09-20T11:28:31Z

@brovador No idea. Does that mean that you found a case where self is a string and this string is set as text block?!

brovador · 2013-09-20T11:37:16Z

I've added a breakpoint in my category in the method - (id)objectForKey:(id)key, if I ask for self or key in the lldb when it's stopped at this breakpoint the info shown is that.

brovador · 2013-09-20T11:41:04Z

The stacktrace:

Breakpoint screenshot:

odrobnik · 2013-09-20T11:42:52Z

@brovador please inspect the attributed string what class the object has behind the DTTextBlock key.

brovador · 2013-09-20T13:10:59Z

After several tries, not always enter in the category, here is other break (BAD_ACCESS in this case) of the same method:

The stacktrace:

(lldb) print index
(NSUInteger) $3 = 6372
(lldb) print &effectiveRangeOfBlocksArray
(NSRange *) $4 = location=6363, length=57366424
(lldb) print DTTextBlocksAttribute
(NSString *const) $5 = 0x00508020 @"DTTextBlocks"
(lldb) print _attributedStringFragment
(NSAttributedString *) $6 = 0x0b5d6ec0 @"La señora aceleró el paso con sus tres hijos, Daoud, Hiba y Hasan Taha, a través de la avenida. No en vano, esta vía se ganó una triste fama durante meses, al ser elegida por un temible francotirador que -dicen- abatió a decenas de personas.
«Es el primer año que pueden venir al colegio porque en el año 2012 era imposible cruzar esa calle. Disparaban continuamente. Ahora es esporádico y podemos correr el riesgo. Hasan estaba hoy feliz, como si fuera su cumpleaños», explica Umm Daoud, la madre de los tres niños, nada más llegar al colegio.
Con más de dos decenas de colegios arrasados por los bombardeos, la ONG local Nashata ha conseguido habilitar tres aulas en un edificio a medio construir y otras tantas en una vivienda particular abandonada. El sábado fue el primer día del segundo año lectivo que apadrinan en la castigada ciudad siria de Deir Ezzor.
«Usamos el sótano para los más pequeños y p"

odrobnik · 2013-09-20T13:12:52Z

@brovador That's not what I asked. Please get the attributes at the specified index and check if the blocks attribute has the correct class.

brovador · 2013-09-20T13:24:03Z

Ok, sorry, checking it in both threads:

In thread 23:

(lldb) print index
(NSUInteger) $22 = 6372
(lldb) po [_attributedStringFragment attributesAtIndex:index effectiveRange:&effectiveRange]
{
    CTForegroundColor = " [ (kCGColorSpaceDeviceRGB)] ( 0.223529 0.223529 0.223529 1 )";
    NSFont = "CTFont \nCTFontDescriptor {type = mutable dict, count = 1,\nentries =>\n\t1 : {contents = \"NSFontNameAttribute\"} = {contents = \"Palatino-Roman\"}\n}\n>";
    NSParagraphStyle = "CTParagraphStyle:\nbase writing direction = -1, alignment = 3, line break mode = 0, default tab interval = 36\nfirst line head indent = 0, head indent = 0, tail indent = 0\nline height multiple = 0, maximum line height = 0, minimum line height = 0\nline spacing adjustment = 0, paragraph spacing = 18, paragraph spacing before = 0\n";
}
(lldb) po [_attributedStringFragment attribute:DTTextBlocksAttribute atIndex:index effectiveRange:&effectiveRange]
 nil

In thread 25:

(lldb) print index
(NSUInteger) $25 = 6371
(lldb) po [_attributedStringFragment attributesAtIndex:index effectiveRange:&effectiveRange]
{
    CTForegroundColor = " [ (kCGColorSpaceDeviceRGB)] ( 0.223529 0.223529 0.223529 1 )";
    NSFont = "CTFont \nCTFontDescriptor {type = mutable dict, count = 1,\nentries =>\n\t1 : {contents = \"NSFontNameAttribute\"} = {contents = \"Palatino-Roman\"}\n}\n>";
    NSParagraphStyle = "CTParagraphStyle:\nbase writing direction = -1, alignment = 3, line break mode = 0, default tab interval = 36\nfirst line head indent = 0, head indent = 0, tail indent = 0\nline height multiple = 0, maximum line height = 0, minimum line height = 0\nline spacing adjustment = 0, paragraph spacing = 18, paragraph spacing before = 0\n";
}
(lldb) po [_attributedStringFragment attribute:DTTextBlocksAttribute atIndex:index effectiveRange:&effectiveRange]
 nil

odrobnik · 2013-09-20T13:27:01Z

We are not getting anywhere like this. Can you please Skype me at TheDrops?

brovador · 2013-09-20T13:37:28Z

Ok perfect!

brovador · 2013-09-21T10:11:47Z

Hi Oliver and thanks a lot for the support, really.

I've created a small project that reproduces the issue:

https://github.com/brovador/DTCoreTextLayoutExceptionExample

In the example, I reproduced the same situation that in my project, creating a column based text. It seems that the issue is related to when is creating the TextContentViews for every column. It's not easy to reproduce, in our real project, we have a collection view of articles and the crash comes randomly when we are creating the cell for the article with the columns.

To recreate the same situation in a easy way, I've created a timer inside the ViewController with a button to regenerate the content (creating all the text columns etc). But it's only to force the error, because it's not even necessary the error can be thrown during application launch too.

I think the issue comes by drawing the columns, it's like two columns are being drawn at the same time and it causes the crash. If I inspect both threads, they have the same attributedstring and each one corresponds to one of the columns. The code in the example that I'm using to draw text layouted in columns:

DTHTMLAttributedStringBuilder *stringBuilder = [[DTHTMLAttributedStringBuilder alloc] initWithHTML:[text dataUsingEncoding:NSUTF8StringEncoding] options:nil documentAttributes:NULL];
DTCoreTextLayouter *layouter = [[DTCoreTextLayouter alloc] initWithAttributedString:[stringBuilder generatedAttributedString]];
    
NSInteger textRangeInit;
DTCoreTextLayoutFrame *layoutFrame;
DTAttributedTextView *textView;
    
//Column1
textRangeInit = 0;
    
layoutFrame = [layouter layoutFrameWithRect:(CGRect){.origin = CGPointZero, .size = column1.size} range:NSMakeRange(textRangeInit, 0)];
textView = [[DTAttributedTextView alloc] initWithFrame:column1];
[textView setAttributedString:[stringBuilder generatedAttributedString]];
[[textView attributedTextContentView] setLayoutFrame:layoutFrame];
[self.view addSubview:textView];
    
//Column2
textRangeInit = [layoutFrame visibleStringRange].location + [layoutFrame visibleStringRange].length;
    
layoutFrame = [layouter layoutFrameWithRect:(CGRect){.origin = CGPointZero, .size = column2.size} range:NSMakeRange(textRangeInit, 0)];
textView = [[DTAttributedTextView alloc] initWithFrame:column2];
[textView setAttributedString:[stringBuilder generatedAttributedString]];
[[textView attributedTextContentView] setLayoutFrame:layoutFrame];
[self.view addSubview:textView];
    
//Column3
textRangeInit = [layoutFrame visibleStringRange].location + [layoutFrame visibleStringRange].length;
    
layoutFrame = [layouter layoutFrameWithRect:(CGRect){.origin = CGPointZero, .size = column3.size} range:NSMakeRange(textRangeInit, 0)];
textView = [[DTAttributedTextView alloc] initWithFrame:column3];
[textView setAttributedString:[stringBuilder generatedAttributedString]];
[[textView attributedTextContentView] setLayoutFrame:layoutFrame];
[self.view addSubview:textView];

The same exception raised in the example:

I hope it helps

brovador · 2013-09-21T11:12:07Z

I've updated the example above, using a button to regenerate the content better than a timer.

brovador · 2013-09-21T13:30:07Z

Ok, after several tries, I finally found a workaround and more info about the problem (updated on my test project).

The issue happens when all the textviews created for each column share the same StringBuilder in the layouter. If I change the code to create a new instance of the stringbuilder and the layouter for each column, the issue does not appear.

In my project example I've added a switch to enable and disable de creation of all the elements for each column:

    DTHTMLAttributedStringBuilder *stringBuilder;
    DTCoreTextLayoutFrame *layoutFrame;
    DTAttributedTextView *textView;
    DTCoreTextLayouter *layouter;
    
    stringBuilder = [[DTHTMLAttributedStringBuilder alloc] initWithHTML:[text dataUsingEncoding:NSUTF8StringEncoding] options:nil documentAttributes:NULL];
    layouter = [[DTCoreTextLayouter alloc] initWithAttributedString:[stringBuilder generatedAttributedString]];
    
    //Column1
    textRangeInit = 0;
    
    layoutFrame = [layouter layoutFrameWithRect:(CGRect){.origin = CGPointZero, .size = column1.size} range:NSMakeRange(textRangeInit, 0)];
    textView = [[DTAttributedTextView alloc] initWithFrame:column1];
    [textView setAttributedString:[stringBuilder generatedAttributedString]];
    [[textView attributedTextContentView] setLayoutFrame:layoutFrame];
    [self.vTextContainer addSubview:textView];
    
    //Column2
    
    textRangeInit = [layoutFrame visibleStringRange].location + [layoutFrame visibleStringRange].length;
    if (createAllContent) {
        stringBuilder = [[DTHTMLAttributedStringBuilder alloc] initWithHTML:[text dataUsingEncoding:NSUTF8StringEncoding] options:nil documentAttributes:NULL];
        layouter = [[DTCoreTextLayouter alloc] initWithAttributedString:[stringBuilder generatedAttributedString]];
    }
    layoutFrame = [layouter layoutFrameWithRect:(CGRect){.origin = CGPointZero, .size = column2.size} range:NSMakeRange(textRangeInit, 0)];
    textView = [[DTAttributedTextView alloc] initWithFrame:column2];
    [textView setAttributedString:[stringBuilder generatedAttributedString]];
    [[textView attributedTextContentView] setLayoutFrame:layoutFrame];
    [self.vTextContainer addSubview:textView];
    
    //Column3
    textRangeInit = [layoutFrame visibleStringRange].location + [layoutFrame visibleStringRange].length;
    if (createAllContent) {
        stringBuilder = [[DTHTMLAttributedStringBuilder alloc] initWithHTML:[text dataUsingEncoding:NSUTF8StringEncoding] options:nil documentAttributes:NULL];
        layouter = [[DTCoreTextLayouter alloc] initWithAttributedString:[stringBuilder generatedAttributedString]];
    }
    layoutFrame = [layouter layoutFrameWithRect:(CGRect){.origin = CGPointZero, .size = column3.size} range:NSMakeRange(textRangeInit, 0)];
    textView = [[DTAttributedTextView alloc] initWithFrame:column3];
    [textView setAttributedString:[stringBuilder generatedAttributedString]];
    [[textView attributedTextContentView] setLayoutFrame:layoutFrame];
    [self.vTextContainer addSubview:textView];

if the variable createAllContent is true the string builder and the layouter will be created for each textview and doing this the issue does not appear in any case.

I think that it's something related with the string generated by the stringbuilder or something with the stringbuilder itself. As workaround I can create the stringbuilder and layouter for each column but it will be very less efficient that having a single instance shared between all the textviews that creates the columns of the text.

odrobnik · 2013-09-21T16:33:14Z

I fear that enumerations of NSAttributedString attributes might not be thread-safe. A solution would be to determine the ranges of text blocks once for the entire layout frame.

Best regards
Oliver Drobnik

@Cocoanetics on Twitter and App.net
www.cocoanetics.com

On 21.09.2013, at 15:30, brovador notifications@github.com wrote:

Ok, after several tries, I finally found a workaround and more info about the problem (updated on my test project).

The issue happens when all the textviews created for each column share the same StringBuilder in the layouter. If I change the code to create a new instance of the stringbuilder and the layouter for each column, the issue does not appear.

In my project example I've added a switch to enable and disable de creation of all the elements for each column. Basicly:
DTHTMLAttributedStringBuilder *stringBuilder;
DTCoreTextLayoutFrame *layoutFrame;
DTAttributedTextView *textView;
DTCoreTextLayouter *layouter;

stringBuilder = [[DTHTMLAttributedStringBuilder alloc] initWithHTML:[text dataUsingEncoding:NSUTF8StringEncoding] options:nil documentAttributes:NULL];
layouter = [[DTCoreTextLayouter alloc] initWithAttributedString:[stringBuilder generatedAttributedString]];

//Column1
textRangeInit = 0;

layoutFrame = [layouter layoutFrameWithRect:(CGRect){.origin = CGPointZero, .size = column1.size} range:NSMakeRange(textRangeInit, 0)];
textView = [[DTAttributedTextView alloc] initWithFrame:column1];
[textView setAttributedString:[stringBuilder generatedAttributedString]];
[[textView attributedTextContentView] setLayoutFrame:layoutFrame];
[self.vTextContainer addSubview:textView];

//Column2

textRangeInit = [layoutFrame visibleStringRange].location + [layoutFrame visibleStringRange].length;
if (createAllContent) {
    stringBuilder = [[DTHTMLAttributedStringBuilder alloc] initWithHTML:[text dataUsingEncoding:NSUTF8StringEncoding] options:nil documentAttributes:NULL];
    layouter = [[DTCoreTextLayouter alloc] initWithAttributedString:[stringBuilder generatedAttributedString]];
}
layoutFrame = [layouter layoutFrameWithRect:(CGRect){.origin = CGPointZero, .size = column2.size} range:NSMakeRange(textRangeInit, 0)];
textView = [[DTAttributedTextView alloc] initWithFrame:column2];
[textView setAttributedString:[stringBuilder generatedAttributedString]];
[[textView attributedTextContentView] setLayoutFrame:layoutFrame];
[self.vTextContainer addSubview:textView];

//Column3
textRangeInit = [layoutFrame visibleStringRange].location + [layoutFrame visibleStringRange].length;
if (createAllContent) {
    stringBuilder = [[DTHTMLAttributedStringBuilder alloc] initWithHTML:[text dataUsingEncoding:NSUTF8StringEncoding] options:nil documentAttributes:NULL];
    layouter = [[DTCoreTextLayouter alloc] initWithAttributedString:[stringBuilder generatedAttributedString]];
}
layoutFrame = [layouter layoutFrameWithRect:(CGRect){.origin = CGPointZero, .size = column3.size} range:NSMakeRange(textRangeInit, 0)];
textView = [[DTAttributedTextView alloc] initWithFrame:column3];
[textView setAttributedString:[stringBuilder generatedAttributedString]];
[[textView attributedTextContentView] setLayoutFrame:layoutFrame];
[self.vTextContainer addSubview:textView];
if the variable createAllContent is true the string builder and the layouter will be created for each textview and doing this the issue does not appear in any case.

I think that it's something related with the string generated by the stringbuilder or something with the stringbuilder itself. As workaround I can't create this stringbuilder and layouter for each column but it will be very less efficient that having a single instance shared between all the textviews that creates the columns of the text.

—
Reply to this email directly or view it on GitHub.

brovador · 2013-09-21T21:20:17Z

Right @Cocoanetics, calculating first the ranges for the layout frame and assigning the substrings to the columns the issue didn't appear:

    stringBuilder = [[DTHTMLAttributedStringBuilder alloc] initWithHTML:[text dataUsingEncoding:NSUTF8StringEncoding] options:nil documentAttributes:NULL];
    attrString = [stringBuilder generatedAttributedString];
    layouter = [[DTCoreTextLayouter alloc] initWithAttributedString:attrString];
    
    NSRange range1, range2, range3;
    
    textRangeInit = 0;
    layoutFrame = [layouter layoutFrameWithRect:(CGRect){.origin = CGPointZero, .size = column1.size} range:NSMakeRange(textRangeInit, 0)];
    range1 = [layoutFrame visibleStringRange];
    
    textRangeInit = range1.location + range1.length;
    layoutFrame = [layouter layoutFrameWithRect:(CGRect){.origin = CGPointZero, .size = column2.size} range:NSMakeRange(textRangeInit, 0)];
    range2 = [layoutFrame visibleStringRange];
    
    textRangeInit = range2.location + range2.length;
    layoutFrame = [layouter layoutFrameWithRect:(CGRect){.origin = CGPointZero, .size = column3.size} range:NSMakeRange(textRangeInit, 0)];
    range3 = [layoutFrame visibleStringRange];
    
    //Column1
    textView = [[DTAttributedTextView alloc] initWithFrame:column1];
    [textView setAttributedString:[attrString attributedSubstringFromRange:range1]];
    [self.vTextContainer addSubview:textView];
    
    //Column2
    textView = [[DTAttributedTextView alloc] initWithFrame:column2];
    [textView setAttributedString:[attrString attributedSubstringFromRange:range2]];
    [self.vTextContainer addSubview:textView];
    
    //Column3
    textView = [[DTAttributedTextView alloc] initWithFrame:column3];
    [textView setAttributedString:[attrString attributedSubstringFromRange:range3]];
    [self.vTextContainer addSubview:textView];

This it's probably the best solution. The layouter and the attributedstringbuilder not need to be regenerated for every column and the code is now thread-safe. For me it's a good workaround to my problem, thanks a lot.

I've created a new example project using this technique: https://github.com/brovador/DTCoreTextColumnsExample

odrobnik · 2013-09-27T10:38:08Z

Closing this as it does not require a change to DTCoreText.

odrobnik · 2013-10-02T09:30:35Z

I'm going to implement a serial queue to avoid doing two enumerations on different threads at the same time.

odrobnik · 2013-10-02T12:27:26Z

I've implemented additional synchronization to prevent multiple processes from enumerating the text boxes at the same time.

@brovador it would be great if you could try the current develop version and verify that this indeed fixes the issue.

brovador · 2013-10-02T13:16:27Z

Ok, I will check it against my test project and verify it. Thanks!

brovador · 2013-10-02T19:12:34Z

@Cocoanetics , I've uploaded again the sample project here:

https://github.com/brovador/DTCoreTextExceptionExample

I was trying with this Podfile, but error still happens:

platform :ios, '5.0'
pod 'DTCoreText', :git => 'https://github.com/Cocoanetics/DTCoreText.git', :branch => 'develop'
pod 'DTFoundation', :git => 'https://github.com/Cocoanetics/DTFoundation.git', :branch => 'develop'

You can download and use my sample project to test or debug the issue. I hope it helps

odrobnik · 2013-10-03T04:03:32Z

@brovador please post a screen shot of the threads call stacks with all threads expanded.

Also, please tell me which Xcode, Sim version you use to reproduce this.

odrobnik · 2013-10-03T08:08:49Z

@brovador Turns out that I needed to synch on the _framesetter or globally. Apparently even though the layoutFrame, the view and the attributed string are separate instances, if you enumerate on overlapping regions you get a crash. Synchronizing on the view class or the _framesetter worked. For safety I opted to do it on the content view globally.

please re-test and comment.

brovador · 2013-10-03T16:04:33Z

Tested over my sample project and now works perfect, Thanks!

odrobnik closed this as completed Sep 27, 2013

odrobnik reopened this Oct 2, 2013

ghost assigned odrobnik Oct 2, 2013

odrobnik closed this as completed Oct 2, 2013

odrobnik reopened this Oct 3, 2013

odrobnik closed this as completed in 00cb93e Oct 3, 2013

iOkay mentioned this issue Nov 8, 2013

Crash in -[DTCoreTextLayoutFrame _enumerateTextBlocksAtLevel:inRange:usingBlock:] #669

Closed

astralbodies mentioned this issue Nov 19, 2013

Update DTCoreText to 1.6.8 or > to eliminate common crash wordpress-mobile/WordPress-iOS#584

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Crash in (NSRange)_effectiveRangeOfOutermostTextBlocksInRange:(NSRange)range #606

Crash in (NSRange)_effectiveRangeOfOutermostTextBlocksInRange:(NSRange)range #606

brovador commented Sep 19, 2013

odrobnik commented Sep 20, 2013

brovador commented Sep 20, 2013

odrobnik commented Sep 20, 2013

brovador commented Sep 20, 2013

brovador commented Sep 20, 2013

odrobnik commented Sep 20, 2013

brovador commented Sep 20, 2013

odrobnik commented Sep 20, 2013

brovador commented Sep 20, 2013

odrobnik commented Sep 20, 2013

brovador commented Sep 20, 2013

brovador commented Sep 21, 2013

brovador commented Sep 21, 2013

brovador commented Sep 21, 2013

odrobnik commented Sep 21, 2013

brovador commented Sep 21, 2013

odrobnik commented Sep 27, 2013

odrobnik commented Oct 2, 2013

odrobnik commented Oct 2, 2013

brovador commented Oct 2, 2013

brovador commented Oct 2, 2013

odrobnik commented Oct 3, 2013

odrobnik commented Oct 3, 2013

brovador commented Oct 3, 2013

Crash in (NSRange)_effectiveRangeOfOutermostTextBlocksInRange:(NSRange)range #606

Crash in (NSRange)_effectiveRangeOfOutermostTextBlocksInRange:(NSRange)range #606

Comments

brovador commented Sep 19, 2013

odrobnik commented Sep 20, 2013

brovador commented Sep 20, 2013

odrobnik commented Sep 20, 2013

brovador commented Sep 20, 2013

brovador commented Sep 20, 2013

odrobnik commented Sep 20, 2013

brovador commented Sep 20, 2013

odrobnik commented Sep 20, 2013

brovador commented Sep 20, 2013

odrobnik commented Sep 20, 2013

brovador commented Sep 20, 2013

brovador commented Sep 21, 2013

brovador commented Sep 21, 2013

brovador commented Sep 21, 2013

odrobnik commented Sep 21, 2013

brovador commented Sep 21, 2013

odrobnik commented Sep 27, 2013

odrobnik commented Oct 2, 2013

odrobnik commented Oct 2, 2013

brovador commented Oct 2, 2013

brovador commented Oct 2, 2013

odrobnik commented Oct 3, 2013

odrobnik commented Oct 3, 2013

brovador commented Oct 3, 2013