Author Topic: ImageIntegration Data Cache Corrupted (Mac OS X)  (Read 863 times)

Offline james7

  • Member
  • *
  • Posts: 53
    • View Profile
ImageIntegration Data Cache Corrupted (Mac OS X)
« on: 2013 November 13 16:14:08 »
I think the data cache for ImageIntegration is corrupted on my system and I seem to be having problems running integrations because of this problem. I also can't access the ImageIntegration preferences to try and clear the cache, since PI just reports and error or hangs if I try to bring up the preferences for ImageIntegration. Is there any way to manual delete this cache? Is it a separate file and where is it located under Mac OS X?

I'm having this problem on BOTH installations of PixInsight (v1.7 and v1.8). Under v1.7 it reports a cache corruption error, but under v1.8 it just hangs when I try to view the preferences or attempt an integration.

Offline james7

  • Member
  • *
  • Posts: 53
    • View Profile
Re: ImageIntegration Data Cache Corrupted (Mac OS X)
« Reply #1 on: 2013 November 13 17:05:34 »
So, I did the following to reset PixInsight and the problem is fixed (I guess this either deleted the cache or changed some internal setting to fix the problem I was having).

To Reset PixInsight settings (Mac OS X): Right-click the PixInsight.app application, press the Ctrl key and hold it pressed while you select "Open" from the context menu. Answer yes on the subsequent confirmation dialog box.

A further note, this also solved an issue I was having with very slow launch and quit from PI. Over the last several weeks it was taking PI several minutes to actually quit, even if I had done nothing within the application itself (other than open and then quit). It appeared to be writing to disk as it attempted to quit, the data rate for the write to disk was slow and PI was using 100% of one core on my quad-core Mac. Anyway this reset seemed to fix those problems also (I'm pretty sure it was the ImageIntegration cache that was causing the problem, it probably had a fair amount of data and may have even been corrupted for a few weeks until it finally failed today).
« Last Edit: 2013 November 13 19:17:24 by james7 »