Remove image cache files

I found on a metalink note "Remove image cache files within directory "$OA_HTML/cabo/images/cache" and style sheet cache files within directory "$OA_HTML/cabo/styles/cache" after the patch is successfully applied"
Could anybody tell me which are the files extension I have to look for (I have to remove)?
thanks,
Paul

That would be ok but make sure you bounce Apache then.
If you have any other languages installed, you would find a directory <lang code> (such as 'en' for English, 'ar' for Arabic) under <OA_HTML>/cabo/images/cache/<lang code> which is used to cache dynamically created images for each language.

Similar Messages

  • Retrieving folder of images - cache file?

    Looks like I have trashed a couple of folders of images stored on the desktop, not iPhoto. However, i found two cache files with the suffix .dpImageCache
    They both have a different file size to one another so it looks like they have got the images there. Is there any way of retrieving the images? Or is this just some stupid dumb techie thing that serves no purpose other than to wind the user up?

    Hi, IR75. There is a .dpimagecache file for each folder of pictures you have used in the past as desktop images. It is a stupid dumb techie thing that serves some purpose best understood by OS X itself and perhaps by stupid dumb techies, not including me or, apparently, you. I don't believe you are likely to have any luck extracting any actual photos from it.
    To recover files of any kind that have been accidentally trashed by someone who is certainly not a stupid dumb techie, but might fairly be characterized as careless, you may want to download the demo version of Data Rescue II or FileSalvage and use it to see whether the photos (or some of them) are still recoverable. If they are, stop using your computer until you are able to buy the full version of one of those utilities and recover your photos to some storage medium other than your main hard drive.
    When you trash a file and empty the trash, the file remains on your hard drive; only its directory entry is removed. That has the effect of making the space it occupies on the drive available for other uses. Until it is actually overwritten by something else in the course of your computer use, it remains recoverable by software that is specially designed for that purpose, like the two utilities I mentioned above.

  • I reinstalled Lion OS after removing the cache file as suggested before but I am still having same issue. Safari quits unexpectedly every time I try to open it.it

    Process:         Safari [386]
    Path:            /Applications/Safari.app/Contents/MacOS/Safari
    Identifier:      com.apple.Safari
    Version:         5.1.6 (7534.56.5)
    Build Info:      WebBrowser-7534056005000000~6
    Code Type:       X86-64 (Native)
    Parent Process:  launchd [147]
    Date/Time:       2012-09-03 19:41:08.591 -0700
    OS Version:      Mac OS X 10.7.4 (11E53)
    Report Version:  9
    Interval Since Last Report:          126027 sec
    Crashes Since Last Report:           24
    Per-App Interval Since Last Report:  577001 sec
    Per-App Crashes Since Last Report:   24
    Anonymous UUID:                      A6055379-1AD4-4DCF-9E47-C29E229C434B
    Crashed Thread:  0  Dispatch queue: com.apple.main-thread
    Exception Type:  EXC_CRASH (SIGABRT)
    Exception Codes: 0x0000000000000000, 0x0000000000000000
    Application Specific Information:
    objc[386]: garbage collection is OFF
    *** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'Invalid parameter not satisfying: (index >= 0) && (index < [_itemArray count])'
    *** First throw call stack:
    0   CoreFoundation                      0x00007fff99134f56 __exceptionPreprocess + 198
    1   libobjc.A.dylib                     0x00007fff91aa7d5e objc_exception_throw + 43
    2   CoreFoundation                      0x00007fff99134d8a +[NSException raise:format:arguments:] + 106
    3   Foundation                          0x00007fff94b9271f -[NSAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 169
    4   AppKit                              0x00007fff931e0cdf -[NSMenu itemAtIndex:] + 165
    5   AppKit                              0x00007fff931e0e38 -[NSMenu removeItemAtIndex:] + 63
    6   Safari                              0x000000010d0a3c2e -[AppController awakeFromNib] + 387
    7   CoreFoundation                      0x00007fff9912bfb1 -[NSObject performSelector:] + 49
    8   CoreFoundation                      0x00007fff9912bf32 -[NSSet makeObjectsPerformSelector:] + 274
    9   AppKit                              0x00007fff931c89ff -[NSIBObjectData nibInstantiateWithOwner:topLevelObjects:] + 1245
    10  AppKit                              0x00007fff931bef73 loadNib + 322
    11  AppKit                              0x00007fff931be470 +[NSBundle(NSNibLoading) _loadNibFile:nameTable:withZone:ownerBundle:] + 217
    12  AppKit                              0x00007fff931be38b +[NSBundle(NSNibLoading) loadNibFile:externalNameTable:withZone:] + 141
    13  AppKit                              0x00007fff931be2ce +[NSBundle(NSNibLoading) loadNibNamed:owner:] + 364
    14  AppKit                              0x00007fff9342f06f NSApplicationMain + 398
    15  Safari                              0x000000010d2a6806 SafariMain + 166
    16  Safari                              0x000000010d08ff24 Safari + 3876
    17  ???                                 0x0000000000000002 0x0 + 2
    terminate called throwing an exception
    abort() called
    Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
    0   libsystem_kernel.dylib             0x00007fff9a393ce2 __pthread_kill + 10
    1   libsystem_c.dylib                  0x00007fff900fd7d2 pthread_kill + 95
    2   libsystem_c.dylib                  0x00007fff900eea7a abort + 143
    3   libc++abi.dylib                    0x00007fff94a927bc abort_message + 214
    4   libc++abi.dylib                    0x00007fff94a8ffcf default_terminate() + 28
    5   libobjc.A.dylib                    0x00007fff91aa81b9 _objc_terminate + 94
    6   libc++abi.dylib                    0x00007fff94a90001 safe_handler_caller(void (*)()) + 11
    7   libc++abi.dylib                    0x00007fff94a9005c std::terminate() + 16
    8   libc++abi.dylib                    0x00007fff94a91152 __cxa_throw + 114
    9   libobjc.A.dylib                    0x00007fff91aa7e7a objc_exception_throw + 327
    10  com.apple.CoreFoundation           0x00007fff99134d8a +[NSException raise:format:arguments:] + 106
    11  com.apple.Foundation               0x00007fff94b9271f -[NSAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 169
    12  com.apple.AppKit                   0x00007fff931e0cdf -[NSMenu itemAtIndex:] + 165
    13  com.apple.AppKit                   0x00007fff931e0e38 -[NSMenu removeItemAtIndex:] + 63
    14  com.apple.Safari.framework         0x000000010d0a3c2e -[AppController awakeFromNib] + 387
    15  com.apple.CoreFoundation           0x00007fff9912bfb1 -[NSObject performSelector:] + 49
    16  com.apple.CoreFoundation           0x00007fff9912bf32 -[NSSet makeObjectsPerformSelector:] + 274
    17  com.apple.AppKit                   0x00007fff931c89ff -[NSIBObjectData nibInstantiateWithOwner:topLevelObjects:] + 1245
    18  com.apple.AppKit                   0x00007fff931bef73 loadNib + 322
    19  com.apple.AppKit                   0x00007fff931be470 +[NSBundle(NSNibLoading) _loadNibFile:nameTable:withZone:ownerBundle:] + 217
    20  com.apple.AppKit                   0x00007fff931be38b +[NSBundle(NSNibLoading) loadNibFile:externalNameTable:withZone:] + 141
    21  com.apple.AppKit                   0x00007fff931be2ce +[NSBundle(NSNibLoading) loadNibNamed:owner:] + 364
    22  com.apple.AppKit                   0x00007fff9342f06f NSApplicationMain + 398
    23  com.apple.Safari.framework         0x000000010d2a6806 SafariMain + 166
    24  com.apple.Safari                   0x000000010d08ff24 0x10d08f000 + 3876
    Thread 1:: Dispatch queue: com.apple.libdispatch-manager
    0   libsystem_kernel.dylib             0x00007fff9a3947e6 kevent + 10
    1   libdispatch.dylib                  0x00007fff9729078a _dispatch_mgr_invoke + 923
    2   libdispatch.dylib                  0x00007fff9728f31a _dispatch_mgr_thread + 54
    Thread 2:
    0   libsystem_kernel.dylib             0x00007fff9a394192 __workq_kernreturn + 10
    1   libsystem_c.dylib                  0x00007fff900fd594 _pthread_wqthread + 758
    2   libsystem_c.dylib                  0x00007fff900feb85 start_wqthread + 13
    Thread 3:
    0   libsystem_kernel.dylib             0x00007fff9a394192 __workq_kernreturn + 10
    1   libsystem_c.dylib                  0x00007fff900fd594 _pthread_wqthread + 758
    2   libsystem_c.dylib                  0x00007fff900feb85 start_wqthread + 13
    Thread 4:: WebCore: IconDatabase
    0   libsystem_kernel.dylib             0x00007fff9a394a8e pread + 10
    1   libsqlite3.dylib                   0x00007fff97e9dce5 unixRead + 69
    2   libsqlite3.dylib                   0x00007fff97ebf4f6 readDbPage + 102
    3   libsqlite3.dylib                   0x00007fff97ebdc9b sqlite3PagerAcquire + 315
    4   libsqlite3.dylib                   0x00007fff97eec872 moveToChild + 146
    5   libsqlite3.dylib                   0x00007fff97eeeb68 sqlite3BtreeNext + 600
    6   libsqlite3.dylib                   0x00007fff97ee7909 sqlite3VdbeExec + 41561
    7   libsqlite3.dylib                   0x00007fff97edca5b sqlite3_step + 1883
    8   com.apple.WebCore                  0x000000010e147eff WebCore::SQLiteStatement::step() + 63
    9   com.apple.WebCore                  0x000000010e1486cc WebCore::IconDatabase::performURLImport() + 908
    10  com.apple.WebCore                  0x000000010e146d3b WebCore::IconDatabase::iconDatabaseSyncThread() + 475
    11  com.apple.JavaScriptCore           0x000000010da8011f _ZN3WTFL19wtfThreadEntryPointEPv + 15
    12  libsystem_c.dylib                  0x00007fff900fb8bf _pthread_start + 335
    13  libsystem_c.dylib                  0x00007fff900feb75 thread_start + 13
    Thread 5:: Dispatch queue: com.apple.CFURLCACHE_work_queue
    0   libsystem_kernel.dylib             0x00007fff9a394a8e pread + 10
    1   libsqlite3.dylib                   0x00007fff97e9dce5 unixRead + 69
    2   libsqlite3.dylib                   0x00007fff97eba898 sqlite3PagerSharedLock + 2184
    3   libsqlite3.dylib                   0x00007fff97eb9a47 sqlite3BtreeBeginTrans + 1191
    4   libsqlite3.dylib                   0x00007fff97eb1427 sqlite3InitOne + 2391
    5   libsqlite3.dylib                   0x00007fff97eb0a44 sqlite3Init + 116
    6   libsqlite3.dylib                   0x00007fff97eabdcf sqlite3Pragma + 10287
    7   libsqlite3.dylib                   0x00007fff97ea3e4f yy_reduce + 3967
    8   libsqlite3.dylib                   0x00007fff97ea2a2d sqlite3Parser + 253
    9   libsqlite3.dylib                   0x00007fff97ea16fd sqlite3RunParser + 413
    10  libsqlite3.dylib                   0x00007fff97ea0fe8 sqlite3Prepare + 1032
    11  libsqlite3.dylib                   0x00007fff97ea0b23 sqlite3LockAndPrepare + 355
    12  libsqlite3.dylib                   0x00007fff97e9ff42 sqlite3_exec + 418
    13  com.apple.CFNetwork                0x00007fff99e2253a __CFURLCache::OpenDatabase() + 188
    14  com.apple.CFNetwork                0x00007fff99e22040 ProcessCacheTasks(__CFURLCache*, bool) + 265
    15  com.apple.CFNetwork                0x00007fff99e21a72 _ZL24_CFURLCacheTimerCallbackPv + 662
    16  libdispatch.dylib                  0x00007fff9728ea86 _dispatch_call_block_and_release + 18
    17  libdispatch.dylib                  0x00007fff972902d6 _dispatch_queue_drain + 264
    18  libdispatch.dylib                  0x00007fff97290132 _dispatch_queue_invoke + 54
    19  libdispatch.dylib                  0x00007fff9728f92c _dispatch_worker_thread2 + 198
    20  libsystem_c.dylib                  0x00007fff900fd3da _pthread_wqthread + 316
    21  libsystem_c.dylib                  0x00007fff900feb85 start_wqthread + 13
    Thread 6:: CoreAnimation render server
    0   libsystem_kernel.dylib             0x00007fff9a39267a mach_msg_trap + 10
    1   libsystem_kernel.dylib             0x00007fff9a391d71 mach_msg + 73
    2   com.apple.QuartzCore               0x00007fff950572d9 CA::Render::Server::server_thread(void*) + 184
    3   com.apple.QuartzCore               0x00007fff95057219 thread_fun + 24
    4   libsystem_c.dylib                  0x00007fff900fb8bf _pthread_start + 335
    5   libsystem_c.dylib                  0x00007fff900feb75 thread_start + 13
    Thread 0 crashed with X86 Thread State (64-bit):
      rax: 0x0000000000000000  rbx: 0x0000000000000006  rcx: 0x00007fff6cc8d418  rdx: 0x0000000000000000
      rdi: 0x000000000000060b  rsi: 0x0000000000000006  rbp: 0x00007fff6cc8d440  rsp: 0x00007fff6cc8d418
       r8: 0x00007fff7e006fb8   r9: 0x00007fff6cc8cea8  r10: 0x00007fff9a393d0a  r11: 0xffffff80002da8d0
      r12: 0x00007fb2e261f8a0  r13: 0x0000000000000004  r14: 0x00007fff7e009960  r15: 0x00007fff6cc8d590
      rip: 0x00007fff9a393ce2  rfl: 0x0000000000000246  cr2: 0x0000000102ef8000
    Logical CPU: 0

    Process:         Safari [386]
    Path:            /Applications/Safari.app/Contents/MacOS/Safari
    Identifier:      com.apple.Safari
    Version:         5.1.6 (7534.56.5)
    Build Info:      WebBrowser-7534056005000000~6
    Code Type:       X86-64 (Native)
    Parent Process:  launchd [147]
    Date/Time:       2012-09-03 19:41:08.591 -0700
    OS Version:      Mac OS X 10.7.4 (11E53)
    Report Version:  9
    Interval Since Last Report:          126027 sec
    Crashes Since Last Report:           24
    Per-App Interval Since Last Report:  577001 sec
    Per-App Crashes Since Last Report:   24
    Anonymous UUID:                      A6055379-1AD4-4DCF-9E47-C29E229C434B
    Crashed Thread:  0  Dispatch queue: com.apple.main-thread
    Exception Type:  EXC_CRASH (SIGABRT)
    Exception Codes: 0x0000000000000000, 0x0000000000000000
    Application Specific Information:
    objc[386]: garbage collection is OFF
    *** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'Invalid parameter not satisfying: (index >= 0) && (index < [_itemArray count])'
    *** First throw call stack:
    0   CoreFoundation                      0x00007fff99134f56 __exceptionPreprocess + 198
    1   libobjc.A.dylib                     0x00007fff91aa7d5e objc_exception_throw + 43
    2   CoreFoundation                      0x00007fff99134d8a +[NSException raise:format:arguments:] + 106
    3   Foundation                          0x00007fff94b9271f -[NSAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 169
    4   AppKit                              0x00007fff931e0cdf -[NSMenu itemAtIndex:] + 165
    5   AppKit                              0x00007fff931e0e38 -[NSMenu removeItemAtIndex:] + 63
    6   Safari                              0x000000010d0a3c2e -[AppController awakeFromNib] + 387
    7   CoreFoundation                      0x00007fff9912bfb1 -[NSObject performSelector:] + 49
    8   CoreFoundation                      0x00007fff9912bf32 -[NSSet makeObjectsPerformSelector:] + 274
    9   AppKit                              0x00007fff931c89ff -[NSIBObjectData nibInstantiateWithOwner:topLevelObjects:] + 1245
    10  AppKit                              0x00007fff931bef73 loadNib + 322
    11  AppKit                              0x00007fff931be470 +[NSBundle(NSNibLoading) _loadNibFile:nameTable:withZone:ownerBundle:] + 217
    12  AppKit                              0x00007fff931be38b +[NSBundle(NSNibLoading) loadNibFile:externalNameTable:withZone:] + 141
    13  AppKit                              0x00007fff931be2ce +[NSBundle(NSNibLoading) loadNibNamed:owner:] + 364
    14  AppKit                              0x00007fff9342f06f NSApplicationMain + 398
    15  Safari                              0x000000010d2a6806 SafariMain + 166
    16  Safari                              0x000000010d08ff24 Safari + 3876
    17  ???                                 0x0000000000000002 0x0 + 2
    terminate called throwing an exception
    abort() called
    Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
    0   libsystem_kernel.dylib             0x00007fff9a393ce2 __pthread_kill + 10
    1   libsystem_c.dylib                  0x00007fff900fd7d2 pthread_kill + 95
    2   libsystem_c.dylib                  0x00007fff900eea7a abort + 143
    3   libc++abi.dylib                    0x00007fff94a927bc abort_message + 214
    4   libc++abi.dylib                    0x00007fff94a8ffcf default_terminate() + 28
    5   libobjc.A.dylib                    0x00007fff91aa81b9 _objc_terminate + 94
    6   libc++abi.dylib                    0x00007fff94a90001 safe_handler_caller(void (*)()) + 11
    7   libc++abi.dylib                    0x00007fff94a9005c std::terminate() + 16
    8   libc++abi.dylib                    0x00007fff94a91152 __cxa_throw + 114
    9   libobjc.A.dylib                    0x00007fff91aa7e7a objc_exception_throw + 327
    10  com.apple.CoreFoundation           0x00007fff99134d8a +[NSException raise:format:arguments:] + 106
    11  com.apple.Foundation               0x00007fff94b9271f -[NSAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 169
    12  com.apple.AppKit                   0x00007fff931e0cdf -[NSMenu itemAtIndex:] + 165
    13  com.apple.AppKit                   0x00007fff931e0e38 -[NSMenu removeItemAtIndex:] + 63
    14  com.apple.Safari.framework         0x000000010d0a3c2e -[AppController awakeFromNib] + 387
    15  com.apple.CoreFoundation           0x00007fff9912bfb1 -[NSObject performSelector:] + 49
    16  com.apple.CoreFoundation           0x00007fff9912bf32 -[NSSet makeObjectsPerformSelector:] + 274
    17  com.apple.AppKit                   0x00007fff931c89ff -[NSIBObjectData nibInstantiateWithOwner:topLevelObjects:] + 1245
    18  com.apple.AppKit                   0x00007fff931bef73 loadNib + 322
    19  com.apple.AppKit                   0x00007fff931be470 +[NSBundle(NSNibLoading) _loadNibFile:nameTable:withZone:ownerBundle:] + 217
    20  com.apple.AppKit                   0x00007fff931be38b +[NSBundle(NSNibLoading) loadNibFile:externalNameTable:withZone:] + 141
    21  com.apple.AppKit                   0x00007fff931be2ce +[NSBundle(NSNibLoading) loadNibNamed:owner:] + 364
    22  com.apple.AppKit                   0x00007fff9342f06f NSApplicationMain + 398
    23  com.apple.Safari.framework         0x000000010d2a6806 SafariMain + 166
    24  com.apple.Safari                   0x000000010d08ff24 0x10d08f000 + 3876
    Thread 1:: Dispatch queue: com.apple.libdispatch-manager
    0   libsystem_kernel.dylib             0x00007fff9a3947e6 kevent + 10
    1   libdispatch.dylib                  0x00007fff9729078a _dispatch_mgr_invoke + 923
    2   libdispatch.dylib                  0x00007fff9728f31a _dispatch_mgr_thread + 54
    Thread 2:
    0   libsystem_kernel.dylib             0x00007fff9a394192 __workq_kernreturn + 10
    1   libsystem_c.dylib                  0x00007fff900fd594 _pthread_wqthread + 758
    2   libsystem_c.dylib                  0x00007fff900feb85 start_wqthread + 13
    Thread 3:
    0   libsystem_kernel.dylib             0x00007fff9a394192 __workq_kernreturn + 10
    1   libsystem_c.dylib                  0x00007fff900fd594 _pthread_wqthread + 758
    2   libsystem_c.dylib                  0x00007fff900feb85 start_wqthread + 13
    Thread 4:: WebCore: IconDatabase
    0   libsystem_kernel.dylib             0x00007fff9a394a8e pread + 10
    1   libsqlite3.dylib                   0x00007fff97e9dce5 unixRead + 69
    2   libsqlite3.dylib                   0x00007fff97ebf4f6 readDbPage + 102
    3   libsqlite3.dylib                   0x00007fff97ebdc9b sqlite3PagerAcquire + 315
    4   libsqlite3.dylib                   0x00007fff97eec872 moveToChild + 146
    5   libsqlite3.dylib                   0x00007fff97eeeb68 sqlite3BtreeNext + 600
    6   libsqlite3.dylib                   0x00007fff97ee7909 sqlite3VdbeExec + 41561
    7   libsqlite3.dylib                   0x00007fff97edca5b sqlite3_step + 1883
    8   com.apple.WebCore                  0x000000010e147eff WebCore::SQLiteStatement::step() + 63
    9   com.apple.WebCore                  0x000000010e1486cc WebCore::IconDatabase::performURLImport() + 908
    10  com.apple.WebCore                  0x000000010e146d3b WebCore::IconDatabase::iconDatabaseSyncThread() + 475
    11  com.apple.JavaScriptCore           0x000000010da8011f _ZN3WTFL19wtfThreadEntryPointEPv + 15
    12  libsystem_c.dylib                  0x00007fff900fb8bf _pthread_start + 335
    13  libsystem_c.dylib                  0x00007fff900feb75 thread_start + 13
    Thread 5:: Dispatch queue: com.apple.CFURLCACHE_work_queue
    0   libsystem_kernel.dylib             0x00007fff9a394a8e pread + 10
    1   libsqlite3.dylib                   0x00007fff97e9dce5 unixRead + 69
    2   libsqlite3.dylib                   0x00007fff97eba898 sqlite3PagerSharedLock + 2184
    3   libsqlite3.dylib                   0x00007fff97eb9a47 sqlite3BtreeBeginTrans + 1191
    4   libsqlite3.dylib                   0x00007fff97eb1427 sqlite3InitOne + 2391
    5   libsqlite3.dylib                   0x00007fff97eb0a44 sqlite3Init + 116
    6   libsqlite3.dylib                   0x00007fff97eabdcf sqlite3Pragma + 10287
    7   libsqlite3.dylib                   0x00007fff97ea3e4f yy_reduce + 3967
    8   libsqlite3.dylib                   0x00007fff97ea2a2d sqlite3Parser + 253
    9   libsqlite3.dylib                   0x00007fff97ea16fd sqlite3RunParser + 413
    10  libsqlite3.dylib                   0x00007fff97ea0fe8 sqlite3Prepare + 1032
    11  libsqlite3.dylib                   0x00007fff97ea0b23 sqlite3LockAndPrepare + 355
    12  libsqlite3.dylib                   0x00007fff97e9ff42 sqlite3_exec + 418
    13  com.apple.CFNetwork                0x00007fff99e2253a __CFURLCache::OpenDatabase() + 188
    14  com.apple.CFNetwork                0x00007fff99e22040 ProcessCacheTasks(__CFURLCache*, bool) + 265
    15  com.apple.CFNetwork                0x00007fff99e21a72 _ZL24_CFURLCacheTimerCallbackPv + 662
    16  libdispatch.dylib                  0x00007fff9728ea86 _dispatch_call_block_and_release + 18
    17  libdispatch.dylib                  0x00007fff972902d6 _dispatch_queue_drain + 264
    18  libdispatch.dylib                  0x00007fff97290132 _dispatch_queue_invoke + 54
    19  libdispatch.dylib                  0x00007fff9728f92c _dispatch_worker_thread2 + 198
    20  libsystem_c.dylib                  0x00007fff900fd3da _pthread_wqthread + 316
    21  libsystem_c.dylib                  0x00007fff900feb85 start_wqthread + 13
    Thread 6:: CoreAnimation render server
    0   libsystem_kernel.dylib             0x00007fff9a39267a mach_msg_trap + 10
    1   libsystem_kernel.dylib             0x00007fff9a391d71 mach_msg + 73
    2   com.apple.QuartzCore               0x00007fff950572d9 CA::Render::Server::server_thread(void*) + 184
    3   com.apple.QuartzCore               0x00007fff95057219 thread_fun + 24
    4   libsystem_c.dylib                  0x00007fff900fb8bf _pthread_start + 335
    5   libsystem_c.dylib                  0x00007fff900feb75 thread_start + 13
    Thread 0 crashed with X86 Thread State (64-bit):
      rax: 0x0000000000000000  rbx: 0x0000000000000006  rcx: 0x00007fff6cc8d418  rdx: 0x0000000000000000
      rdi: 0x000000000000060b  rsi: 0x0000000000000006  rbp: 0x00007fff6cc8d440  rsp: 0x00007fff6cc8d418
       r8: 0x00007fff7e006fb8   r9: 0x00007fff6cc8cea8  r10: 0x00007fff9a393d0a  r11: 0xffffff80002da8d0
      r12: 0x00007fb2e261f8a0  r13: 0x0000000000000004  r14: 0x00007fff7e009960  r15: 0x00007fff6cc8d590
      rip: 0x00007fff9a393ce2  rfl: 0x0000000000000246  cr2: 0x0000000102ef8000
    Logical CPU: 0

  • Remove caches file's automatically if you delete a folder from your drive???

    Gday,
    First off all sorry for my poor/bad English.
    When i remove/delete a folder in bridge, where will by the cache file of this folder??
    Does it also Remove/delete automatically, ????
    Or should I in the preferences box, tick on the (automatically Export Cache to folders when possible) option???
    Already many Thanks,
    Henry

    As the others say, no, the backup copy won't be deleted immediately, but it will eventually.
    If you want to delete all backups of a selected item, such as for space or security reasons, see #12 in Time Machine - Frequently Asked Questions.

  • Remove images from library without deleting referenced files

    Hi,
    I cannot find solution: how do I remove images from Aperture library completely (all versions, etc), but keep the referenced master files? (all my images are kept outside aperture lib, as referenced masters).
    If I delete all versions and projects, they go to Trash, and attempting to empty the Trash brings only two options: delete permanently and move to system Trash. But I do not want to touch the referenced masters in any way. Is there a way to keep them safe, while emptying Aperture of all references to those files?
    Thanks.

    If the originals are referenced when you empty the Aperture trash the confirm box will have a checkbox asking yf you also want to move the referenced originals to the system trash.
    If you do not select this option the referenced originals are left where they are. If you of not see this option in the confirmation box then the originals in the Trash are not referenced.

  • Extract thumbnail images from a cache file without originals?

    After an external drive crash, I'm left with only the Bridge (CS2) cache files for a folder full of images. Does anyone know a way to extract the thumbnails from the cache as jpgs or some other standalone format when you *don't* have the original image files? They would be low-res, but better than nothing. Thanks in advance.

    >>says that this export technique does not work, it produces a low res screen version of the file.
    Are you certain the original files were any better?
    My preferred method of doing this works well, but it takes a few extra steps. I'd make a high-res PDF out of the PM file, then pick apart the PDF to extract the graphics. Are the graphics raster or vector? If they're raster, you can use Acrobat's Touch-up Object tool to open them in Photoshop. If they're vector, you can open the PDF in Illustrator and save out the graphics from there.
    HTH

  • Lr 5.6 error message that reading preview cache failed and will correct when reopened; does not correct on reopening; removing preview.lrdata files allows LR to open but photos not shown; what action should I take next?

    Lr 5.6 error message that reading preview cache failed and will correct when reopened; does not correct on reopening; removing preview.lrdata files allows LR to open but photos not shown; what action should I take next?

    Yikesyou have helped me before and I thank you for that.  Funny how at the last resort I ask a question and then an hour later I fix something that has been broken for five days.  I got off on the wrong foot with Lightroom installation and I really stepped in it...a lot had to do with a bad hard drive and all that.  I still have remnants of catalogues etc so I am never quite sure where I am.  I ran a search and found more than one .lrdata files.  I finally got the right one to delete and I think I am okI'll be crying to you again if I am wrongall best, thanks again for your helpjim sterne

  • Messages Opening Image Cache Folder when Sending Files

    Messages / iChat seems to be opening my image cache folder every time I send an image to my contacts the image cache folder opens in Finder and stays open with the copied image. Is there a way to get rid of this? It's really annoying. It started happening after I updated to Mavericks.
    Thanks!

    Hi,
    I don't have an answer for this one.
    Are you finding those items are zipped before Sending ?
    Where are they from?
    I get them zipped when sending a pic dragged from a Browser or from iPhoto but not from the Desktop or a Finder window.
    10:44 pm      Tuesday; November 5, 2013
      iMac 2.5Ghz 5i 2011 (Mavericks 10.9)
     G4/1GhzDual MDD (Leopard 10.5.8)
     MacBookPro 2Gb (Snow Leopard 10.6.8)
     Mac OS X (10.6.8),
     Couple of iPhones and an iPad

  • Image Caching With JList

    Hi all, I need to know, how can I implement an Image Cache feature with a JList that is effective, ie. basic I would like the images to be stored in memory when the list is visible (done that already using a WeakHashMap<String, Icon>) and removed from memory when the JList is not displayed.
    Currently I use the following code section, to try and remove the data from memory, seems not work according to task manager. Sorry I cannot seem to come up with a good SSCCE since I'm not exactly sure how to make an example that loads images. Any suggestion with that?
    WeakHashMap<String,Icon> icons = new WeakHashMap<String,Icon>();
    JList list = new JList(); // something like this in actual code
    public void startClearTimer() {
        new javax.swing.Timer( 30000, new ActionListener() {
            public void actionPerformed(ActionEvent e) {
                if(!list.isShowing() && icons.size() > 0 ) {
                    resetIconCache();
                    System.out.println("Icons Cleared");
                    System.gc();
                    //((javax.swing.Timer)e.getSource()).stop();
        }).start();
    public void resetIconCache() {
        if(icons == null) {
            return;
        Iterator<Icon> images = icons.values().iterator();
        while(images.hasNext()) {
            ImageIcon icon = (ImageIcon)images.next();
            icon.getImage().flush(); // smoke but no cigar
            icon = null;
        icons.clear();
        icons = new WeakHashMap<String,Icon>();
    }This code is used in a ListCellRenderer, which loads the images, scales them, caches them in memory so the repaints are faster and displays them along side some JLabels.
    So basically how can I load the images in memory and release the resources used when the images are not required?
    ICE

    you can't be cleverer than JVM for memory usage.
    Of course you can, because the point of caching is that it requires (or at the very least is optimised by) some understanding of the use case. JVMs are somewhat unlikely to predict how any given set of users will use any given application, nor are they capable of factoring in the cost of downloading (or otherwise obtaining) data which has been freed from memory. To a JVM, a lump of voidable memory is no different to any other.
    Take an example of an applet (which is limited to 96Mb of heap) which browses images on a server. Let's say it's looking at images which occupy 20Mb of memory each (far from unreasonable) in memory. They might each be 1Mb or so in compressed file size, which is an appreciable delay in download time.
    Each time the user switches between images, the applet will probably want to implement a policy that says "that last image should be kept in memory if possible, since the user might return to it and they won't want another long delay to load it, but if you run out of memory downloading the next image, feel free to discard the first, because the next is more important." (Furthermore, your workflow might permit you to prioritise images.)
    In order to indicate to the JVM that the first image is disposable, you must clear all strong references to it. However, this simply makes it eligible for garbage collection: simple as that. You have no control over whether the garbage collector will clean that image data (which takes several seconds to retrieve) or a bunch of other data which is completely useless or can be recreated in milliseconds. Also note that in practice, weak and soft references do not actually encourage the GC to retain the data: it is cleared long before the memory is actually required.
    Note, too, that the suggestion of tweaking the heap allocation is no use for an applet (unless you have a very small, very knowledgeable and very tolerant user base).

  • JE as Image Cache

    Folks,
    We're considering using JE as an image cache for a large(ish) number of small(ish) images. The question is whether or not JE would be fit for this particular use. The requirements are simple: store a single Java object via DPL in the form:
    class Image{
    @PrimaryIndex
    String uuid;
    @SecondaryIndex(...)
    Date lastModified;
    @SecondaryIndex(...)
    Date expires;
    byte[] data;
    We expect to store 50K or so images with data[] sizes ranging from 1k to 50k. Any reasons why JE might not be a fit? We've stored blocks of XML in the past without issue, so don't expect issues here.
    Regards,
    -tyson

    Tyson,
    You're probably familiar with this already, but JE is agnostic about data types at the actual storage level. Only the DPL layer understands what type the data is. So in this case, the major factor to consider is the size of the data.
    We have certainly heard of uses cases with data in the 1 - 50K range, and it should be possible, but I'll explain the factors to consider in terms of the size of the data.
    1. Because of JE's append only storage architecture, an update to a record is a new, fully size copy of the record. So if a large data record is updated a lot, the log does grow. Of course, those older versions are obsolete, and the log cleaner removes them, but it results in log file growth and compression (cleaning) in larger degrees of granularity.
    2. In general, JE pulls data records in their entirety into cache. So a large data record takes more room, the cache fits fewer data records, and there may be more eviction activity going on to maintain the cache. One exception is the "Partial" option when fetching data entries, described in the Cursor javadoc under "Using Partial DatabaseEntry Parameters" here: http://www.oracle.com/technology/documentation/berkeley-db/je/java/com/sleepycat/je/Cursor.html. It lets you fetch only the key portion of a data record and avoid pulling the data portion into the cache, when using READ_UNCOMMMITED, and can be useful in some cases.
    3. We don't yet provide any streaming APIs, which would be handy for really large records.
    That's what I can think of! Maybe folks who have been storing large records can speak to their experience. But we do know that people do store records that large in JE.
    Regards,
    Linda

  • CS2: Adobe Bridge Cache File on Desktop...Why?

    For some unknown reason...CS2 has started placing "Adobe Bridge Cache" file shortcuts on my desktop. When I click on one, I receive a Win XP error message that says the file .bc is unkown and can't be opened.
    These shortcuts have never appeared before. Now the simple act of opening Bridge and looking at jpeg files seems to initiate it.
    Questions: Why is PS doing this? Do I need to pay attention to it? If not, how do I stop PS from cluttering up my desktop.
    Thanks!
    Ed

    Ed,
    Yes you can. The cache facilitates the quick display of images in a folder.
    When there's no cache, Bridge has to render thumbnails from every image file upon viewing a folder's contents. This can take a couple of minutes.
    Rob
    P.S.
    >I do, indeed, have image files in a folder on my desktop.
    This would mean that there is a cache inside that folder, *not* on the desktop itself.

  • Image cache not working with Firefox and apex

    Hi,
    I'd like to cache all my images to save page rendering time and bandwidth because my images are all static and never change.
    I use the John Scott's caching technique Link: [http://jes.blogs.shellprompt.net/2007/05/18/apex-delivering-pages-in-3-seconds-or-less/], in a few words this technique consists of adding a header line "Expires: date in the future" in the http response.
    It works very well in IE, the images are cached and the same image can be accessed several times (within the same session or in different sessions) without issuing an http request to the server each time.
    with Firefox it does not work, the same image is asked again and again to the server (i'm using FF 3.5 and APEX 3.2).
    - Is it a date format problem? no, because when i type about:cache in FF, i can find my image in the cache with an expire date in the future.
    The weird thing here is that the counter is incremented each time u request the image, so FF knows it is in the cache and even if the expire date is in the future, FF asks it again to the server.
    - Is it a FF bug? If u read the http specs or if u google a little, u can come to the conclusion that FF does not follow the standards,
    but... images.google.com for example manages to get its images cached with FF.
    They use an http response header "cache-control: public, max-age=604800".
    I tried the same and all kinds of combinations but without success.
    When i compare my image with the one from google in the FF cache, they both have the same attributes.
    - It's not an apex issue neither because it works with IE, most probably an incompatibility between apex and FF?
    Maybe the use of cookie? or the http request (not the response) containing "cache-control: max-age=0"?
    I've found so far 2 half solutions:
    1) use ETag and modified date, see the Tyler Muth's note Link: [http://tylermuth.wordpress.com/2008/02/04/image-caching-in-plsql-applications/].
    with this technique FF continues to send request each time but the answer is shorter because it's just a "304 not modified" instead of "200 OK" (200 response is bigger as it contains the image).
    it's better than nothing but you still have 1 request + 1 response for nothing.
    Another problem is that you need SYS access to implement this, which is not possible on an hosted server. (note that for images from the file system it is already foreseen by apex 3.1, Tyler's note is for images from the db)
    2) if you preload the image (using myimage=new Image();myimage.src='...';), then there is max 1 request per browser session.
    There are 2 minor issues here:
    - no caching across sessions
    - if u don't want to preload all the images (example a page with lots of thumbnails, when user clicks it show a bigger image, in that case the thumbnails can be preloaded but overkill for the big images), then you need to load the image, wait until the image has loaded before displaying it, it does not slow down the execution, but requires some extra JS.
    I'm not asking anyone to investigate it, i can live with the 2 workarounds,
    but just in case someone encountered the same problem and already fixed it.
    Let me know if u managed to use the John Scott's technique with Firefox. (U can use Firebug to see the http traffic)
    Thx
    Tim

    Hi Anshul, hope these help. Let me know if you need to see anything else.
    Best,
    Menu Settings:
    Tab Hyperlink:
    Label Text with with hyper link option not available (works as a hyperlink in chrome and IE though):
    Thanks for the help in advance!

  • Bridge cache files for different bridge versions

    Bridge with CS2 and now CS3 is a superb image browsing tool - particularly when the cache files are within the directory containing the images. It would be very very useful if new versions of bridge could read older version cache files.
    If a user creates cache files in a disk directory and then backs up the directory to a DVD for archival purposes, it would be very valuable to allow the "current version" of bridge to properly read the "old version" DVD archived bridge files. This would add greatly to the browsing speed of the DVD archive - since a new cache file will not be needed (or desired).
    In addition, if previous versions of the cache files are on a hard drive, the ability to process the old version files would allow bridge to work more rapidly when browsing images. Of course, there are problems if the user attempts to update information that is version specific, however I am sure there are sane solutions to the problem.
    tony

    Not having to use a centralised cache was one of Bridge 1.0's strengths.
    Not sure about the current versions insistence on centralising with the option of distributed as well or why the cache type as changed. A pain from an archival point of view as I used distibuted cache, which is now a waste of bytes.

  • How do I remove images from aperture?

    Totally new to apple and aperture so I apologise if this seems like a somewhat noob question but how do I remove images from aperture (using the latest version, 3.4.1)? Coming from a PC and using lightroom I'm used to being able to remove images in two ways:
    - removing the image from the "library", so that it no longer shows up in the program at all but is still on your hard drive (when I say removing it from the program entirely, I mean entirely, i.e. not sitting in a trash can or some other place where it's still taking up memory)
    - deleting the original image off the hard drive
    Is it possible to do either of these things in aperture, on both just a single image or a selection of multiple images, and if so how? I've tried googling this already and am getting a bunch of mixed solutions, none of which have really worked so far, so any answers would be appreciated. Thanks!

    The answer partially depends on whether you have a managed or referenced library. Since you're totally new to Aperture, I'm assuming you have a managed library since that's the default.
    FYI: Managed means Aperture handles image files and places them inside the library file. Referenced means you manage the image files and Aperture only points to (references) them.
    For a managed library, select an image you want to delete. Type command-delete. (That's the reverse delete key next to the "=" key). (You can also right-click an image and choose Delete Version) That will remove the images from their Project and place in the Aperture Trash. They're still taking up space in the Trash. If you really want them gone for good, right-click the Trash in the library pane and select Empty Trash. Poof.
    For a reference library, I forgot the exact details since I don't use this type of library, but you'll be asked (or can check a box) to delete the original file from the disk.

  • How can I get rid of cache files?

    Premiere Pro, can't find cache files on Mac, not in the common folder, clean doesn't work, I know there are Gigs of them on my drive.  How can I get rid of them?
    I started a premiere project I had worked on before using an external drive but forgot to hook up the external drive.  In a few minutes, Premiere loaded 5 gigs of cache files onto my macbook pro drive OSX 10.8.6.  I tried the following to free up the space:
    Tried to "clean" the cache folder before switch it to the external drive - this only removed a small amount of the 5 gigs created
    Tried to find files in the Application Support/Adobe/common folder - no cache files found
    Tried searching the web for answers - no new info
    Tried searching my drive for the files - can't find them
    Tried restarting the MacBook and Premiere with and without the external drive - no luck
    Now what?
    Message was edited by: Kevin Monahan
    Reason: please make a shorter and more concise title next time. Thanks.

    First off, exactly which version of Premiere are you running? Not simply PPro CC or CC2014 but the version number shown in the About box.
    I'm not clear whether you're saying that Premiere can't find the cache files or that you can't find them.
    I gather that you're referring to the Clean button on the Media tab of the Preferences dialog, which is also where you set the path for the cache files.
    Are you sure you're looking in the correct Library--not the one that's readily accessible under Macintosh HD but the one that Apple, in it's infinite wisdom, hides from users. To access it, open the Go menu and press Option.

Maybe you are looking for