Deleting messages causes "Unresponsive script" error

[Ryan1]

When I put checkmarks next to messages, and then click the "Delete" button on the toolbar, I often get an "Unresponsive script" error.

It doesn't happen every time, but it does happen often.

At first it happened several times (but not every time) when I searched through a few thousand messages, then checked the few hundred messages that met the search criteria and tried to delete them. Sometimes it deleted a few "100, 200, etc." and then ended with an error before finishing. Sometimes it seemed to stop with the error as soon as I clicked "Delete."

Just now it happened when I checked only one message and tried to delete it. So it doesn't look like the number of messages is necessarily the issue.

I attached a screen shot of the error message in the hope that it will help.

[Ryan1]

Here is some more information that I think may be related to this bug.

After I installed Zimbra, I noticed that something was causing an error when I shut down windows. The error messages flashes on screen for only a moment immediately before windows shuts down, so I have not been able to capture it. But I did see the file name of the file it shows having the problem.

It's cscript.exe ... since this bug involves something with scripts, I assume this is related... although I can't be sure of course. However, it is a bug that seems to have been introduced after installing Zimbra, that I am sure of.

BTW ... the OS is Windows XP SP3 and Zimbra v7.01.

Sorry! Just realized I should have posted this thread in the errors forum but posted it here instead by mistake.

[Ryan1]

I have not tried anything that would trigger the "unresponsive script" error message I posted above, so I don't know if that is still present. I will try it out and report back. I will see if there are any Zimbra updates first and install if there are.

However, I am still getting the cscript error message when I close Windows XP. That problem is still present. But other than getting my blood pressure up a few points because it makes the dreaded Windows error sound, it really isn't much of any kind of obvious problem. Whether it causes any other kind of damage, I can't say... I assume probably not. So it's disturbing, but not intolerable.

[Ryan1]

Yes, still getting the unresponsive script errors.

It should be easy to reproduce. But you need to have lots of messages.

Do a search through a few thousand messages that returns at least say 1,000 of them. Then select those found messages and press the delete key to delete them to the trash can. You will probably have to do it in batches as Zimbra seems to limit loading to 400 at a time.

Now select the trash can and empty it.

If you have not gotten the unresponsive script error by now, keep repeating this kind of thing. Searches that return a lot of hits, deleting those hits a lot at a time and emptying the trash. For me it triggers the error nearly every time.

[bjquinn]

I think a problem I'm having may be related to yours. See --

Script stack space quota is exhausted

Before I get the script stack space quota exhausted error, I get the unresponsive script error you're getting. If I click "continue" then I get the stack space quota exhausted error. I don't specifically get this error when deleting messages, but I get a few moments after ZD loads, when doing searches, etc.

I have a ton of messages in this particular account, 10GB of email and ~90k messages. I've tracked my particular problem down to a memory limitation in Firefox 3.0 (which I believe is what Zimbra Desktop is based on -- see https://bugzilla.mozilla.org/show_bug.cgi?id=420869), which limitation may have been raised in later versions of Firefox, but I don't know what version ZD is based on now, especially since Mozilla has discontinued Prism. At any rate, the setting appears not to be configurable by the end user.

[brickjenks101]

this may be related

https://bugzilla.mozilla.org/show_bug.cgi?id=644241

[Ryan1]

Hmmmm...

Seems like it may be related, but I'm not sure. Definitely seems like something is putting too many of something into something before another thing is ready to deal with them.

How's that for some fancy tech talk?

So I am still having these two problems:

1. The unresponsive script errors described above that seem to happen with various types of operations most often in search related things with large numbers of messages.

2. The cscript.exe error dialog that I get when I shut down Windows pretty much any time that I used ZD during that Windows session. Seems pretty harmless, but obviously shouldn't be happening.

If someone from ZD is reading this, can you tell me if there is anything I can do to help you get to the bottom of these? (since I know you have nothing else to do! ha ha ha!)

Thanks!

[brickjenks101]

I get that same error so this forum post should be merged with this one Script stack space quota is exhausted.

i get the csscript.exe error as well, also I installed Zimbra web client in Mozilla Prism and got the stack space quota exhausted error. I installed the Zimbra web client in web runner and have not received the error yet...

Mozilla Prism is no longer being developed (see Warning https://wiki.mozilla.org/Prism), the Mozilla project is now Chromeless (https://developer.mozilla.org/en/Chromeless). Web Runner (http://www.salsitasoft.com/webrunner/) is taking over Prism.

My theory is Web Runner uses the latest version of the Mozilla software that handles JavaScript ( this software has the stack space quota on JavaScript workers removed in accordance with the Mozilla bug report 644241.) Prism uses the older version of the Mozilla software that handles JavaScript workers (this software has the stack space quota on JavaScript workers imposed). I believe Zimbra Desktop is using the latest version of the Prism software which, unfortunately is no longer in development and therefore has not updated the aspect of the software that handles JavaScript workers.

the bug report on JavaScript stack space quota is here https://bugzilla.mozilla.org/show_bug.cgi?id=644241.

the bug report on JavaScript web workers and stack space quota is here https://bugzilla.mozilla.org/show_bug.cgi?id=653967