Repeatedly receive "Script failed to terminate" messages, computer slow

RESOLVED INCOMPLETE

Status

()

RESOLVED INCOMPLETE
6 years ago
3 years ago

People

(Reporter: dbd400, Unassigned)

Tracking

15 Branch
x86_64
Windows 7
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

6 years ago
User Agent: Opera/9.80 (Windows NT 6.1; WOW64; U; en) Presto/2.10.289 Version/12.02

Steps to reproduce:

At first, I deleted all add-ons which I thought could conceivably cause the problem, and which were not crucial.  This helped somewhat and reduced the incidence. The text detail accompanying the message helped to locate the problem. I had thought it was cured, although the machine did speed up somewhat, it continued slower than it should be.


Actual results:

Now, I have received once again the "script failed to terminate" message, indicating looping. The accompanying text is: Script: resource://gre/modules/XPCOMUtils.jsm:323, which is identified as belonging to XPCOM utilities within mozilla.
For what it is worth, I am sending it along. I do not yet know what triggers this. The CPU is a Q6600 quad, fast enough that delays are quite obvious. The OS is W7, though that should not matter. The detailed version is 15.0.1. I am not clear as to just when it started. Sorry I cannot supply more info, but would be happy to if I know what.
User Agent 	Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:46.0) Gecko/20100101 Firefox/46.0
Version 	46.0a1
Build ID 	20160112030207
Channel 	nightly

Thank you for taking time to report this.
Are you still able to reproduce this in the latest version ? Can you give more detail on how to reproduce this?
Component: Untriaged → General
Flags: needinfo?(dbd400)
Product: Firefox → Core
Closing this as incomplete due to lack response from the reporter. 
Feel free to reopen the bug if it reproduces in the latest versions. Thanks
Status: UNCONFIRMED → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → INCOMPLETE

Updated

3 years ago
Flags: needinfo?(dbd400)
You need to log in before you can comment on or make changes to this bug.