[SOLVED] Terminal output after Firefox is started

linux_user · 2016-12-19 07:47:24

I start terminal using the command

firefox &

Firefox run, everything seems to be ok, but now and then I get strange output on terminal.

console.error: 
  Corrupt session file (invalid JSON found) 
  Message: SyntaxError: JSON.parse: unexpected end of data at line 1 column 1 of the JSON data
  Stack:
    SessionFileInternal.read<@resource://app/modules/sessionstore/SessionFile.jsm:217:22
TaskImpl_run@resource://gre/modules/Task.jsm:315:40
Handler.prototype.process@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:933:23
this.PromiseWalker.walkerLoop@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:812:7
this.PromiseWalker.scheduleWalkerLoop/<@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:746:1

  SessionFileInternal.read<@resource://app/modules/sessionstore/SessionFile.jsm:217:22
TaskImpl_run@resource://gre/modules/Task.jsm:315:40
Handler.prototype.process@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:933:23
this.PromiseWalker.walkerLoop@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:812:7
this.PromiseWalker.scheduleWalkerLoop/<@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:746:1

 1482133425155	addons.productaddons	ERROR	Request failed certificate checks: [Exception... "SSL is required and URI scheme is not https."  nsresult: "0x8000ffff (NS_ERROR_UNEXPECTED)"  location: "JS frame :: resource://gre/modules/CertUtils.jsm :: checkCert :: line 145"  data: no]

###!!! [Child][MessageChannel] Error: (msgtype=0x80000F,name=PHttpChannel::Msg___delete__) Channel closing: too late to send/recv, messages will be lost

New output is on the screen every few mins... Any help?

Last edited by linux_user (2016-12-24 06:12:13)

Head_on_a_Stick · 2016-12-19 18:53:21

Do you still get these errors if you start FF in "safe" mode?

https://support.mozilla.org/en-US/kb/tr … -safe-mode

Perhaps one of your AddOns is malfunctioning.

Horizon_Brave · 2016-12-20 01:16:50

Can you track it down to what it is you're doing on Firefox when you get these messages?
Can you disable all of most of your plugins and try it and see if you get the same message?

Horizon_Brave · 2016-12-20 01:34:04

Actually wow, I tried on my VM BL setup and I get the same message :

 1482133425155	addons.productaddons	ERROR	Request failed certificate checks: [Exception... "SSL is required and URI scheme is not https."  nsresult: "0x8000ffff (NS_ERROR_UNEXPECTED)"  location: "JS frame :: resource://gre/modules/CertUtils.jsm :: checkCert :: line 145"  data: no]

but that's probably just ssl cert related.

Perhaps if you open up firefox, click the menu options, and click "Developer" options, then choose "Debugger" . This will open up a small console on the bottom of your web session. Move over to the "Console" tab. This may garner a peak into what's going on?

linux_user · 2016-12-20 13:23:21

Head_on_a_Stick wrote:

Do you still get these errors if you start FF in "safe" mode?
https://support.mozilla.org/en-US/kb/tr … -safe-mode
Perhaps one of your AddOns is malfunctioning.

Yes, this is what I got when viewing the URL attached...

1482240148702	addons.productaddons	ERROR	Request failed certificate checks: [Exception... "SSL is required and URI scheme is not https."  nsresult: "0x8000ffff (NS_ERROR_UNEXPECTED)"  location: "JS frame :: resource://gre/modules/CertUtils.jsm :: checkCert :: line 145"  data: no]

linux_user · 2016-12-20 13:27:50

Horizon_Brave wrote:

Actually wow, I tried on my VM BL setup and I get the same message :
 1482133425155	addons.productaddons	ERROR	Request failed certificate checks: [Exception... "SSL is required and URI scheme is not https."  nsresult: "0x8000ffff (NS_ERROR_UNEXPECTED)"  location: "JS frame :: resource://gre/modules/CertUtils.jsm :: checkCert :: line 145"  data: no]
