Messages

Hi Mike,

I've seen your response and proceeded with the steps to re-install iSpy, nevertheless as you suspected, this has not solved the performance issue with Postbox.

Regards
Nicolas

I ran the diagnostic tool as requested and I've submitted the report. Please let me know what's the outcome.

Regards
Nicolas

Hi Scott,

Thank you for sharing the email from Thunderbird. We'll investigate into this.

My understanding is that it may be related to the mail indexing, both encryption and mail indexing combined can slow down the overall system performance.

I have an SSD and I have noticed no performance slowdown with Sparrow, so it is likely that the slower the hard drive, the more noticeable the performance degradation is with Espionage.

If we find that it is not compatible, we'll consider the request to remove it.

Thank you once again for your help.

I'm nwi (Nicolas), not Scott ;-)
Scott is the engineer from Postbox who responded to me.

I have personally tested Postbox with Espionage on my MacBook Pro with an OWC SSD drive and I have noticed this performance issue so much that I could not use Postbox at all. Therefore, SSD drive does not improve anything on my side.

Regards
Nicolas

FYI, I've contacted the Postbox support for this performance issue between Postbox and Espionage, this looks to be the same issue for Thunderbird I think. Here is their response:

---start---
Hi,

Postbox is not compatible with Espionage. Running Postbox on an encrypted profile folder will cause Postbox to be very slow as the disk IO becomes very slow on the system. We don't recommend this.

Cheers,

-Scott
---end---

Therefore, I think the Postbox template in Espionage should be removed, if the Postbox team confirms that it is not compatible with Espionage.

I'm testing Postbox and it was working fine until I encrypted it with Espionage. Now that Postbox is encrypted, it is slowing down to the point that makes Postbox unusable. I cannot use Espionage with Postbox, this is likely the same issue others encountered with Thunderbird.

Ok thanks greg.

Regards
nwi

Yes, this works much better now ;-) I didn't think about the whitelist, as I added Finder into this list a while back (before the latest upgrade).

Thanks
nwi

This happens all the time. BTW, this morning I rebooted my laptop and I've tested again right now. The issue still happens all the time.
I've sent the diagnostic data right now.

nwi

Hi Greg,

Actually this happens when I have no finder window open.

Regards
nwi

Hi,

I've just installed 2.5, as the installer has not requested to reboot the laptop, I have not restarted it.
I've enabled the Global Status Menu and tested the lock/unlock function. I've locked one folder, this succeeded. Now I'm trying to unlock this same folder using the Global Status Menu. This folder appears under the "Locked Folders" section, I'm selecting it and choose "Unlock". Interestingly, Espionage doesn't unlock the folder, rather it open the folder where it is. In other words, it seems that the function "Unlock" under the Global Status Menu does the same as "Reveal in Finder" instead of unlocking the folder.

Am I doing anything wrong ?

Thanks
nwi

I've now updated to 2.5 and will monitor it for a number of days to see if this issue happens again.

Regards
nwi

Hi Greg,

Thanks for responding and confirming that this is an issue which will be fixed in the next release.
I'm looking forward to updating my version.

Regards
nwi

Hi,

I'm running Espionage 2.1.1 with Mac OS 10.6. The last 2 days it happened twice that Espionage stopped to respond and consequently the folders could not be encrypted and/or unencrypted. This happened again right now, I've tried opening Mail.app and it didn't open. Then I tried opening Espionage but it hung and Activity Monitor indicated that Espionage was not responding. Therefore, I've looked at the console logs and found that the EspionageHelper was not working properly:

13/09/2009 17:23:50   EspionageHelper[240]   WARN (event_handler_for_assoc:2020): ScriptManager busy, avoiding deadlock

Therefore, I've killed EspionageHelper and manually restarted it which solved the issue. However I'm wondering why this happens while I've never had such issue with Mac OS 10.5.

Any idea ?

Thanks