Colab question

[David703]

Hi, sorry to bother you guys, but I've been experiencing this error on all my Google accounts recently:

"Failed to execute cell. Could not send execute message to runtime: SecurityError: Permission denied to access property "traceDefinedHardwareId" on cross-origin object"
Is it a known problem with a known solution?


Here are the error details:
Permission denied to access property "traceDefinedHardwareId" on cross-origin object self.tr_NMvxyzOxhGbceXrQ/<@https://colab.research.google.com/github/chalsall/GPU72_CoLab/blob/master/gpu72_tf.ipynb:3:9 self.tr_NMvxyzOxhGbceXrQ@https://col...gpu72_tf.ipynb:41:6 get@https://colab.research.google.co...gpu72_tf.ipynb:59:23 get@https://colab.research.google.co...gpu72_tf.ipynb:94:25 get@https://colab.research.google.co...gpu72_tf.ipynb:50:25 get@https://colab.research.google.co...gpu72_tf.ipynb:36:25 get@https://colab.research.google.co...gpu72_tf.ipynb:37:25 I_@https://colab.research.google.com...ymer_binary.js?vrz=colab-20191025-092551-RC00_276702382:2519:66 Ida/<@https://colab.research.google.com/v2/external/external_polymer_binary.js?vrz=colab-20191025-092551-RC00_276702382:2562:424 za@https://colab.research.google.com...ymer_binary.js?vrz=colab-20191025-092551-RC00_276702382:12:336 xa.prototype.next_@https://colab.res...ymer_binary.js?vrz=colab-20191025-092551-RC00_276702382:10:453 Ba/this.next@https://colab.research.google.com/v2/external/external_polymer_binary.js?vrz=colab-20191025-092551-RC00_276702382:13:206 b@https://colab.research.google.com/...ymer_binary.js?vrz=colab-20191025-092551-RC00_276702382:22:43

[chalsall]

Originally Posted by David703

Hi, sorry to bother you guys, but I've been experiencing this error on all my Google accounts recently:

Hmmm... Google is being a bit "grumpy" this morning -- refusing to give my shivering virtual selves (read: SOCKS tunneled "human instances") environments. My two Barbados manifesting accounts are getting instances, but they are being killed after an hour.

But... No errors such as you're reporting.

A couple of thoughts... I do remember Google presents a warning message when running the GPU72_TF Section for the first time. Something along the lines of "Google didn't author this -- be sure you review and trust it before running". Perhaps you didn't acknowledge that?

Alternatively, rather than cloning from Github, you can also just copy-and-paste the code from the GPU72 "View Note Access Key" -> "Notebook Access Key" page into a new Colab and/or Kaggle Notebook.

Remember that both Colab and Kaggle are very particular about the copy-and-paste. You can't just highlight the code, and then middle-button-click. You have to highlight, then "Cntl-C", then "Cntl-V" into the Notebook Section.

Please let us know if either of the above resolves your issue.

[David703]

It always displays the message "Google didn't authorize etc etc" and I always press "Run anyways" so I don't think that is the problem. Just tried to copy and paste the code from the Notebooks Acces Keys section but Colab is still displaying the same error.

[chalsall]

Originally Posted by David703

Just tried to copy and paste the code from the Notebooks Acces Keys section but Colab is still displaying the same error.

Hmmm... Have you tried turning it off and on again?

That's meant to be funny, and serious, at the same time...

Perhaps try fulling exiting from your browser, and restarting. I can't think of a reason a full reboot would be needed, but if a browser reset doesn't help, perhaps try going to Settings, and flush your cache.

[David703]

Tried to exit Firefox and then run Colab but it still displays the same error. Not weirdly, it seems to work fine using Chrome, it must have to do with the dozen addons I installed yesterday. I'm going to try to disable them one at a time and see which one is causing problems. Will let you know if I can figure this out.


EDIT: Just found the problem: the addon "Trace" was somehow preventing the cell from running, now that I jave disabled it Colab works fine, thank you guys for your help!

[chalsall]

Originally Posted by David703

EDIT: Just found the problem: the addon "Trace" was somehow preventing the cell from running, now that I jave disabled it Colab works fine, thank you guys for your help!

Excellent. Good you found the cause of the "regression".

It's our pleasure to help with stuff like this. It's an important way to find the "edge-cases" of our code.

[David703]

Sounds great! I would like to ask just another thing. Out of sheer curiosity: how come trial factoring a number in the 97M exponent range from 2^74 to 2^75 "costs" around 40GHz-days while an exponent in the 63M range still from 2^74 to 2^75 costs 60? Why, in general, is the TF algorithm that we run slower with lower exponents?

[Uncwilly]

Originally Posted by David703

Sounds great! I would like to ask just another thing. Out of sheer curiosity: how come trial factoring a number in the 97M exponent range from 2^74 to 2^75 "costs" around 40GHz-days while an exponent in the 63M range still from 2^74 to 2^75 costs 60? Why, in general, is the TF algorithm that we run slower with lower exponents?

The number of candidates that need to be tested at each bit level goes down as the exponent goes up. Any divisor of a Mersenne number must be in the form 2kp+1 , where the p is the exponent in question. As it gets larger, there are fewer numbers in each bit size that will fit that requirement.

[David703]

Originally Posted by Uncwilly

Any divisor of a Mersenne number must be in the form 2kp+1 , where the p is the exponent in question

Oh, got it, thank you!

[dcheuk]

Just got assigned 2 Tesla P100s on 2 different accounts!

[dcheuk]

Originally Posted by dcheuk

Just got assigned 2 Tesla P100s on 2 different accounts!

Make it 3 including my university's google account.