Aperture 3.4.4 crashes with NSRangeException

Question

My Aperture 3.4.4 crashes all the time a few minutes after startup.
attached the error message below.
Someone has any idea to fix this?
Exception Type:  EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Application Specific Information:
*** Terminating app due to uncaught exception 'NSRangeException', reason: '*** -[NSPathStore2 substringWithRange:]: Range or index out of bounds'
terminate called throwing an exception
abort() called
Application Specific Backtrace 1:
0   CoreFoundation                      0x00007fff871f6b06 __exceptionPreprocess + 198
1   libobjc.A.dylib                     0x00007fff8d00f3f0 objc_exception_throw + 43
2   CoreFoundation                      0x00007fff871f68dc +[NSException raise:format:] + 204
3   Foundation                          0x00007fff81f3a3ad -[NSString substringWithRange:] + 107
4   RedRock                             0x000000010a0b693f +[RKFileNamingPolicy fileSafeName:] + 136
5   RedRock                             0x000000010a261958 -[RKVersion(Imaging) proxyWritePath:] + 141
6   RedRock                             0x000000010a261edf -[RKVersion(Imaging) absoluteProxyWritePath:] + 28
7   RedRock                             0x000000010a255b97 -[JPEGFileCacheStore filePathForVersion:key:withWrite:] + 51
8   RedRock                             0x000000010a329d64 -[IPMiniJPEGFileCacheStore newCachePageLookupForRequest:] + 428
9   ProXTCore                           0x000000010b88a14e -[XTCachePersistentPolicy newCachePageOnLookupForRequest:] + 136
10  ProXTCore                           0x000000010b881534 -[XTCacheEvictionPolicy isObjectReadyForRequest:] + 20
11  ProXTCore                           0x000000010b8872d0 -[XTCacheStore isObjectReadyForRequest:] + 37
12  ProXTCore                           0x000000010b880b77 -[XTCache isObjectReadyForRequest:] + 28
13  RedRock                             0x000000010a20b8a2 -[RKImageCache hasThumbnailOnDiskForVersion:style:] + 70
14  RedRock                             0x000000010a21b12c -[DownsampleFactory cache:cacheStore:onFulfillRequest:intoPageRef:] + 1162
15  ProXTCore                           0x000000010b882501 -[XTCacheFactory cache:cacheStore:fulfillRequest:intoPageRef:] + 896
16  ProXTCore                           0x000000010b881388 -[XTCacheBroker cacheStore:fulfillRequest:intoPageRef:] + 51
17  ProXTCore                           0x000000010b88809f -[XTCacheStore newObjectFulfillRequest:] + 546
18  ProXTCore                           0x000000010b888657 -[XTCacheStore newObjectForRequest:] + 1034
19  Geode                               0x000000010b629fc0 -[DGTier2Factory readRequest:intoPageRef:] + 482
20  Geode                               0x000000010b62a604 -[DGTier2Factory cache:cacheStore:onFulfillRequest:intoPageRef:] + 589
21  ProXTCore                           0x000000010b881f47 -[XTCacheFactory backgroundFulfillment:] + 532
22  ProXTCore                           0x000000010b862736 -[XTDistributor distributeMessage:] + 444
23  ProXTCore                           0x000000010b8620fa -[XTThread handleMessage:] + 342
24  ProXTCore                           0x000000010b860eb3 -[XTThread run:] + 345
25  Foundation                          0x00007fff81f5acd2 __NSThread__main__ + 1345
26  libsystem_c.dylib                   0x00007fff8a28f7a2 _pthread_start + 327
27  libsystem_c.dylib                   0x00007fff8a27c1e1 thread_start + 13

Answer 1

Finally, I found both of the cause and the solution.
The cause :
(1) in Aperture, upload some photos to Facebook
(2) in Facebook, update the photos's caption with long foreign characters.
(3) in Aperture, synchronize the photos with Facebook again.
This will rename the photo files in Aperture library, and eventually this will corrupt Database/ImageProxies.apdb inside Aperture library folder.
when Aperture accesses this correupted Database/ImageProxies.apdb file, Aperture just crashes.
The temporary solution :
(1) quit Aperture
(2) delete Database/ImageProxies.apdb file inside Aperture library folder.
(3) start Aperture
(4) it will be better rename the master files with only english alphabet to prevent future crash.
    (We can update all the master file names easily by using "Batch Change" menu.)
Please someone let Aperture developer know this and fix it for next release.
Regards
This will help until the next sync, if you do not also fix the captions on Facebook.
But you never answered my question re the formatting of your drives:
Are your referenced original master image files on a drive formatted MacOS X extended Journaled?
Long filenames or ethnic characters in the captions and version names derived from the captions should only matter, if the drive is formatted incorrectly. It would really be good to know, for future similar cases, if all this happened with the library and /or the original files on a correctly formatted drive.