Closed
Bug 935605
Opened 11 years ago
Closed 10 years ago
After updating to FF26 win32 the system console appears to have verbose enabled which floods the console to the extent that the browser is sluggish, this output should've been filtered and may have had operations performed due to the performance loss.
Categories
(Add-on SDK Graveyard :: General, defect, P2)
Add-on SDK Graveyard
General
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: rodneyd.teal, Unassigned)
References
Details
User Agent: Mozilla/5.0 (Windows NT 5.1; rv:27.0) Gecko/20100101 Firefox/27.0 (Beta/Release)
Build ID: 20131105004004
Steps to reproduce:
I updated to FF26 win32 and executed cfx with the following arguments: run --package-path="%TorrentPlus%" --pkgdir="%TorrentPlus%" --profiledir="%userprofile%\Desktop\cfx-profile" --binary="C:\Program Files\Aurora\firefox.exe"
Actual results:
Log information from all webpages under all log categories was being logged to the system console such as js strict warnings ,System Js: *, and etc. As though verbose had been enabled. This made the browser extremely sluggish.
Expected results:
Only console.(error|info|debug): or special xpcom cases should have been logged by default.
Reporter | ||
Comment 1•11 years ago
|
||
I patched addon-sdk-1.14/cuddlefish/runner.py.
Define regex to filter output.
#DIFF
FILTER_OUTPUT = re.compile('^(console\.error|console\.info|console\.debug).*', re.DOTALL)
#DIFF
modify run_app function to filter output using above RE
def run_app:
last_output_time = time.time()
#DIFF
m = FILTER_OUTPUT.match(new_chars)
if m:
sys.stderr.write(m.group(0))
#DIFF
#sys.stderr.write(new_chars)
sys.stderr.flush()
Reporter | ||
Updated•11 years ago
|
OS: All → Windows XP
Hardware: All → x86
Priority: -- → P2
Comment 2•10 years ago
|
||
Sorry we won't be releasing any new versions of cfx, jpm is the replacement https://www.npmjs.com/package/jpm
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Resolution: --- → WONTFIX
Updated•10 years ago
|
OS: Windows XP → All
Hardware: x86 → All
You need to log in
before you can comment on or make changes to this bug.
Description
•