Closed Bug 1669958 Opened 5 years ago Closed 5 years ago

console not logging messages depending on startup

Categories

(DevTools :: Console, defect)

Product:
DevTools
Component:
Console
Version:
Firefox 81
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 1661569

People

(Reporter: firefox, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:81.0) Gecko/20100101 Firefox/81.0

Steps to reproduce:

(I use Windows 7 on laptop)
METHOD 1

  • Launch Firefox (thus cold start)
  • CTRL+SHIFT+M to enter mobile view
  • CTRL+SHIFT+K to show developer console
    Visit a url that logs to the console.
    Result: XHR messages are logged but missing are console.log, console.debug, console.info messages are missing. The messages fail to log even after refresh of the browser which leads me to believe the console isn't listening.

METHOD 2

  • Launch Firefox (thus cold start)
    Visit a url that logs to the console.
  • CTRL+SHIFT+M to enter mobile view
  • CTRL+SHIFT+K to show developer console
  • Refresh browser
    All expected messages appear

Actual results:

Console logging results vary depending on when the Developer Console AND Mobile View are started when the desktop browser is launched.

After launch, so long as the browser has visited a site, any site, (and thus "warmed up") and then you enter Developer Console/Mobile View, all expected messages are delivered. But if you immediately start your Developer Console/Mobile View after launching Firefox, only XHR messages are in console.

Note there are intermitent times that I struggle to repeat where the console stops reporting even if I clear my cache. The solution is to restart the browser. It typically happens after the browser has been running for an extended period (hour or more).

Expected results:

My scripted messages to console.log, console.debug, console.info should have appeared.

Component: Untriaged → Console
Product: Firefox → DevTools

Hello ranbo, thanks for filing a bug.
This looks like what was fixed with Bug 1661569, which will be in Firefox 82.
We added a test (Bug 1664493) so we don't have the same issue again in the future.

I'm going to close this, as this was handled, but feel free to reopen it if you are still observing this on 82.

Status: UNCONFIRMED → RESOLVED
Closed: 5 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.