On 3/12/2018 8:05 AM, R P Herrold wrote:
Rather than ad hoc experimentation, is there a way to turn on
(unix syslog style, perhaps across a UDP socket, so not
blocking any process) 'logging', to a file, or at least a
'listener', of all that FF is doing?
I would filter that 'flood' of course, so I could 'hunt down'
through traditional 'partitioning' techniques, offending
'hung' DNS lookups, local or remote scripts, and who know what
else
There is "about:networking" which has a logging feature. When I was
having slowness issues and reported it to this list about a year ago, I
was told to use this feature to create a log and send it in to someone
at mozilla to parse. They claimed their developers could not find the
problem, then the person who originally asked for the logs handed me off
to someone else to send future logs to and I never heard from anyone at
mozilla again.
Be aware, this logging feature will generate LARGE files if you leave it
running too long. When I was doing testing for the above-mentioned
issues, it created 10s of GB in log files just browsing a dozen or so sites.
jim
_______________________________________________
Enterprise mailing list
[email protected]
https://mail.mozilla.org/listinfo/enterprise
To unsubscribe from this list, please visit https://mail.mozilla.org/listinfo/enterprise
or send an email to [email protected] with a subject of
"unsubscribe"
