Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Hierdie gesprek is in die argief. Vra asseblief 'n nuwe vraag as jy hulp nodig het.

How to get the console log to show all output without truncating beginning

more options

I have a complicated script with a lot of debugging output. When I check it, Firefox's console log always starts in the middle of script execution, making it impossible for me to see what is going wrong at the beginning of the script. It seems to have a maximum limit to what my script can output, making development a major pain in the tuchus.

I have tried this in both regular Firefox and the Developer edition. I have set all the about:config devtools.hud.loglimit and devtools.performance.memory.max-log-length to 1000000000, the maximum allowable value. Is there a way to turn this truncation off?

I've also tried having the script append log entries to a comment in the of the page instead of writing to console.log, but as I'm trying to log objects so I can look at them, JSON.stringify(object) is choking on cyclical reference errors, and even if it worked that would not be an idea solution since it's much easier to browse objects in the console.

I have a complicated script with a lot of debugging output. When I check it, Firefox's console log always starts in the middle of script execution, making it impossible for me to see what is going wrong at the beginning of the script. It seems to have a maximum limit to what my script can output, making development a major pain in the tuchus. I have tried this in both regular Firefox and the Developer edition. I have set all the about:config devtools.hud.loglimit and devtools.performance.memory.max-log-length to 1000000000, the maximum allowable value. Is there a way to turn this truncation off? I've also tried having the script append log entries to a comment in the of the page instead of writing to console.log, but as I'm trying to log objects so I can look at them, JSON.stringify(object) is choking on cyclical reference errors, and even if it worked that would not be an idea solution since it's much easier to browse objects in the console.

All Replies (4)

more options

The Dev Tools team has its own forum where you might be able to get a solution:

https://discourse.mozilla.org/c/devtools

more options

Yeah, as is apparently par for the course for Mozilla/Firefox, the login form on that forum is completely broken. I've tried logging in twice using their email link and once using my google credentials and it keeps logging me in and then immediately telling me I'm not logged in and need to log in again.

Jeezus, can't Mozilla get ANYTHING right?

more options

Oh, wait. It just popped open a bunch of tabs telling me to create a new account.

On those tabs, none of the buttons work. Not one. They do nothing.

This has been quite a spectacular waste of time.

more options

Hi mikirby, I'm going to tell you what you undoubtedly already know I'm going to say: "The site works normally for me."

If a site is generally known to work in Firefox, these are suggestions to try when it stops working normally:

Double-check content blockers: Firefox's Tracking Protection feature and extensions that counter ads and tracking may break websites that weren't built to operate normally without the blocked components.

Do you see a shield icon toward the left end of the address bar, near the lock icon? More info on managing the Tracking Protection feature in this article: What happened to Tracking Protection?.

Extensions such as Adblock Plus, Blur, Disconnect, Ghostery, NoScript, Privacy Badger, uBlock Origin or uMatrix should provide toolbar buttons to manage blocked content in a page. There may or may not be a number on the icon indicating the number of blocked items; you may need to click the button to see what's going on and test whether you need to make an exception for this site.

Cache and Cookies: When you have a problem with one particular site, a good "first thing to try" is clearing your Firefox cache and deleting your saved cookies for the site.

(1) Clear Firefox's Cache

See: How to clear the Firefox cache

If you have a large hard drive, this might take a few minutes.

(2) Remove the site's cookies (save any pending work first). While viewing a page on the site, try either:

  • right-click (on Mac Ctrl+click) a blank area of the page and choose View Page Info > Security > "Clear Cookies and Site Data"
  • (menu bar) Tools > Page Info > Security > "Clear Cookies and Site Data"
  • click the padlock or "i" icon in the address bar, then the ">" button, then More Information, and finally the "Clear Cookies and Site Data" button

In the dialog that opens, you will see one or more matches to the current address so you can remove the site's cookies individually without affecting other sites.

Then try reloading the page. Does that help?

Testing in Firefox's Safe Mode: In its Safe Mode, Firefox temporarily deactivates extensions, hardware acceleration, and some other advanced features to help you assess whether these are causing the problem.

If Firefox is not running: Hold down the Shift key when starting Firefox. (On Mac, hold down the option/alt key instead of the Shift key.)

If Firefox is running: You can restart Firefox in Safe Mode using either:

  • "3-bar" menu button > "?" Help > Restart with Add-ons Disabled
  • (menu bar) Help menu > Restart with Add-ons Disabled

and OK the restart.

Both scenarios: A small dialog should appear. Click "Start in Safe Mode" (not Refresh).

Any improvement?