Hey, all. I'm working off a chromium browser, the browser in question is Torch.

I keep getting the "Aw, Snap" error whenever trying to load any image with the Absurd Res tag. It's obviously not the tag itself but the res that's the issue, but I have no idea what that issue could be.

All other pages load just fine, regardless if flash, video, etc, but any image that's absurd res crashes that page and all other e6 pages I have open, whether they're in a different window or just a different tab.

This started happening fairly recently, less than a week ago, IIRC, and as far as I'm aware nothing has been installed or changed on my browser or computer. I've done malware and virus scans within the last 24 hours and things have come up clean (said scans were normal scheduled, not specifically for this issue.)

I've also disabled each and every extension I have one by one. I've found that the problem still persists despite this. I have, however, found that toggling off my "Enable Right Click" extension (Found on the Chrome store here https://chrome.google.com/webstore/detail/enable-right-click/hhojmcideegachlhfgfdhailpfhgknjm or disabling my "allow copy" extension here https://chrome.google.com/webstore/detail/allow-copy/abidndjnodakeaicodfpgcnlkpppapah helps as doing either one of those things makes it so I can refresh the absurd res page.

However disabling both, or, indeed, even all of my extensions doesn't offer any improvement, absurd res images still require me to, at the very least, refresh the page a few times before they load properly and, indeed, when it crashes it still crashes all other e6 pages open.

Any insight as to why this may be happening would be really appreciated.

Have you tried any Chromium browsers other than Torch?

Absurd res images are working just fine for me with Chromium 53.0.2785.143 (64-bit) for Linux.

Tuvalu said:
Have you tried any Chromium browsers other than Torch?

Absurd res images are working just fine for me with Chromium 53.0.2785.143 (64-bit) for Linux.

I don't have any other browsers installed and don't really want to install any other browsers, choosing another browser isn't a solution and I didn't figure any others would have the issue as there aren't any others complaining about it.

It seems to be a localized error. I'm more than happy to provide any additional information.

I'm apparently on version 51.0.0.11603 currently.

I do have Edge (because win 10) and it loads up the image perfectly.. so definitely just a localized problem with this browser.

I just pulled out a computer to test with, I'm getting the same result with Torch Browser on Windows 7, as well as with the 32-bit version of Chromium.

A 64-bit install of Google Chrome is working just fine, however.

It doesn't appear That Torch has a 64-bit version right now, but according to their site there is a 64-bit beta which should be coming soon.

Torch auto-updates, so it's likely they broke something with the latest set of hotfixes. I'd recommend either filing a bug report with them directly, or waiting until they fix it.

Personally I would recommend to always have a spare browser flying around, preferably something Firefox based if you use a Chromium browser, or the other way around. Some things are optimized for one render engine but run sluggish on the other, so it's quite convenient to be able to test the page on the other one.

For Firefox you can tell the browser to not install the auto-update during installation, that way you won't have another process running in the background unless you actually open it, something that chrome vehemently tries to force.

Thanks, all. Good to know it's nothing I can fix. Well.. sorta, good in the way that it's good to know what's going on, you know?

Huh, I'm having any kind of issues using the latest version of Torch on my (now-recently-re-installed) Windows 10 machine... If it helps at all, I'm using a 64-bit version of Windows 10.

Edit: I just now realized I said "I'm having". I meant to say "I'm not having"