search for: dispatch_group_async_f

...from the LLVM docs whether this is allowed. I would be surprised, however, if the global lock I added wouldn't have sorted out that issue if it was the problem. - In case it makes any difference, I am running on OS X and using Grand Central Dispatch to execute the background compilation using dispatch_group_async_f() Is this a known problem? Can anyone suggest anything I can do to fix or further debug this problem? Thanks in advance, Peter Zion #0 0x965221a6 in szone_malloc_should_clear () #1 0x00916795 in ChromeMain () #2 0x96522148 in malloc_zone_malloc () #3 0x96520218 in malloc () #4 0x953da617 i...

...the LLVM docs whether this is allowed.  I would be surprised, however, if the global lock I added wouldn't have sorted out that issue if it was the problem. > - In case it makes any difference, I am running on OS X and using Grand Central Dispatch to execute the background compilation using dispatch_group_async_f() > > Is this a known problem?  Can anyone suggest anything I can do to fix or further debug this problem? My best guess is that your background thread has less stack space than the main thread. The version of LazyValueInfo which is in 2.8 was recursive, and can use a lot of stack space in...