Colabtools: JavaScript not working on Colab

[cbrionesr]

Bug report for Colab: http://colab.research.google.com/.

• Describe the current behavior: I've been using Colab for a while now and never had issues, but suddenly today it started throwing an error. It says:

Error
Could not load the JavaScript files needed to display output.
This is probably because your Google account login access has expired or because third-party cookies are not allowed by your browser.

Please reload this page.

(Uploaded a picture of error...) None of the two possible problems that says it's true.. my google account access has not expired and I have 3rd paty cookie enabled.. I restarted chrome, disabled/enables 3rd party cookies and login again.. nothing works.

• Describe the expected behavior: It should read the script perfectly (Using a notebook in Python 3)... it has done it several times and i don't understand why

• The web browser you are using (Chrome, Firefox, Safari, etc.): Google Chrome latest version

• Link to self-contained notebook that reproduces this issue
  (click the Share button, then Get Shareable Link): https://colab.research.google.com/drive/1-8KpjrPLoZ6Bhvip6LcIBGSsk0adATNl

[mouadriyad]

Same problem + it uses all my laptop ram => crash

[blois]

Looking at that notebook it looks like many of the plotly graphs are consuming large amounts of CPU and memory. The outputs will only be rendered when they are scrolled into view, so I can open Chrome's task manager and watch the CPU and memory increase while scrolling through. In a fresh browser session I'm seeing it get up to 2GB of RAM for that renderer process.

The error dialog you're seeing is because the frames are going unresponsive because of how much CPU they are using (the memory pressure isn't helping).

The workarounds for this would be to either break the single notebook up into separate notebooks with fewer outputs or see if you can reduce the complexity of the plotly graphs (they appear to be the primary source of the issue).

[Alexyjones]

I do get a similar error, when running a cell in my colab. Even loading just some library results in this error. I tried to log in and out, using a private tab and also other browsers. Even uninstalling all extensions did not change this behavior.
I am using Safari 13 now.
This error just appeared about 2 weeks ago and has persisted since.

Any help how I can trace this error would be greatly appreciated!

Thanks!

[blois]

@Alexyjones - I'm unable to repro issues with Safari 13, but about 2 weeks ago did make some changes specifically to fix some Safari issues specifically in this area.

Can you try using a Private window? Also I'm curious if you can think of any other extensions or settings which may cause problems.

[Alexyjones]

@blois Thank you for the quick response. I have tried a private window and reproduced the error. I could share the colab if it helps (just not publicly). I got the "feeling" that it is tied to my google account...

[Keramatfar]

I have the same problem.

[Alexyjones]

I just observed that it might be a network issue - The error appears only in my company network (which is restrictive, many ports blocked), but is resolved, when I use my mobile network.

[QuantumNinja92]

It only started occurring recently, and more frequent on GPU environment.
so network, cookies, OS restart ? Any actual cause cause its troublesome with long running models.

[Alexyjones]

Sometimes using an unfiltered access to the internet helped. Check if there
are port restrictions.

Am Mo., 6. Juli 2020 um 11:07 Uhr schrieb Ramzy Karam <
[email protected]>:

It only started occurring recently, and more frequent on GPU environment.
so network, cookies, OS restart ? Any actual cause cause its troublesome
with long running models.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/googlecolab/colabtools/issues/757#issuecomment-654111900,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AK5WUSTXTD34HTFVLSHUMTTR2GH5RANCNFSM4IZWOFRQ
.

[QuantumNinja92]

Hi Alex,
I am using Incognito mode and it hasn't got the error so far.
But you'd have to relogin to any service used with the Colab like google drive

[Ahmad-noborders]

hey @blois i had the same error but the cell is still running. i am expecting that the cell will complete execution even after error and i should wait. or should i cancel it because it?

[blois]

If the code is still running and you get this error then you can try moving the cell up/down using the arrows on the cell toolbar-this will cause the output to re-render itself. If the error is caused by a spinning output then you may need to first kill the task using Chrome's Task Manager, then move the cell up/down to re-render it.

If you have something which consistently repro's this then I'd be interested in diving into what is causing it.

[QuantumNinja92]

My scenario is an 8-10 hours training, after the training the model is saved and sent to google drive.
The below solution works perfectly for me as long as you didn't exceed the 12 hours, used incognito mode, and before the session connects allow cookies.
https://stackoverflow.com/a/60388275/2791816

[Ahmad-noborders]

thank you @blois for our reply actually my drive space was full and it was unable to write data on drive i thin this caused the problem. i freed up space and it is all good now,

[Ahmad-noborders]

@QuantumNinja92 ye in my case it was around 6 hours training

