Skip to content
Snippets Groups Projects
Select Git revision
  • master default
  • adhoc_3.1.20171129_215341
  • adhoc_3.1.5.beta.2
  • transparentMetal2
  • adhoc_3.1.20171104_144308
  • metal
  • adhoc_3.1.20171013_214551
  • asyncSemanticHistory
  • release_3.1.2
  • adhoc_3.1.20170924_105026
  • 3.1.1
  • adhoc_3.1.20170912_222342
  • adhoc_3.1.20170820_220120
  • deferredUpdateWithBugfix
  • cadenceControllerAndDeferredCadenceChanges
  • adhoc_3.1.20170801_221757
  • adhoc_3.1.20170513_113452
  • 3.0.16
  • adhoc_3.1.20170424_220422
  • adhoc_3.1.20170424_215714
  • v3.1.5
  • v3.1.5.beta.2
  • v3.1.4
  • v3.1.5.beta.1
  • v3.1.4.beta.1
  • v3.1.3
  • v3.1.3.beta.1
  • v3.1.2
  • v3.1.2.beta.2
  • v3.1.2.beta.1
  • v3.1.1
  • v3.1.0
  • v3.1.beta.10
  • v3.1.beta.9
  • v3.1.beta.8
  • v3.1.beta.7
  • v3.1.beta.6
  • v3.1.beta.5
  • v3.1.beta.4
  • v3.1.beta.3
40 results

NSFileManager+iTerm.h

  • George Nachman's avatar
    8bc31051
    Remove mechanism for catching proc_pidinfo and statfs timeouts. It was causing... · 8bc31051
    George Nachman authored 
    Remove mechanism for catching proc_pidinfo and statfs timeouts. It was causing crashes, but I don't understand why. Perhaps mixing ARC and non-ARC code has some problem? I saw lots of crashes on 3.1.4 where proc_pidinfo exceeded the timeout and when it finally returned there was heap corruption. It looked as though the dispatch group had been freed even though there was an outstanding reference to it. At any rate, if proc_pidinfo is hanging you're going to have a bad time even without this workaround.
    8bc31051
    History
    Remove mechanism for catching proc_pidinfo and statfs timeouts. It was causing...
    George Nachman authored 
    Remove mechanism for catching proc_pidinfo and statfs timeouts. It was causing crashes, but I don't understand why. Perhaps mixing ARC and non-ARC code has some problem? I saw lots of crashes on 3.1.4 where proc_pidinfo exceeded the timeout and when it finally returned there was heap corruption. It looked as though the dispatch group had been freed even though there was an outstanding reference to it. At any rate, if proc_pidinfo is hanging you're going to have a bad time even without this workaround.