X
Tap here to go to the mobile version of the site.

Support Forum

Why is an unresponsive script referencing chrome?

Posted

I uninstalled the Chrome browser from my Raspberry Pi. But after weeks of running with FireFox (Quantum ESR 68.4.1esr (32 bit)). on the same url, suddenly I see: "raspberry pi warning unresponsive script chrome://global/content/elements/button.js:297" I really was hoping I got google out of just one little corner of my life. The url was for my security system (OpenHAB) on this Pi and nobody touched the keyboard or anything else on the Pi.

After weeks of just sitting there,, why did this pop up?

And why the reference to chrome?

Thanks Pete

I uninstalled the Chrome browser from my Raspberry Pi. But after weeks of running with FireFox (Quantum ESR 68.4.1esr (32 bit)). on the same url, suddenly I see: "raspberry pi warning unresponsive script chrome://global/content/elements/button.js:297" I really was hoping I got google out of just one little corner of my life. The url was for my security system (OpenHAB) on this Pi and nobody touched the keyboard or anything else on the Pi. After weeks of just sitting there,, why did this pop up? And why the reference to chrome? Thanks Pete

Chosen solution

Generally speaking the chrome:// protocol is used for internal addresses within Firefox's program files, and the term chrome generally refers to the user interface part of the browser (as distinguished from content). This usage dates back to the gestation of Firefox, long before another company decided they liked it so much they would name numerous products after it.

As for why the button.js script seems to have gone into an infinite loop on your device, I have no idea.

Read this answer in context 1
Quote

Additional System Details

Installed Plug-ins

  • Shockwave Flash 32.0 r0

Application

  • User Agent: Mozilla/5.0 (Windows NT 6.3; Win64; x64; rv:72.0) Gecko/20100101 Firefox/72.0

More Information

jscher2000
  • Top 10 Contributor
8963 solutions 73452 answers

Chosen Solution

Generally speaking the chrome:// protocol is used for internal addresses within Firefox's program files, and the term chrome generally refers to the user interface part of the browser (as distinguished from content). This usage dates back to the gestation of Firefox, long before another company decided they liked it so much they would name numerous products after it.

As for why the button.js script seems to have gone into an infinite loop on your device, I have no idea.

Generally speaking the <code>chrome://</code> protocol is used for internal addresses within Firefox's program files, and the term chrome generally refers to the user interface part of the browser (as distinguished from content). This usage dates back to the gestation of Firefox, long before another company decided they liked it so much they would name numerous products after it. As for why the button.js script seems to have gone into an infinite loop on your device, I have no idea.
Was this helpful to you? 1
Quote

Question owner

OK, thanks. At least it isn't google sneaking in through some back door. Google knows too much about me.

I did click the "Continue" button and everything seems fine.

Thanks again.

OK, thanks. At least it isn't google sneaking in through some back door. Google knows too much about me. I did click the "Continue" button and everything seems fine. Thanks again.
Was this helpful to you?
Quote
Ask a question

You must log in to your account to reply to posts. Please start a new question, if you do not have an account yet.