Recently I've attempted to upgrade to GWT 2.8 but ran into an issue where a small number of users report browser tabs hanging (eventually putting up kill/wait popups) in Chrome 55.0.2883.95 and Safari 10.0.2. Seems to affect Mac users primarily. Going back to GWT 2.7 made the issue go away. I haven't been able to reproduce the issue myself, so it doesn't seem to be a general problem. Has anybody experienced anything similar after upgrading?
Related
We are seeing a really weird issue with our production site where after 30 seconds it appears that the session is invalidated in the Chrome and Edge browsers. We don't see any errors in the chrome inspect console.
We saw this behavior on 25MAY2022 right around when chrome 102 got pushed to the browsers at 5pm. IF we use inspect and turn off the cache then we don't see any issues with loading the site and everything operates fine.
FireFox works fine.
I'm using chrome 101.0.4951.61 against the same site on my android 11 phone and I cannot reproduce the issue.
Are there any new features in 102 we could turn off to see if a specific new security check might be at play?
My team is experiencing a similar issue when calling our API. If you go to chrome://flags/#private-network-access-send-preflights, and disable it, does that resolve your issue? If it does, then adding this header to your site may resolve the issue:
Access-Control-Request-Private-Network: true
We are currently doing pre-prod testing which is so far promising.
https://developer.chrome.com/blog/private-network-access-preflight/
Chrome ERROR_TIMED_OUT in latest version
I'm having an issue related to a PWA which was created using Blazor.
This app worked fine until yesterday which starting failing in Google Chrome in mobile devices only.
I'm using Chrome 91.0.4472.88 Android 8.0
The weird thing is that the app is working fine in mobile Opera and also in any browser in desktop computers.
The app is hosted using IIS 10.0
I debugged a bit and I found this error output
This error is only happening in Google Chrome mobile version.
I tried updating to target build net 5.0, maybe this has been solved, but it does not fix the error.
I found some related links to this issue, but no luck
https://github.com/dotnet/aspnetcore/issues/26698
https://github.com/dotnet/runtime/issues/42628
Anyone has an idea how to fix this problem? I'm out of ideas.
This appears to be something with Chrome 91, which has all kinds of significant performance optimizations that, for me, tanked Blazor apps (or at least mine). My app will work on Android Firefox, but I get errors like this, and/or memory errors, since the browser updated to 91. I find it hard to believe that we're the only ones, but I haven't seen any wider concern among Blazor devs.
I'm working on a project using KineticJS version 4.6 (currently the latest version), and since last night's Chrome update to Chrome 29, the Kinetic canvas is completely blank. While using the console, I am still able to detemine that the created objects, such as the Kinetic.Stage and Kinetic.Layer, still exist and are filled with correct data.
Afterwards, I tried loading the same page in Internet Explorer and Firefox, and they still work as intended, showing the canvas with the correct elements.
I have tried searching for people with similar issues, but I guess Chrome's update is too recent to show any results. Does anyone perhaps know if there is a way to fix it or if I should simply wait for either a KineticJS or a Chrome update?
EDIT: And now it suddenly works again after restarting Chrome. Hotfixed?
EDIT2: After a while it broke again, but restarting the browser seems to work
EDIT3: It is a bug in Chrome, acknowledged by the Chromium team in this thread. The thread states that the bug is definitely fixed in version 30, which is currently in beta. This fix may be merged in version 29 soon, but there is no definitive timetable for this.
We have the same problem in Chrome 29.
In some cases a workaround is to tell your users to use Chrome Incognito mode to fix this issue.
A test to replicate the issue consistently is posted here:
https://github.com/ericdrowell/KineticJS/issues/585
At present, the bug is not present in Chrome 30. (8/27/2013)
You should star this chromium issue:
https://code.google.com/p/chromium/issues/detail?id=280153
I'm trying to understand these strange rendering error boxes that are too big to be ignored. This seems to happen on Chrome in Windows 7 (my testing isn't too elaborate) and nowhere else. When I attempt to inspect, they all disappear. This could be some kind of video card issue as I'm using some pretty advanced CSS3 transitions that could mess up memory. In any case, if someone could offer advice on what I could do to fix, I'm at a loss. The site is www.crane-usa.com
Having the same issue with our site using 21.0.1180.89 and 21.0.1180.79. Problem is in Windows 7, Mac OS X latest, Ubuntu and in Chrome frame running in IE9. IE9 with Chrome frame disabled works fine. The problems are intermittent and unrepeatable. Inspect element removes the problem as you say. I tried disabling GPU compositing via chrome://flags but that didn't fix the issue.
We and our users have only been seeing these issues since approx Aug 27, 2012, 3 days ago. I took a look in crbugs.com and found that this seems to have existed for a couple of weeks already. http://code.google.com/p/chromium/issues/detail?id=143647
Sorry our site is not public so I can't post our url but you're not alone.
I'm having trouble with a website of ours that is not displaying images on Mac Safari
The exact same website is on a dedicated server and works fine.
When we moved it to a load balanced environment the images stop working only in Mac Safari, but still works in all other browsers including windows safari, and Firefox on the mac that had the original problem.
We tried other macs, and the problem only exists on macs running OS version 10.4.etc
The problem presents itself on ALL versions of safari on the Mac running 10.4, and the problem disappears on ALL versions of safari on Macs running other versions.
The website is built on Community Server.
I've done some googling, and I found various forums that mention the problem, however they are all from a client side perspective and they say that this issue only affects certain websites. I haven't found any developer related material that explains how to fix it from the code side.
I'm reaching out to the Mac website developers, because I am definitely not a Mac user, and I have no idea how to proceed. Any links or ideas that could get me started?
You can solve this by
making sure Safari's proxy is set properly
bypassing Safari's cache when refreshing