Hi guys, This is a known problem, we are working on a fix for it right now.
Although we've received some reports that people started seeing this particular crash report a lot more after upgrading to Snow Leopard, it's not completely isolated to Snow Leopard. We are pretty far along with the actual fix and are currently testing whether it has any adverse effects elsewhere. To fix the issue, we've had to make some changes pretty deep down in the guts of some of the library code we use, so we need/want to test rigorously for side effects before we're ready to ship it. I'm hoping we'll have this resolved soon, possibly in the next update to Versions, Thanks for your patience, - Dirk the Versions team On Dec 3, 3:13 pm, misterniall <niall.br...@gmail.com> wrote: > You aren't the only one. I have at least 30 of them > > here is an example of mine: > > Process: Versions [1599] > Path: /Applications/Versions.app/Contents/MacOS/Versions > Identifier: Versions > Version: ??? (???) > Code Type: X86 (Native) > Parent Process: Versions [424] > > Date/Time: 2009-11-19 16:33:42.839 -0330 > OS Version: Mac OS X 10.6.2 (10C540) > Report Version: 6 > > Interval Since Last Report: 4201 sec > Crashes Since Last Report: 1 > Per-App Crashes Since Last Report: 1 > Anonymous UUID: F7C53458-E942-4CBE- > B7B1-21971F46D79B > > Exception Type: EXC_BAD_ACCESS (SIGSEGV) > Exception Codes: KERN_INVALID_ADDRESS at 0x0000000073722f83 > Crashed Thread: 0 > > Application Specific Information: > *** multi-threaded process forked *** > > Thread 0 Crashed: > 0 libapr.dylib 0x002d928d apr_pool_cleanup_kill + -- You received this message because you are subscribed to the Google Groups "Versions" group. To post to this group, send email to versi...@googlegroups.com. To unsubscribe from this group, send email to versions+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/versions?hl=en.
