We are using a headless Chrome to take screenshots of our websites. Because on startup there are some animations we set a timeout of 10 seconds before we take the screenshot. We are running all of this on an AWS lambda. It sucks though that we actually have to wait 10 real life seconds. Is there a way to tell (headless) Chrome to fast forward (or "fake") 10 seconds?
Related
I got a Colab Pro+ because I wanted to use the background execution option.
I enabled the background execution and GPU type and started my code.
My code is a simple CNN on Tiny ImageNet, which requires several hours of training on a GPU.
I closed the browser, and after one-two hours, I returned, and everything was frozen!
How can I resolve this issue?
This happens to me as well and the best solution I've been able to come up with (which works inconsistently, but seems to help a lot more that otherwise) is to prevent my screen from locking. Let me explain.
I run Colab Pro+ on a Macbook laptop, and the battery-saving settings are ordinarily such that the screen locks when the laptop is idle for 5 mins, the lockscreen comes up. I noticed that for some reason Colab was much more likely to freeze and disconnect if I was away from the laptop than if I were working on it for hours as it ran, so to superficially mimic this, I changed my settings to never lock the screen. And I then I realized that with these settings Colab would freeze and disconnect much less frequently, and I could successfully let it run overnight and check it in the morning. [Edit: let me clarify that I have not tried this while closing the browser. So I can attest to the efficacy of my method if you leave the browser open].
I have to say though, that it's been bad for my laptop and it's unacceptable that this is necessary despite what we pay for Colab Pro+. Their product simply does not work as advertised and we have no recourse. If anyone has discovered a better solution (that works) I'm all ears.
An alternative that works for me is to make the navigator click with some interval. You can add the following script to the console. It works well with Colab Pro and Pro+ but remember that, if you use the free account, Colab will disconnect you after some hours.
To open the console press F12 or ctrl/command+shift+i.
function Clicking(){
console.log("Clicking");
document.querySelector("colab-connect-button").click()
}
setInterval(Clicking,50000)
When I was developing my Chrome extension I used the alarms API, and it worked without any issues. After uploading it to the Chrome Web Store, it doesn't trigger at the scheduled times (I am settings timers greater than one minute). I tested with a 5 minute timer, and it took 5 minutes and 47 seconds to trigger. I am considering switching to setting a timeout for the timers, but would prefer to use the alarms API. Below is a screenshot of the scheduled time going over the actual time.
Any ideas on how to fix this?
recently, I find Chrome devTool have no Frame mate anymore, but Frame Rendering Stats, They are different panel. I can get real time FPS before, but now, it just show me how much Frame ploted and how much droped, and memory use. if I want FPS, must record preformance and analys it of write script to compute it.
so, is there any method to get real time FPS directly
I keep on typing in the google Colaboratory but it has happened three times now I left for like 2 minutes to check of some other things onto a web browser, at the same time 90 minutes finished and the runtime disconnected, which mean it wasn't idle for 90 minutes, it just disconnects me after 90 minutes anyways. Does it have to do with where I live maybe? India
I had this issue many times due to bad internet, if that's not case switch to GPU runtime and try.
How does google calculate waiting time and receiving time in chrome network panel?
There are 4 timing categories in google chrome network panel
1.) Blocking
2.) Sending
3.) Waiting
4.) Receiving
I would like to know what all factors are included while calculating these options.
From this link
High "Receiving Time" for HTTP Responses below 500 bytes in Chrome Devtools
an explanation is there for receiving, but I would like to know about all the options in a bit more detail. Can anyone please help me out here ?
It appears that the timing functions may be platform related.
I have an internal web site and the access times reported for the same transactions appear vastly different. For example, my Windows 7 (latest Chrome) shows total response times as 200ms (almost 190ms of receiving) while my Ubuntu laptop shows a total of 4ms on the Chrome Network tab.
I also put timers on my server side first, just to make sure that it was not a delay in my node.js server (running on a different ubuntu box - not the one that has the Chrome client).