Reviews for Allow CORS: Access-Control-Allow-Origin
Allow CORS: Access-Control-Allow-Origin by Muyor
101 reviews
- Rated 3 out of 5by Okdi, 5 days agoFound an infinite loop that kept one CPU core busy at ~100% constantly, even with the extension idle.
Environment: Firefox Developer Edition (build 20261102), macOS 27.2, Apple M2 Pro.
What happens: the extension's background script gets stuck in a storage feedback loop. I captured two 5-second Firefox Profiler recordings, and in that window the extension ran this sequence about 6,500–7,000 times (≈1,300–1,400 times per second):
storage.local.get → storage.session.get → storage.local.set → storage.onChanged fires → declarativeNetRequest.getSessionRules + tabs.query → storage.local.set again → ...
It looks like the storage.onChanged listener writes to storage.local, which triggers storage.onChanged again, so the loop never ends.
Impact: the WebExtensions process sat at 90–100% CPU for over 24 hours, and Firefox's main process used about another full core just handling the IndexedDB transactions and IPC messages (~345,000 IPC messages in 5 seconds). My MacBook was constantly hot even with just two tabs open. Disabling the extension brought Firefox's CPU usage down to ~0% right away.
Suggested fix: skip the storage.local.set call when the value hasn't changed, or ignore onChanged events caused by the extension's own writes.
Happy to share the profiler recordings if that helps. - Rated 5 out of 5by 退出党团队远离中共邪教, 21 days ago
- Rated 1 out of 5by octalish, a month agoEating a lot of CPU and RAM even if CORS bypass is not enabled (so extension is supposed to do nothing). There is iither issues in the code, or well-hiden malware /cryptominer.
A quick read of the code shows nothing obviously nasty, so I guess it is just buggy, but hard to be sure.
Disabling the extension gave my computer fresh air ! - Rated 2 out of 5by dbenton, 2 months agoit is not a crypto miner, i looked into the source code. but WOW does it use too many resources. if you want this to not use as many, set it to a manual origin instead of leaving it at *
- Rated 1 out of 5by Firefox user 19757071, 9 months agousing 1 CPU core at 100% constantly. Something's wrong
- Rated 1 out of 5by Taconator, 9 months agoConstantly uses 100% of a core on my CPU, and when I removed it, it was suddenly reinstalled and couldn't be removed. I had to open my profile folder and delete it manually
- Rated 1 out of 5by stark-bit, 10 months agoStill has memory leaks, still massive CPU use even when enabled but switched off for all tabs
- Rated 1 out of 5by Firefox user 19611818, a year agodo not use this Addon. Youtube and other Websites wont work anymore properly
- Rated 1 out of 5by tad1, a year ago
- Rated 1 out of 5by Firefox user 19570256, a year ago
- Rated 3 out of 5by Mugnum, a year agoHeads up: currently causes a memory leak, rapidly increasing to +40 Gb and either flushes or crashes browser.
- Rated 1 out of 5by Fahad Yousaf, a year ago"WORST ADDON EVER. HUGE BATTERY DRAINS"
I just purchased a Macbook Pro M4 and it was an upgrade from my M1 Air. I thought I'll be enjoying some decent performance with great battery life until I saw that my laptop was draining battery in the worst possible way.
I used activity monitor to track it down to firefox. Inside firefox I saw Firefox WebExtensions process taking almost all the power and cpu time constantly even when my laptop was lid down.
I ran the firefox's profiler to track down what was causing all this right at that very moment.
Every profiling logged this extension's URI and Name in call stacks.
Removed it instantly. - Rated 1 out of 5by willdaplum, a year agoI recently installed this on my new laptop and almost returned it for getting abysmal battery life until I found that it was this extension's fault.
- Rated 1 out of 5by Firefox user 18548671, a year ago
- Rated 1 out of 5by Firefox user 19000335, a year agoConstantly uses >"70%" in the Firefox Task Manager for the Addon's usage.
- Rated 3 out of 5by 0xivb, 2 years agoUnlike some of the reviews suggest, this isn't malware, but it does have a bug that causes it to use up a lot of CPU - other than that works great!
- Rated 1 out of 5by bär, 2 years ago