Not sure if this is the correct site to ask, tried SuperUser, got no replies.
I've been experiencing this issue for a while, but didn't really bother me until I started using Youtube for music and it hanged after every 2-3 videos.
Basically what happens is if I click on a new video or YT moves onto the next one, the red bar on the top gets stuck at ~75% and just nothing happens. The UI is still interactable but the only fix is reloading the page forcefully. Happened across multiple browsers (Chrome and Edge mainly).
At first I thought this was a networking issue, so I removed my PiHole and uninstalled any virtual network drivers I had (mostly VPNs) and rebooted both my router and my PC. The issue still persisted.
I started checking the Networking tab of inspect element to see what I find, maybe uBlock is blocking something. Well it was blocking something, but it wasn't my issue, as it still persist even if it is disabled. Networking tab with uBlock enabled looks like this:
I thought uBlock was doing something, so I disabled it. The issue went from the requests being blocked, to the requests being stuck on pending:
I tried the URL with an online API tester, and it just returns an empty object on a POST request, but it does return something, meaning something is wrong with my end. The dev tools menu said that a 'Cache-Control' header is missing, so maybe its an issue with caching. I cleared my cache and tried Shift+Refreshing. It worked for seemingly longer after that, but after 10-20 minutes it happened again. Current edge version is 89.0.774.75.
Any help is appreciated and if this is the wrong forum for this, I'll try again on SuperUser maybe I'll get lucky this time.
Here's the URL: https://www.youtube.com/youtubei/v1/log_event?alt=json&key=AIzaSyAO_FJ2SlqU8Q4STEHLGCilw_Y9_11qcW8
Related
I can't find anybody facing the same problem as mine.
Every time I click an image on google image, suddenly the whole page disappear, but I'm still able to click things just like everything is still there.
I already turn off all extension, use incognito mode, after finally I try to use inspect element, and found attribute stating "Opacity: 0" on the body. And after unchecking the box (Quick disable attribute in inspect element chrome) everything shows up again.
I'm so confused on why this is happening.
Does anyone have ever facing the same problem?
Or how do I fix it?
It's so frustrating, because I have to refresh the page, every time I click on an image, or switch between images
so I was having this one. in the end, it was a virus.
In my case, it was showing an AD screen on the main google page, and in the sources>gstatic.com it had a different source which also was in a [unknown] source.
dug a bit up and discover some adware was using gstatic as a proxy to show ads on all browsers.
I solved it by running malwarebytes, it found it pretty quickly and solved it for me.
Posting this here because I'm hoping it helps people who search for this issue in the future.
part of the log
i'm struggling with the classic HTML input of type file. I was using it on my angular application and i had freeze sometimes, the whole browser became unresponsive, and the only thing that works is the scroll.
You can't click any buttons, select any text or even change tab on the browser for about 5 seconds. I tried a lot of different file type and sizes and it doesn't change any of this, it even freeze sometimes when i don't select any file in the explorer and i click the close button directly.
So I thought it was my implementation that was bad and i went to the Mozilla developper website where you have an example and I have exactly the same behaviour. I also tried to take only the HTML from the Mozilla website and put it alone on a .html file and again, same behaviour.
This does not occur 100% of the time, but I would argue that on my end it does it about 60/70 % of the times.
I tried it on chrome and Firefox (both up to date), on multiple computer (all running Windows though) and i have the same behaviour on all of them.
I don't have any error or anyting in the consoles.
I don't know what to do with this, i'm pretty sure it can't be the file's input on the whole web that are bugged, but i tried a lot of various things with always the same results. Should i report it somewhere? ( if so, where? ) Or what would you suggest to do to investigate this further?
I couldn't find anyone discussing this issue on the internet apart for this thread that had no solution, they also say in this thread that the bug is not reproducible in Edge, but i just tried and it does the same thing.
Thanks for reading me and for any help about this.
Chrome freezes for few seconds when after any use of file field.
It was because I had a shortcut in "Quick Access" menu in windows explorer. This shortcut has been linked with a folder shared by network. I've removed this shortcut and everything is good now.
Same here, I have a mapped network drive that is not responding, this make a 5 seconds delay. After unmapping the drive, no more delay. The delay is the same in firefox or chrome.
Same here, if you want to remove it, on Windows 10, click on the icon Quick access (blue star), then right click on the dead link appearing in the "Frequent folders" panel on the right panel and choose "Unpin/Remove from Quick access". There should be no error message.
Hi all,
I am looking to record a live stream/video post on Facebook. I can see the 'Live' button when posting. Once clicked it takes you to this page (see screenshot) then gives this error "something went wrong, but we're working to fix it as soon as we can". Been like this for 2 days now.
This happens in Chrome, Edge and on Iphone. I can record a live stream using other facebook accounts on these formats though. I am using windows 10 if that helps?
The page address is takes you to is:
https://www.facebook.com/live/producer/?target_id=100050905598457&source=CAMERA&entry_point=feedx_sprouts
I know it's not specifically a programming issue, however I wondered if any coders could decipher what issues there may be. The only difference I can see is that the working account has upgraded to the 'new' facebook layout. Unfortunately, I can't update the facebook account I need to actually stream from yet, as facebook are still rolling this out.
Many Thanks
I have a link in my app that points to an app protocol of type myProtocol://". Until a few days ago this was working completely fine, whenever you clicked on the link, the native app would open.
However, iOS9.2 seems to have broken this. Now what happens is when the links is clicked, I get a prompt to open the native app which disappears after roughly 1 second, not even close to giving the user enough time to access. Shortly afterwards I get prompted to go to the App Store to the app's page.
Any idea why this is happening and what changes in iOS9.2 that is causing this would be helpful.
It seems that with iOS9.2, Apple is making a move towards Universal Links and traditional deeplinking is not supported anymore. While I was not able to find any information published direct on iOS9.2 release notes, following links indicate the same:
https://blog.branch.io/ios-9.2-redirection-update-uri-scheme-and-universal-links
https://www.adjust.com/overview/features/2015/12/11/ios-9-2-deeplinking/
Got an odd problem, only persistent in Chrome browser. Can't imagine what would be the problem. Chrome's "Back" button doesn't work, nor does history.go(-1), but works fine on all other browsers. To see the problem simply click this link, which will asynchronously initiate searches on two separate services, or sites if you will. Upon click on any search result list item, we traverse to another page, but "Back" doesn't work for Chrome.
http://vps-net.com/MSSMine/?search=some
Any suggestions or ideas are welcome.
I found the problem with the page you have linked, I don't believe it to be an issue with Chrome.
When you load the page, it also loads two iFrames as the request to the site finishes. Chrome takes a somewhat different approach to history, allowing you to navigate not simply from changes in the URL displayed, but through every new individual browser-initiated request. When the iFrames load, Chrome adds history for each step of the page loading process, creating 4 separate history items. When you go back 1 "page load", it takes you back to the site you linked to, at a different step in the process. You aren't seeing anything change because as soon as that page loads, any unloaded iFrame now loads again.
If you do history.go(-8) or some other large number, you should see the page at that many pageloads ago. However, if the link is opened "in a new tab" then the history begins for that tab at the URL you told it to open, effectively limiting the history to the pages that occurred during that tab's lifespan.
This was tested on Chrome 34.0.1847.116 running under Ubuntu 13.10.
My back button was not working as well, but it would not work with any browser. I went into my add/delete software and deleted what software was added the night before - BOOM! All is fine now.