but that's probably just ssl cert related.
Perhaps if you open up firefox, click the menu options, and click "Developer" options, then choose "Debugger" . This will open up a small console on the bottom of your web session. Move over to the "Console" tab. This may garner a peak into what's going on?

Indeed, it doesn't affect my browsing in any way, just that I need to open another terminal to use it while browsing....

Nothing comes up in the console tab when these output are up in the terminal.

ohnonot · 2016-12-22 07:56:56

about the corrupt session file:
i remember it was quite common for firefox to mess up its own configuration every now and then, and there used to be ways to fix it.
maybe you should search for "corrupt session file" on http://forums.mozillazine.org/

linux_user · 2016-12-22 16:20:10

ohnonot wrote:

about the corrupt session file:
i remember it was quite common for firefox to mess up its own configuration every now and then, and there used to be ways to fix it.
maybe you should search for "corrupt session file" on http://forums.mozillazine.org/

Hmm.. Thanks...

BLizgreat! · 2016-12-22 18:01:13

Wasn't gonna but...

All that stuff is completely normal. The browser doesn't ordinarily show you that stuff cause it's not important.

It's designed to deal with those errors. A messed up script on a website, a 3rd party cookie, whatever else routinely triggers that type of junk, the browser deals with it and gets on with its/your life.

But you're running Ff as a background process in a console so you see these things and wonder what they're all about.

Ans: normal, ff isn't meant to be run in bg of a console and you don't see those errors otherwise cause they don't matter.

Last edited by BLizgreat! (2016-12-22 18:03:27)

Horizon_Brave · 2016-12-22 18:45:23

BLwillbegreat! wrote:

Ans: normal, ff isn't meant to be run in bg of a console and you don't see those errors otherwise cause they don't matter.

Don't matter to non geeks you mean!

linux_user · 2016-12-23 03:32:17

BLwillbegreat! wrote:

Wasn't gonna but...
All that stuff is completely normal. The browser doesn't ordinarily show you that stuff cause it's not important.
It's designed to deal with those errors. A messed up script on a website, a 3rd party cookie, whatever else routinely triggers that type of junk, the browser deals with it and gets on with its/your life.
But you're running Ff as a background process in a console so you see these things and wonder what they're all about.
Ans: normal, ff isn't meant to be run in bg of a console and you don't see those errors otherwise cause they don't matter.

I get those errors even running in normal mode (not background). By the way I am not sure if that's exactly the same errors, but I am sure I do see some error output.

BLizgreat! · 2016-12-24 03:26:11

^Yeah going to happen however someone uses a console. My money's still on them being related to normal operation hiccups and nothing to be concerned about.

If someone were really curious could always hit up Google about them.

#1 2016-12-19 07:47:24

[SOLVED] Terminal output after Firefox is started

#2 2016-12-19 18:53:21

Re: [SOLVED] Terminal output after Firefox is started

#3 2016-12-20 01:16:50

Re: [SOLVED] Terminal output after Firefox is started

#4 2016-12-20 01:34:04

Re: [SOLVED] Terminal output after Firefox is started

#5 2016-12-20 13:23:21

Re: [SOLVED] Terminal output after Firefox is started

#6 2016-12-20 13:27:50

Re: [SOLVED] Terminal output after Firefox is started

#7 2016-12-22 07:56:56

Re: [SOLVED] Terminal output after Firefox is started

#8 2016-12-22 16:20:10

Re: [SOLVED] Terminal output after Firefox is started

#9 2016-12-22 18:01:13

Re: [SOLVED] Terminal output after Firefox is started

#10 2016-12-22 18:45:23

Re: [SOLVED] Terminal output after Firefox is started

#11 2016-12-23 03:32:17

Re: [SOLVED] Terminal output after Firefox is started

#12 2016-12-24 03:26:11

Re: [SOLVED] Terminal output after Firefox is started

Board footer