Closed
Bug 1136497
Opened 11 years ago
Closed 9 years ago
Firefox floods session.log to the tune of several gigabytes per day
Categories
(Core :: Widget: Gtk, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: dennisml, Unassigned)
Details
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:35.0) Gecko/20100101 Firefox/35.0
Build ID: 20150122214805
Steps to reproduce:
Use Firefox.
Actual results:
.cache/gdm/session.log in my home directory get flooded with message like:
JavaScript strict warning: https://www.google.com/js/bg/Tf-qGjWUMoHZMXVBkTsgDeQliWpEx7wNIIiB--IlBD8.js line 1 > eval, line 1: ReferenceError: deprecated caller usage
JavaScript strict warning: https://plus.google.com/_/scs/apps-static/_/js/k=oz.sbw.en_US.0KFYharWP1M.O/m=sbw_base,sbw_card,sbw_s/am=5AEGAAAH/rt=j/d=1/t=zcms/rs=AGLTcCMlM8OXySQvUApZIhIt-HfwzNxbUQ, line 2: SyntaxError: in strict mode code, functions may be declared only at top level or immediately within another function
JavaScript strict warning: https://bugzilla.mozilla.org/data/assets/c98a90851d2ae5b989b74529d5fea389.js?1424755211, line 45: ReferenceError: reference to undefined property i.children
The session.log grows over 1G during the day. This is excessive.
I noticed this because I was wondering why the free space of my harddisk kept shrinking without any apparent reason.
Expected results:
Firefox shouldn't log so excessively that the log consumes a significant amount of disk space.
Updated•11 years ago
|
Component: Untriaged → Widget: Gtk
Product: Firefox → Core
Comment 1•11 years ago
|
||
Could you have a debug build perhaps, or a pref set to dump these errors?
Updated•9 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Resolution: --- → INCOMPLETE
Comment 2•9 years ago
|
||
This may be caused by setting javascript.options.strict to true in about:config and loading certain Google scripts (in my case, Google recaptcha but I've seen the same problem from what looks like Google+ widget scripts). I assume the same problem could come about by concatenating certain "use strict" scripts with those scripts, but in my case that global setting caused a flood of those errors in the console. Check to see if that setting is on.
You need to log in
before you can comment on or make changes to this bug.
Description
•