mayhemer / logan

Log Analyzer for Mozilla logs
7 stars 4 forks source link

Error when trying to view a log #24

Closed nwgh closed 6 years ago

nwgh commented 6 years ago

Entered a log so I could try to track down the source of a bug. Parsing got something like 99.9% of the way there, and then the progress bar just stopped, and I was never able to do anything with the log. The log was created from startup using the appropriate environment variables (not about:networking). The URL that was loaded was from bug 1397621, and loading was cancelled by hitting escape. The browser was then cleanly shut down. The problematic log (from a fresh profile, so no PII) is moz.log.busted.gz

The following error was in the devtools console:

while processing '2017-11-03 21:49:53.100025 UTC - [Socket Thread]: I/nsHttp Http2Stream::WriteSegments 0x108cc8c80 Buffered 80470007 0'
at moz.log.busted:382128 (line#s are inaccurate) logan.js:737:14

Safari words it as (not sure if this will be helpful):

while processing '2017-11-03 21:49:53.100025 UTC - [Socket Thread]: I/nsHttp Http2Stream::WriteSegments 0x108cc8c80 Buffered 80470007 0'
at nspr.log:382128 (line#s are inaccurate)
    processRule (logan.js:1048)
    processLineByRules (logan.js:1028)
    processLine (logan.js:980)
    consumeLineByRules (logan.js:967)
    consumeLine (logan.js:945)
    (anonymous function) (logan.js:919)
    asyncFunctionResume
    (anonymous function)
    promiseReactionJob
mayhemer commented 6 years ago

(deployed)

nwgh commented 6 years ago

Awesome, thanks Honza!

mayhemer commented 6 years ago

And I thank you for the report!