Databases
StackOverflow2013
Postsdbo
POCrashes in __CFTSDFinalize
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POCrashes in __CFTSDFinalize
    primarykey
    data
    text
    <p>we have a serious crashing bug we can absolutely not get a hold of. The problem is that it happens to happen asynchronously in the background, obviously when the dispatch system cleans up a worker thread. Here are two example stack traces:</p> <pre><code>Thread 7 Crashed: 0 libobjc.A.dylib 0x3b23b5b0 objc_msgSend + 15 1 Foundation 0x33c03581 -[NSNotificationCenter postNotificationName:object:userInfo:] + 49 2 Foundation 0x33cb3367 __NSFinalizeThreadData + 255 3 CoreFoundation 0x3336cf81 __CFTSDFinalize + 65 4 libsystem_c.dylib 0x3b68a12b _pthread_tsd_cleanup + 174 5 libsystem_c.dylib 0x3b689e03 _pthread_exit + 119 6 libsystem_c.dylib 0x3b68cd02 _pthread_workq_return + 26 7 libsystem_c.dylib 0x3b68ca16 _pthread_wqthread + 366 </code></pre> <p>And:</p> <pre><code>Thread 8 Crashed: 0 Foundation 0x31bfd2e2 __NSFinalizeThreadData + 122 1 CoreFoundation 0x312b6f81 __CFTSDFinalize + 65 2 libsystem_c.dylib 0x395d412b _pthread_tsd_cleanup + 174 3 libsystem_c.dylib 0x395d3e03 _pthread_exit + 119 4 libsystem_c.dylib 0x395d6d02 _pthread_workq_return + 26 5 libsystem_c.dylib 0x395d6a16 _pthread_wqthread + 366 </code></pre> <p>All these crash reports seem to have the same reason:</p> <pre><code>Exception Type: SIGSEGV Exception Codes: SEGV_ACCERR at 0x9209ea83 </code></pre> <p>I got as far as this: It seems there is an <code>NSThreadWillExitNotification</code> being posted. Crash logs occur more often <strong>without</strong> the <code>NSNotificationCenter</code> frame (second example). Regular invocations just pass <code>@"NSThreadWillExitNotification"</code>, the <code>NSThread</code> object, <code>nil</code> userInfo.</p> <p>All problems I can think of right now is the NSThread object being overreleased somehow. I just checked and <strong>all</strong> uses we make of NSThread are simple equivalence checks with the main thread. Like so:</p> <pre><code>if (NSThread.currentThread == NSThread.mainThread) ... </code></pre> <p>Any insights? Just another weird ARC issue?</p> <p>Thank you all,<br> Max</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USMax Seelemann
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POCrashes in __CFTSDFinalize
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POCrashes in __CFTSDFinalize
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POCrashes in __CFTSDFinalize
      1. USstoflow
      1. VTFavorite
    1. CORelated, perhaps? http://stackoverflow.com/questions/12901031/segv-accerr-calling-nsnotificationcenter-defaultcenter-removeobserverself-i
      singulars
      1. POCrashes in __CFTSDFinalize
      1. USCodaFi
    2. CO@CodaFi Not really, because this method happens to be called after all user-objects have been freed.
      singulars
      1. POCrashes in __CFTSDFinalize
      1. USMax Seelemann
    3. COWhat happens if you CFRetain the thread as a test?
      singulars
      1. POCrashes in __CFTSDFinalize
      1. USFrank Illenberger
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload