ค้นหาฝ่ายสนับสนุน

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

เรียนรู้เพิ่มเติม

Getting Java error in NewEgg on version 42

  • 2 การตอบกลับ
  • 2 คนมีปัญหานี้
  • 3 ครั้งที่ดู
  • ตอบกลับล่าสุดโดย illriginalized

more options

Receiving an error every time I click on any item in Newegg.com

The error is:

A script on this page may be busy, or it may have stopped responding. You can stop the script now, open the script in the debugger, or let the script continue.

Script: resource://gre/modules/commonj…ery/data/includes/page_info.js:62


I've attached the screen shot of the error as well.

Receiving an error every time I click on any item in Newegg.com The error is: A script on this page may be busy, or it may have stopped responding. You can stop the script now, open the script in the debugger, or let the script continue. Script: resource://gre/modules/commonj…ery/data/includes/page_info.js:62 I've attached the screen shot of the error as well.
ภาพหน้าจอที่แนบมา

วิธีแก้ปัญหาที่เลือก

Figured it out. It was the latest Ghostery. Just received an update a two~four days ago or so and that's been the culprit.

อ่านคำตอบนี้ในบริบท 👍 0

การตอบกลับทั้งหมด (2)

more options

Java and JavaScript are different languages. To avoid confusion, see:


This issue can be caused by an extension that isn't working properly.

Start Firefox in Safe Mode to check if one of the extensions (Firefox menu button/Tools > Add-ons > Extensions) or if hardware acceleration is causing the problem.

  • Switch to the DEFAULT theme: Firefox menu button/Tools > Add-ons > Appearance
  • Do NOT click the Reset button on the Safe Mode start window

You can check for issues caused by plugins and set plugins to "Ask to Activate" on the "Firefox menu button/Tools > Add-ons > Plugins" page.

  • plugins are not affected by Firefox Safe Mode
more options

วิธีแก้ปัญหาที่เลือก

Figured it out. It was the latest Ghostery. Just received an update a two~four days ago or so and that's been the culprit.