[KimYonghyun94]

I goto a same error on colab, but colab is working on ipad even same googleID.
Only Windows and Linux got this error on colab, also my google profile and googledrive icon(?) image(?) were broken..... how can i solve the problem?

[ahelmi365]

I have the same problem.

[KimYonghyun94]

I solved this error. if youguys use Chrome, go to History (ctl + h) and clear browsingdata (browsing history, cookies and other sites data, cached imagesand files). and then reboot.

[ahelmi365]

Is this applicable for Microsoft Edge browser?

[brianferrell787]

Check your task manager on your laptop and see how full the disk is.
Mine was 100% so I searched “disk cleanup” on my Windows computer And got rid of temporary files and files downloaded from internet, etc. also clear cache and cookies on whatever browser you’re doing. And if you have synced your google chrome and Microsoft edge specifications as the same(cookies, extensions, etc) then get rid of both cache and other stuff on them as well. Also check 3rd party cookies

[brianferrell787]

Do you have too many cells open on your Colab that aren’t needed? Start a new notebook with just the cells you need or get rid of them.

[brianferrell787]

Too many cells that weren’t needed helped me. And starting a new notebook!!

[Ceceu]

Bug report for Colab: http://colab.research.google.com/.

• Describe the current behavior: I've been using Colab for a while now and never had issues, but suddenly today it started throwing an error. It says:

Error
Could not load the JavaScript files needed to display output.
This is probably because your Google account login access has expired or because third-party cookies are not allowed by your browser.

Please reload this page.

(Uploaded a picture of error...) None of the two possible problems that says it's true.. my google account access has not expired and I have 3rd paty cookie enabled.. I restarted chrome, disabled/enables 3rd party cookies and login again.. nothing works.

• Describe the expected behavior: It should read the script perfectly (Using a notebook in Python 3)... it has done it several times and i don't understand why
• The web browser you are using (Chrome, Firefox, Safari, etc.): Google Chrome latest version
• Link to self-contained notebook that reproduces this issue
  (click the _Share_ button, then _Get Shareable Link_): https://colab.research.google.com/drive/1-8KpjrPLoZ6Bhvip6LcIBGSsk0adATNl

Any solution?

[Echo9k]

None of these worked for me.

• I tried terminating the environment,
• Doing a factory reset,
• Restarting chrome,
• Restarting my laptop,
• Cleaning cookies for Colab, and for everything in the last 24 hours.
• Using a different browser (Google Chrome beta, Brave browser)
• Using Colab with a Local Host.
• Coincidently I started using a VPN in between and yet it wasn't working.

It was working yesterday before my environment ran out of RAM. Perhaps it's something wrong with Colab?
—
It worked after changing my user in Chrome.

[brianferrell787]

“None of these worked for me.

• I tried terminating the environment,
• Doing a factory reset,
• Restarting chrome,
• Restarting my laptop,
• Cleaning cookies for Colab, and for everything in the last 24 hours.
• Using a different browser (Google Chrome beta, Brave browser)
• Using Colab with a Local Host.
• Coincidently I started using a VPN in between and yet it wasn't working.

It was working yesterday before my environment ran out of RAM. Perhaps it's something wrong with Colab?”

Do you have too many cells open on your Colab that aren’t needed? Start a new notebook with just the cells you need or get rid of them.

[Echo9k]

None of these worked for me.

• I tried terminating the environment,
• Doing a factory reset,
• Restarting chrome,
• Restarting my laptop,
• Cleaning cookies for Colab, nor for everything in the last 24 hours.
• A different browser (Google Chrome beta, Brave browser)
• Using a local environment and it's not working.
• Coincidently I started using a VPN in between, and yet it wasn't working.

It was working yesterday before my environment ran out of RAM. Perhaps it's something wrong with Colab?

“None of these worked for me.

• I tried terminating the environment,
• Doing a factory reset,
• Restarting chrome,
• Restarting my laptop,
• Cleaning cookies for Colab, and for everything in the last 24 hours.
• Using a different browser (Google Chrome beta, Brave browser)
• Using Colab with a Local Host.
• Coincidently I started using a VPN in between and yet it wasn't working.

It was working yesterday before my environment ran out of RAM. Perhaps it's something wrong with Colab?”

Do you have too many cells open on your Colab that aren’t needed? Start a new notebook with just the cells you need or get rid of them.

I'd not say so, you can check it here.
https://colab.research.google.com/drive/1YMKWa2so2AESmQth77Kd8pJbd1TfTzxs?usp=sharing
While I was making a few changes to share it with you I got the error and it's not even running.