Script Problem

[David C. Kifer]

I'm using TB 31.4.0 in Win XP.

For some time I've been seeing this message pop-up frequently:

"Unresponsive Script
A script on this page may be busy, or it may have stopped responding. You can stop the script now,
or you can continue to see if the script will complete.

Script: chrome://messenger/content/toolbarIconColor.js:55"

with a choice of "continue" or "stop".

Another one that appears not quite so often is:

"Script: chrome://messenger/content/folderPane.js:503"

I have been unable to determine what either one is, what is causing it or how to fix it, even
looking for it with Google. It also tends to lock up my system for a period from seconds to minutes,
during which nothing works. Then it will "unfreeze" until the next time, which might be ten minutes
or the next day.

What does the script do? What breaks it to cause the warning? How can I get rid of it or stop the break?

I do not, have never used "messenger" or "chat", if this is coming from that.

Any suggestions? Thanks.

--
Dave
"Tam multi libri, tam breve tempus!"
(Et brevis pecunia.) [Et breve spatium.]

[Ron K.]

First of all, TB has not supported running of external scripts since TB3.
These are scripts used internally to run functions of the program. The
first error is one effecting the toolbar region of the GUI. The second
effects layout of the folderpane.

If you can determine a way these errors are reproducible it would aid a
Dev to trouble shoot and fix the cause. It may be a platform unique issue,
since your the first person I have seen raise this issue. There may be a
compressed archive reading problem.

--
Ron K.
Who is General Failure, and why is he searching my HDD?
Kernel Restore reported Major Error used BSOD to msg the enemy!

[David C. Kifer]

On 1/24/2015 18:23 PM, Ron K. wrote:
> David C. Kifer wrote on 1/24/2015 2:04 PM:
>> I'm using TB 31.4.0 in Win XP.
>>
>> For some time I've been seeing this message pop-up frequently:
>>
>> "Unresponsive Script
>> A script on this page may be busy, or it may have stopped responding. You
>> can stop the script now, or you can continue to see if the script will
>> complete.
>>
>> Script: chrome://messenger/content/toolbarIconColor.js:55"
>>
>> with a choice of "continue" or "stop".
>>
>> Another one that appears not quite so often is:
>>
>> "Script: chrome://messenger/content/folderPane.js:503"
>>
>> I have been unable to determine what either one is, what is causing it or
>> how to fix it, even looking for it with Google. It also tends to lock up
>> my system for a period from seconds to minutes, during which nothing
>> works. Then it will "unfreeze" until the next time, which might be ten
>> minutes or the next day.
>>
>> What does the script do? What breaks it to cause the warning? How can I
>> get rid of it or stop the break?
>>
>> I do not, have never used "messenger" or "chat", if this is coming from that.
>>
>> Any suggestions? Thanks.
>>
>
> First of all, TB has not supported running of external scripts since TB3. These are scripts used
> internally to run functions of the program. The first error is one effecting the toolbar region of
> the GUI. The second effects layout of the folderpane.

Thanks for the Reply.

So these are scripts built into Thunderbird? I have noticed no changes, before/during/after the
message appears, in either the toolbar or the folderpane.

> If you can determine a way these errors are reproducible it would aid a Dev to trouble shoot and fix
> the cause. It may be a platform unique issue, since your the first person I have seen raise this
> issue. There may be a compressed archive reading problem.

I do not use the "archive" function of TB. Is there a compression I'm unaware of in the "usual"
folders -- Inbox/Draft/etc.?

Three other messages I have seen but once or twice, if they may point to something:

Script: chrome://calendar/content/calendar-invitations-manager.js:22

Script: chrome://sendlater3/content/backgrounding.js:857

Script: chrome://global/content/bindings/progressmeter.xml:26

I will try harder to pin down what might be happening just before these messages appear. If I can,
I'll return with details.
As mentioned above, many of the warnings appear when I am not actively using TB, while it's open but
in the background.

[Ron K.]

During the early years of development, Mozilla installed all the code
modules in a folder tree. As FF and TB matured and access to the modules
was not important to end users, the files were packaged into a single file
which is named omni.ja. This file was processed into a compressed archive
format. All of the file paths you listed are for script files residing
within the omni.ja file.

What some cases of error messages signal is the code was expecting a
result at the stated error point and the action was wrong or missing.
Having an error handler step in then can prevent the application from
crashing on non-critical errors.

[Wayne]

The most common cause of Unresponsive Script is not a script problem per
se, but rather some general performance problem not related to the
script - something in excess of 50%. In other words, the script is the
victim of someone else's deeds.

So unless you have very specific steps that reproduce the problem
(deleting messages for example) and always point to the same script,
then the first order of business is to determine if the cause may be an
addon, or some other program, which is where
https://wiki.mozilla.org/Thunderbird:Testing:Memory_Usage_Problems can help.

[David C. Kifer]

Thanks. I'll see what I can find there.

[andym...@gmail.com]

I get this error message as well. Using TB 31.7.0 with Vista and SP2
Script: chrome://messenger/content/toolbarIconColor.js:55
It locks up everything for minutes at a time.