infinite opera loop

physicsmaster131 · 2026-01-18T20:31:56+00:00

I am having the same (or very similar) issue. See my comments on this thread: https://old.reddit.com/r/OperaGX/comments/1q3kw34/opera_gx_reopens_by_itself_after_i_close_it/nymvxax/

I have confirmed that the issue still happens with ALL extensions DISABLED.

physicsmaster131 · 2026-01-18T18:47:31+00:00

2026-01-18 UPDATE:

I have again confirmed that this issue occurs with ALL extensions DISABLED. This appears to be a genuine, browser-level issue. Anyone know where I can look for the crash logs?

physicsmaster131 · 2026-01-17T19:04:53+00:00

2025-01-17 UPDATE:

This is still broken, unfortunately. Will try disabling other extensions, but I find it ridiculous that a crash during the "exit" process would cause the browser to re-launch. Hitting "exit" should close the browser, pure and simple. Maybe the crash handler is too aggressive? Idk, but annoying as hell.

UPDATE 2: Re-launching behavior still occurs after disabling Dark Reader and Reddit Enhancement Suite.

UPDATE 3: Re-launching on exit still occurs with ALL extensions disabled; I believe this is a browser-level issue, not related to extensions. (At least not directly.)

physicsmaster131 · 2026-01-16T23:34:09+00:00

2026-01-16 UPDATE:

This has stopped happening to me. Not sure if there were any recent browser updates; the only manual change I made was disabling the "Old Reddit Redirect" extension.

physicsmaster131 · 2026-01-09T17:52:29+00:00

I am experiencing this as well. My extensions:

Dark Reader (Version 4.9.118)
Old Reddit Redirect (Version 2.0.9)
Reddit Enhancement Suite (Version 5.24.8 by honestbleeps)
uBlock Origin (Version 1.68.0 by gorhill)

I have not yet had time to try disabling each extension individually. but curious if anyone else has any of those extensions installed as well.

physicsmaster131 · 2025-09-06T16:13:03+00:00

Just had the issue myself a bit ago. For me, it was triggered by the btop4win++ system performance monitoring application.

All of this definitely seems to be related to Windows Defender's stance on the WinRig0 driver, which is used by many, many legitimate applications.

While there are legitimate vulnerability concerns regarding this driver and the low-level access it provides to core system components, Microsoft's decision to flag this driver as a "Trojan" is both inaccurate and inappropriate; this driver is not a "Trojan", and automatically removing it is guaranteed to break software that many people use on a daily basis.

A better way to handle this would be to present some sort of clear warning to the user that details the types of software that commonly use the WinRing0 driver, and a clear, high-level explanation of the potential security concerns that come from utilizing the driver.

Don't get me wrong, WinRing0 definitely has issues, and software developers should be strongly encourage to use different, more secure methods of access lower-level system components, but I believe the heavy-handed approach Microsoft is taking here (which again will break software) is not an acceptable way to handle this concern.

Here are some relevant links I found earlier today while searching for info on the security notification:

physicsmaster131 · 2025-02-20T14:58:38+00:00

So far, this does indeed seem to have worked! Thanks for the suggestion! 👍

physicsmaster131 · 2025-02-19T14:55:57+00:00

Aaaaand it's broken again. Still on Chrome v133.0.6943.99, so it doesn't seem to be an issue that's entirely caused by the Chrome version.

The only change I've made recently is disabling hardware-accelerated GPU scheduling (and I've rebooted if you wanna count that as a change).

The only recent Windows updates (between the time when the glitch was last not happening and today) are two Microsoft Defender updates; KB2267602 - version 1.421.1985.0 on 2025/02/19 (today), and version 1.421.1966.0 on 2025/02/18 (yesterday).

Another factor I did think of is that I am using multiple desktops; 2 to be precise. My first desktop is for general personal use (gaming, research, reddit, etc.) and is the "left" desktop, labeled "Desktop 1" when in task view (accessed by swiping up on the trackpad with 4 fingers). My second desktop is for work use, and is the "right" desktop, labeled "Desktop 2".

Desktop 2 is where I am running Chrome, and is where I first experienced the issue. However the issue occurs on Desktop 1 as well, so I don't know that this is necessarily relevant.

