If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Facebook Unresponsive Script Bug (Adblock Plus)

NEW
Unassigned

Status

()

Core
JavaScript Engine
5 years ago
8 months ago

People

(Reporter: Hasan Alicik, Unassigned)

Tracking

15 Branch
x86
Windows XP
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [testday-20120615][js:inv:p2][platform-rel-Facebook])

Attachments

(1 attachment)

(Reporter)

Description

5 years ago
Created attachment 623401 [details]
TheScript.bmp

User Agent: Mozilla/5.0 (Windows NT 5.1; rv:15.0) Gecko/15.0 Firefox/15.0a1
Build ID: 20120511030513

Steps to reproduce:

I'm using Nightly. While I was looking Facebook photos, this script gave error. Not one time.


Actual results:

This script is giving error "https://s-static.ak.fbcdn.net/rsrc.php/v2/yr/r/NbUH3T8_mCD.js:49"


Expected results:

This script should be work.
Is this only an issue with this build or does this also happen with Firefox12 as example ?
Can you try it in the Firefox safemode ?
http://support.mozilla.org/en-US/kb/Safe+Mode

We need steps to reproduce, "looking Facebook photos" is not useable.
(Reporter)

Comment 2

5 years ago
I realized this isn't only existing on Facebook photos. It's existing anytime you roam at Facebook. I'll try it in SafeMode.
(Reporter)

Comment 3

5 years ago
Can it be Adblock Plus' issue?
(Reporter)

Updated

5 years ago
Component: Untriaged → Add-on Builder
Product: Firefox → addons.mozilla.org
Version: 15 Branch → unspecified
(Reporter)

Updated

5 years ago
Summary: Facebook Script Bug "https://s-static.ak.fbcdn.net/rsrc.php/v2/yr/r/NbUH3T8_mCD.js:49" → Facebook Unresponsive Script Bug "https://s-static.ak.fbcdn.net/rsrc.php/v2/yr/r/NbUH3T8_mCD.js:49"
Not entirely sure why this was moved to the Addon Builder component. This doesn't look like it has anything to do with Builder...
(Reporter)

Comment 5

5 years ago
I'm just change it. I'm researching which part of component so it isn't true I know.
(Reporter)

Updated

5 years ago
Summary: Facebook Unresponsive Script Bug "https://s-static.ak.fbcdn.net/rsrc.php/v2/yr/r/NbUH3T8_mCD.js:49" → Facebook Unresponsive Script Bug (Adblock Plus)
(Reporter)

Updated

5 years ago
Component: Add-on Builder → Web Apps
Product: addons.mozilla.org → Firefox
Version: unspecified → 15 Branch
Moving to extension compatibility - this refers to a problem with an extension.
Component: Web Apps → Extension Compatibility
QA Contact: untriaged → extension.compatibility

Comment 7

5 years ago
(In reply to Jason Smith [:jsmith] from comment #6)
> Moving to extension compatibility - this refers to a problem with an
> extension.

Unlikely. Most likely cause of this is a script that assumes that all web requests will load successfully and that goes into an endless loop if this doesn't happen for some reason.

For reference: line 49 of NbUH3T8_mCD.js refers to the ServerJS API (all of it thanks to obfuscation). Obfuscation makes it hard to tell what this piece of code does and why it hangs up.
Duplicate of this bug: 765117
Tried reproducing on vista, with no luck after about 15 minutes.
Changing the status to new due to duplicate bug and 2 more reports in Nightly testers mailing list.

Any chance this is related to bug 690229?
Assignee: nobody → general
Status: UNCONFIRMED → NEW
Component: Extension Compatibility → JavaScript Engine
Ever confirmed: true
Product: Firefox → Core
QA Contact: extension.compatibility → general
Whiteboard: [testday-20120615]
Whiteboard: [testday-20120615] → [testday-20120615][js:inv:p2]

Comment 10

5 years ago
I get this fairly regularly on Nightly and release while using Facebook when the tab has been open for a few hours and I've been using it for photo's and chatting. Closing the facebook tab and reopening clears the issue until another few hours pass.
(Assignee)

Updated

3 years ago
Assignee: general → nobody
platform-rel: --- → ?
Whiteboard: [testday-20120615][js:inv:p2] → [testday-20120615][js:inv:p2][platform-rel-Facebook]
platform-rel: ? → ---
You need to log in before you can comment on or make changes to this bug.