Closed Bug 306069 Opened 19 years ago Closed 18 years ago

Script warning launching Mozilla Thunderbird 1.06 (20050716) Windows

Categories

(Thunderbird :: General, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: josephrot, Assigned: mscott)

Details

User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET CLR 1.1.4322)
Build Identifier: Thunderbird 1.06 (20050716) Windows

Many times, not continually though, when launching Mozilla Thunderbird 1.06 
(20050716) Windows:

"  Script warning

A script on this page is causing mozilla to run slowly. If it continues to 
run, your computer may become unresponsive.
Do you want to abort the script? "

User Comments: What's causing this, how to STOP it from doing this. 
What script?  where?  what's the name?

The MOST annoying and wasting everyone's time:

No programmer thought of advising us WHICH "script" is causing or calling 
this, so we users can ID it, take action, and help BugZilla even.


Reproducible: Sometimes

Steps to Reproduce:
1.Run Thunderbird.
2.Script error shows up in upper left of screen in a dialog box.
3.

Actual Results:  
Cancel or dismiss the script warning, and Thunderbird appears to load and run 
normally.

Expected Results:  
The MOST annoying and wasting everyone's time:

No programmer thought of advising us WHICH "script" is causing or calling 
this, so we users can ID it, take action, and help BugZilla even.


PLEASE communicate with me via Skype ( josephrot )
or Email:  josephrot@windowgroup.com
Do you have any extensions installed? May be one of them...
In time order, oldest step first:

1. Yes, I did have extensions installed, and I allowed the then older version of TBird to lock OUT extensions that it felt would not work.

2. Problem resolved itself after Updating to eventual 1.5.0.10.

Thank you.
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
-> changed to worksforme because no patch included here.
Resolution: FIXED → WORKSFORME
You need to log in before you can comment on or make changes to this bug.