Hi,
It is not easily reproducible (see below), but is periodically reported by users.
Crash always occurs in iOS code, and searching for similar stack traces shows similar issues reported on Mac OS X in the past.
Chrome code that leads to the crash is inspired by Apple's sample code and is publicly available here:
The only relatively repeatable way to reproduce this (or similar) issue requires the following:
1. Use Mac OS X machine connected to wired corporate network.
2. Have 'Auto Proxy Discovery' enabled for that ethernet adapter.
3. Build Chrome for iOS for running in the simulator.
4. Place breakpoints in certain (unrelated) places to affect timing.
5. Start Chrome in the simulator under debugger.
6. Pause on break points for 5-15 seconds at the time.
7. In ~20% of the cases observe crash inside of CoreFoundation.
8. If crash does not occur, stop Chrome and restart with step 5.
Couple of notes:
- Corporate network uses fairly complex proxy configuration script.
- There are multiple (3-5) threads that are concurrently calling net::ProxyResolverMac::GetProxyForURL().
- There are crash reports with slightly different call stacks, all of them somewhere inside of Apple's code called from CFRunLoopRunInMode doing CFNetworkExecuteProxyAutoConfigurationURL.
We have tried a few ideas, but they didn't seem to help, so I'll appreciate any expert advice,
thanks,
-m