WebRTC logging on Firefox 55.0.2 x64 W10

[Sylvain Pascou]

Hello,

I'm having a hard time enabling logs for WebRTC on FF 55 x64 for Windows 10. I've been using these environments:

R_LOG_LEVEL=3
R_LOG_VERBOSE=1
NSPR_LOG_MODULES=timestamp,sync,nsHttp:4,nsSocketTransport:4,nsStreamPump:4,nsHostResolver:4,signaling:5,mtransport:5,MediaManager:4,GetUserMedia:4,webrtc_trace:5
NSPR_LOG_FILE=%temp%\nspr.log
WEBRTC_TRACE_FILE=nspr

R_LOG_LEVEL=3
R_LOG_VERBOSE=1
NSPR_LOG_MODULES=timestamp,sync,nsHttp:4,nsSocketTransport:4,nsStreamPump:4,nsHostResolver:4,signaling:5,mtransport:5,MediaManager:4,GetUserMedia:4,webrtc_trace:5
WEBRTC_TRACE_FILE=%temp%\webrtc.log

In both cases, nspr.log (first case) or default logfile (second case) is populated with info about TCP, HTTP and so on but nothing pertaining to signaling, nor is the file "webrtc.log" created.

I have also tried not using environment variables in a script but about:config and about:networking to set log modules. However I still get the same result.

The same procedures on FF 56.0b5 x64 also yield the same results.

Am I doing something very wrong or forgetting something very important ? ^.^

Thank you for your help,

Sylvain Pascou

[Randell Jesup]

On 8/23/2017 8:51 AM, Sylvain Pascou wrote:
> Hello,
>
> I'm having a hard time enabling logs for WebRTC on FF 55 x64 for Windows 10. I've been using these environments:
>
> R_LOG_LEVEL=3
> R_LOG_VERBOSE=1
> NSPR_LOG_MODULES=timestamp,sync,nsHttp:4,nsSocketTransport:4,nsStreamPump:4,nsHostResolver:4,signaling:5,mtransport:5,MediaManager:4,GetUserMedia:4,webrtc_trace:5
> NSPR_LOG_FILE=%temp%\nspr.log
> WEBRTC_TRACE_FILE=nspr

This should work, but the log with webrtc would likely be in
nspr-child1.log/etc (or something like that)

>
> R_LOG_LEVEL=3
> R_LOG_VERBOSE=1
> NSPR_LOG_MODULES=timestamp,sync,nsHttp:4,nsSocketTransport:4,nsStreamPump:4,nsHostResolver:4,signaling:5,mtransport:5,MediaManager:4,GetUserMedia:4,webrtc_trace:5
> WEBRTC_TRACE_FILE=%temp%\webrtc.log
>
> In both cases, nspr.log (first case) or default logfile (second case) is populated with info about TCP, HTTP and so on but nothing pertaining to signaling, nor is the file "webrtc.log" created.
>
> I have also tried not using environment variables in a script but about:config and about:networking to set log modules. However I still get the same result.
>
> The same procedures on FF 56.0b5 x64 also yield the same results.
>
> Am I doing something very wrong or forgetting something very important ? ^.^

Unfortunately, writing to log files directly from Content processes
(i.e. e10s aka Multi-Process Firefox) doesn't work; a Content process
can't open a file (webrtc.log) for writing.  NSPR_LOG* opens the logs in
the master process (and note, NSPR_LOG* has been replaced by
MOZ_LOG/MOZ_LOG_FILE now; I think that's all in place in 55, but for now
NSPR_LOG* should still work, with a few possible differences).

  Randell Jesup

[Sylvain Pascou]

On Wednesday, August 23, 2017 at 9:28:56 PM UTC+2, Randell Jesup wrote:
> On 8/23/2017 8:51 AM, Sylvain Pascou wrote:
> > Hello,
> >
> > I'm having a hard time enabling logs for WebRTC on FF 55 x64 for Windows 10. I've been using these environments:
> >
> > R_LOG_LEVEL=3
> > R_LOG_VERBOSE=1
> > NSPR_LOG_MODULES=timestamp,sync,nsHttp:4,nsSocketTransport:4,nsStreamPump:4,nsHostResolver:4,signaling:5,mtransport:5,MediaManager:4,GetUserMedia:4,webrtc_trace:5
> > NSPR_LOG_FILE=%temp%\nspr.log
> > WEBRTC_TRACE_FILE=nspr
>
> This should work, but the log with webrtc would likely be in
> nspr-child1.log/etc (or something like that)
>

WebRTC-related (signaling, media, etc) logs are in nspr.log.child-x, indeed ! I did not look in there. My bad.

> >
> > R_LOG_LEVEL=3
> > R_LOG_VERBOSE=1
> > NSPR_LOG_MODULES=timestamp,sync,nsHttp:4,nsSocketTransport:4,nsStreamPump:4,nsHostResolver:4,signaling:5,mtransport:5,MediaManager:4,GetUserMedia:4,webrtc_trace:5
> > WEBRTC_TRACE_FILE=%temp%\webrtc.log
> >
> > In both cases, nspr.log (first case) or default logfile (second case) is populated with info about TCP, HTTP and so on but nothing pertaining to signaling, nor is the file "webrtc.log" created.
> >
> > I have also tried not using environment variables in a script but about:config and about:networking to set log modules. However I still get the same result.
> >
> > The same procedures on FF 56.0b5 x64 also yield the same results.
> >
> > Am I doing something very wrong or forgetting something very important ? ^.^
>
> Unfortunately, writing to log files directly from Content processes
> (i.e. e10s aka Multi-Process Firefox) doesn't work; a Content process
> can't open a file (webrtc.log) for writing.  NSPR_LOG* opens the logs in
> the master process (and note, NSPR_LOG* has been replaced by
> MOZ_LOG/MOZ_LOG_FILE now; I think that's all in place in 55, but for now
> NSPR_LOG* should still work, with a few possible differences).
>

Thanks for that explanation ! I confirm that using MOZ_LOG/MOZ_LOG_FILE instead of NSPR_LOG_MODULES/NSPR_LOG_FILE is working all right in FF55.
The variable WEBRTC_TRACE_FILE still has to be set to "nspr" which is kinda confusing.

Perhaps updating section "Media (the GIPS stack: RTP/RTCP)" @ https://wiki.mozilla.org/Media/WebRTC/Logging could be a good idea to avoid misunderstandings about the 'WebRTC.log' file.

>   Randell Jesup

Thank very much you for your help!