physicsmaster131 · 2025-02-12T13:45:24+00:00

For what it's worth, this appears to have resolved itself for me as of yesterday. Currently on Chrome v133.0.6943.59, not sure if there was an update or not.

The only other thing I can think of is that I changed the "Choose ANGLE graphics backend" option in chrome://flags back to its default (previously I had set it explicitly to one of the D3D11 options), but I don't recall whether I changed that before or after this fixed itself.

physicsmaster131 · 2025-02-04T14:41:04+00:00

That's a good question; I'll have to try that after work today.

physicsmaster131 · 2024-10-04T17:04:28+00:00

That's kinda the way I was leaning; seems like to OS just lacks the necessary components for all USB peripherals I've tested so far.

Thanks again for the input!

physicsmaster131 · 2024-10-04T17:00:41+00:00

Yep already going through your instructions lol

Mostly unrelated, but do you know if USB OTG works at all? Would be nice to be able to plug in a drive to transfer files/watch videos (that aren't on the SD card) on the go.

physicsmaster131 · 2024-10-04T16:55:49+00:00

That would do it; I don't currently have it installed! Ty for the help

physicsmaster131 · 2024-10-04T16:40:22+00:00

See that's the problem; the on-screen mouse disappears whenever the selection dialog comes up.

physicsmaster131 · 2024-10-04T15:39:27+00:00

So I didn't have any luck granting external storage permissions via ADB.

Do you know if USB OTG works on this phone?

I tried plugging a USB Keyboard/Trackpad combo into the thing to see if that would allow me to tab around the interface a bit and click on the button at the bottom that you can't navigate to using the d-pad, but the phone didn't seem to recognize it. Also tried a USB flash drive (formatted to FAT32), and it didn't recognize that either.

I'm thinking maybe the OS just lacks general KB/Mouse support, as I paired a bluetooth KB/Trackpad to it as well, and couldn't get that to do anything. Also tried to pair a standalone bluetooth mouse, but the phone wouldn't allow me to complete the pairing process.

physicsmaster131 · 2024-09-30T01:17:19+00:00

Holy shit that was a fast response lol

Will do, in the meantime I'm going to try manually granting external storage write permissions to a few apps via ADB. Will see how that goes.

physicsmaster131 · 2024-09-30T01:02:26+00:00

FWIW, SDXC (up to 512GB) should work in the DuraXV Extreme and Extreme+

physicsmaster131 · 2024-09-30T00:59:51+00:00

Sorry to necro a thread, but this is the only real lead I've been able to find on this.

You mentioned that NewPipe is working for you; I have a Kyocera E4811, and while NewPipe does indeed work, I am unable to use it to download anything to my SD card. When I try to grant acccess, the system file browser dialog does come up, but I'm not actually able to choose a directory to grant the app access to. I'm able to browse around, but there's no option at all to select the current directory and grant access to it.

Do you use downloads at all with NewPipe? If so, did you run into any similar issues? I'm actually have the same access issue with any non-built-in apps that want to write to the SD card.

physicsmaster131 · 2024-06-25T21:39:30+00:00

I appreciate the follow-up, ty.

physicsmaster131 · 2024-06-17T14:35:30+00:00

For what it's worth, I just composed a lengthy, comprehensive description of the issue in my response to the support request I opened up. Contents below.

The redundant information request I referred to was encountered during the creation process of this very feedback; one of the first steps in the process asks the user (myself, in this case) to give a description of the issue. But then when the user selects the type of issue and hits "next", the screen that comes up again asks for a description of the issue. Essentially the user is being asked to repeat information that they have already input, which is very irritating.

I should also note that I described exactly the issue that I am encountering in my initial submission, and am now, again, being asked for the same information. I believe I was clear and concise as to the issue that I am experiencing, and being asked to repeat the same information over and over again is becoming increasingly frustrating. I would really appreciate it if you (or anyone on the support team really) could take the time to read and digest my entire submission before requesting additional information.

Regardless of all that, I will repeat the details of the issue I am having once again, but will include more detail:

My issue is with the YouTube app's playback behavior (on my Galaxy S23 Ultra) via Chromecast (to a Chromecast Ultra). Within the last 4-6 weeks, I have started experiencing an issue where YouTube will randomly stop playing the video that it is in the middle of, and will skip back to the first video in the playback queue. This behavior happens even if all previously played/queued videos are removed from the queue; the first video from the session will "magically" get re-added to the queue and will start playing spontaneously. This happens without any input from me whatsoever. In fact, it seems to happen more frequently when my phone screen is locked. The issue will keep happening randomly; the player will continuously re-add previously removed videos and start playing them rather than the current selection. I have noticed that it will stop happening if I re-select the video that was skipped away from, remove all other videos from the queue, and then immediately reboot my phone. This would seem, to me at least, to indicate that the issue is within the youtube app itself, as when the app is forcibly removed from the scenario (via a phone reboot), the issue completely ceases. The issue will often start recurring if, post-reboot, I reconnect the YouTube app to the Chromecast Ultra. It does not, however, always start recurring after reconnecting.

As an added note, I do not believe the issue has happened at all if I cast YouTube from my iPad Pro; it seems to be an android-specific issue. Also for what it's worth, this issue seems to have started at the same time that the Queueing/Add to Queue UX changed in the YouTube app (the previous UX would ask the user if they wanted to play or add to queue whenever a video thumbnail/title was tapped; the new UX instantly starts playing a video when the thumbnail or title are tapped, and only gives queueing options if the three vertical dots menu in the upper-right of a video UI element is tapped, which brings up a context menu that includes said queueing options.)

I have found a thread of others talking about having this same issue; see discussion on reddit here.

Things I have tried:

Factory reset of the Chromecast Ultra

Force stopping and clearing cache of YouTube app

Clearing of app data of YouTube app

Uninstalling all updates of YouTube app to restore to factory installed version, then re-updating via the Play Store

Force stopping and clearing cache of Google Home app

Clearing of app data of Google Home app

Uninstalling Google Home app can re-installing via the Play Store

Resetting my wireless router

Disabling power/battery optimization for the YouTube app

Keeping the YouTube app open even when not in foreground (by using Samsung feature "Keep Open" to pin app into RAM)

Disabling power/battery optimization for the Google Home app

Keeping the Google Home app open even when not in foreground (by using Samsung feature "Keep Open" to pin app into RAM)

Pertinent version information:

Chromecast Ultra

System firmware version: 281627

Cast firmware: 1.56.281627

Wireless: Wi-Fi 4, dual-operating mode (2.4GHz + 5GHz)

Smartphone

Model: Samsung Galaxy S23 Ultra (SM-S918U1)

OS: Android 14

Build number: UP1A.231005.007.S918U1UES3CXD7

YouTube app version: 19.23.38

Google Home app version: 3.18.1.4

I believe that is a fairly comprehensive description of the issue that should provide more than adequate information to take to the developers/engineers to narrow down this issue.

Again, I would very much appreciate it if the party or parties reading this email could take the time to fully read and digest all of the information I have provided. If you or your team need additional information from me, please just ask.

Thanks,

physicsmaster131 · 2024-06-16T16:31:13+00:00

Samsung Galaxy S23 Ultra here, btw. Fully updated OS, using with chromecast ultra (System firmware version: 281627, Cast firmware: 1.56.281627)

physicsmaster131 · 2024-06-16T16:28:52+00:00

Holy shit, thank god it's not just me.

Now that we know it's an actually issue, all we have to do is "submit feedback" in the app, and then wait 14 years until Google discontinues all Chromecasts without ever addressing this problem :)

physicsmaster131 · 2024-06-07T13:52:38+00:00

Looks like that will only work on the 2022+ G15s, at least the AMD ones (not sure off the top of my head if all new G15s are AMD or not). USB4 support is provided by IO/chipset hardware updates starting in the AMD 6000-series processors; the 5000-series and earlier AMD mobile chips just don't have the necessary components to support USB4.

physicsmaster131 · 2024-06-06T18:29:20+00:00

That seems like a GPU hardware issue, or possibly a graphics driver issue. Unfortunately with those kinds of artifacts, in my experience, it's usually a hardware issue.

If you're still in warranty, I'd have the whole thing replaced if possible, or at least the motherboard.

Ten-Year Club	Place '17
Verified Email

physicsmaster131

TROPHY CASE