Closed Bug 660321 Opened 14 years ago Closed 8 years ago

mochitest-oth spams tons of "JavaScript strict warning: resource:///modules/NetworkPrioritizer.jsm, line 117: reference to undefined property aBrowser.webNavigation"

Categories

(Firefox :: General, defect)

defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: dholbert, Unassigned)

References

Details

mochitest-oth spams tons of lines of these two warnings right now: { JavaScript strict warning: resource:///modules/NetworkPrioritizer.jsm, line 117: reference to undefined property aBrowser.webNavigation } and { TEST-INFO | chrome://mochitests/path/to/some/test.js | Console message: [JavaScript Warning: "reference to undefined property aBrowser.webNavigation" {file: "resource:///modules/NetworkPrioritizer.jsm" line: 117}] } This green mochitest-oth log, for example... http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1306518921.1306523049.29373.gz ... has 1860 lines that include the text "reference to undefined property aBrowser.webNavigation" and "NetworkPrioritizer.jsm" This obscures useful/important warning messages. Can we clean this up somehow? The code that the warning points to is: > 115 // Auxiliary methods > 116 getLoadgroup: function(aBrowser) { > 117 return aBrowser.webNavigation.QueryInterface(Ci.nsIDocumentLoader) > 118 .loadGroup.QueryInterface(Ci.nsISupportsPriority); > 119 }
This is scary. aBrowser.webNavigation.QueryInterface(...) must fail when there's no webNavigation. It's entirely unclear to me why the warning isn't followed by an error, breaking getLoadgroup's caller. I found the message 933 times in a test log, by the way.
Um, the messages seem to have disappeared all of a sudden. If anyone is seeing them again, please report back.
Seeing it again: http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1308293146.1308296452.8572.gz It only appeared two times in there, though.
NetworkPrioritizer.jsm has been removed.
Status: NEW → RESOLVED
Closed: 8 years ago
Depends on: 1351281
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.