[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4668: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3815)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4670: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3815)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4671: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3815)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4672: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3815)
Tao Effect Forums • View topic - ScriptManager busy, avoiding deadlock
Page 1 of 1

ScriptManager busy, avoiding deadlock

PostPosted: Sun Sep 13, 2009 3:41 pm
by 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

Re: ScriptManager busy, avoiding deadlock

PostPosted: Sun Sep 13, 2009 5:03 pm
by greg
Hi nwi,

We've noticed this problem as well in Snow Leopard and we've fixed it for the next release of Espionage (which should be arriving sometime this month), however what you can do in the meantime to limit its impact is temporarily disable the "Lock On Quit" option for all of the application associations that you have setup. You can do this from within Espionage by selecting a folder and clicking "Edit Application Associations". You may wish to turn on your sleep/screen saver password in the Security System Preferences after doing so.

Best regards,
Greg, Tao Effect

Re: ScriptManager busy, avoiding deadlock

PostPosted: Mon Sep 14, 2009 5:55 am
by 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

Re: ScriptManager busy, avoiding deadlock

PostPosted: Fri Sep 18, 2009 6:24 pm
by 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

Re: ScriptManager busy, avoiding deadlock

PostPosted: Sun Sep 20, 2009 5:23 pm
by greg
Hey nwi,

Just fyi, you'll never see that message in the console again as in 2.5 that code has been completely removed & rewritten. ;-)

Cheers,
Greg, Tao Effect

Re: ScriptManager busy, avoiding deadlock

PostPosted: Sun Sep 20, 2009 7:58 pm
by nwi
Ok thanks greg.

Regards
nwi