Here's a new one:
At some point in the last few weeks, printing to my wireless network printer, a very average HP OfficeJet 6970, causes
all Chromium browsers to crash at the printer selection screen, upon choosing it.
(By "all" I mean the three I tested--Vivaldi, Chrome itself, and the Edge Chromium beta.)
Every other program can print over my network. Every
non-Chromium browser (like Edge or Internet Explorer) can too. It's just the magic of crashy Chromium. Reinstalling said browsers obviously did not work. Nor did reinstalling said printer after wiping the drivers. The printer
does seem like the culprit--if it hadn't been updated recently, and if everything else had no issues seeing it. I'm short of USB ports as it is, hence the need for wireless printing. I can print everything as a PDF, and use Acrobat Reader to print because it doesn't suck and crash, but that's an extra step I'd like to avoid.
Anyone else run into this? It's almost a common issue on Chrome forums, but the answer seems to be "Yeah, we don't know what's wrong. Try deleting Chrome's folder in AppData and maybe it'll help. Or not. Who knows."
Posts
Then hope for the best.
https://steamcommunity.com/profiles/76561197970666737/
Doesn't sound like it'll work, but Revo Uninstaller sounds like a handy tool. I don't have a brutish uninstalling program presently, because Windows 10 is good about that. And there's barely any software for the printer anyway.
Chromium: Still Crashy, just the way you remember it. It's going to kind of suck if I somehow fix this for Chrome (which I don't use) but not Vivaldi (which I do). Fortunately, it probably won't come to that, and everything will just stay crashy.
https://steamcommunity.com/profiles/76561197970666737/
I gathered. Did not work, as expected, and I was more than aggressive (I even actively reinstalled all related programs just to wipe out the traces).
Vivaldi (and Chrome, etc.) are just crashing when they try and access my particular networked printer. It's a semi-common issue, the solution being "Eh, try deleting some files. But it'll come back."
It was worth a try. Did some house cleaning for fragments of Chrome left over.
No idea. Is that some sort of early preview version? The issue is found in other versions going back a few years, so I doubt that would help. If it hits you, it hits you, and that's about it.
One of us, one of us
Steam | XBL
I mean, it's not great so far. Leave it alone for 20 minutes and it hangs (and frequently crashes) when you return. I turned off hardware acceleration, hoping that helps.
Firefox is crashing too? Like, in general?
Sounds like it's fresh install time.
https://steamcommunity.com/profiles/76561197970666737/
Except Firefox is known to crash in this (it's a pretty common issue, that's how I got found the solution). Edge never crashes, and Vivaldi doesn't hang when left idle even overnight (only when you try and print something).
Plus, you know, "hangs after hybrid sleep" is different than "crashes upon printing".
EDIT: Firefox, at least for me, is also less snappy and responsive than Vivaldi or Edge, but I think this might be by design (it has a smaller memory footprint at least compared to Vivaldi).
I leave it idle for a couple of hours or more fairly often and it is always - and I do mean always - just fine when I come back to it. Multiple tabs and often multiple windows. No problems going in or out of sleep mode either.
Steam | XBL
It's been a common issue in the past too, though efforts were made to address it. There could be any number of causes--they just don't effect Edge (not surprising, given its relative simplicity and design for Windows 10).
Considering nothing like it happens in any other browser...yeah, I don't think reinstalling Windows 10 is the correct approach. Ironically, I actually performed an in-place Windows 10 upgrade pretty recently too.
EDIT: Turning off Hybrid Sleep mode seemed to address the issue--and with hardware acceleration on it's snappier. That's good!
It's an Extended Security Release. Basically it's a version where they lock the functionality to a specific patch number and only provide security updates. Then every 6 months they patch the functionality up to the current mainline version.
There's been a couple times where it's been really useful for me. I also just plain like the idea of separating security patches from functionality patches.
Even if that didn't help, that would also be a nice option for Vivaldi--I really should've disabled updated months ago, getting two patches a week multiple weeks in a row got old fast.
Now I just need to come up with a good solution to the "Firefox is already running, but is not responding." issue (another common minor issue that has a few solutions)
On the bright side, 1Password's old extension works much better with Firefox than Vivaldi.
Fuck you, Chromium.
That being said, once I ironed out the bugs and got used to the changes, I'm glad I acclimated myself to Firefox after having stopped using it back in university. I'll probably keep it as an option in case this same stupid shit happens again.