|
Wheany posted:Opera 12 was getting a bit laggy, so I looked at its information in process explorer. It was using 7.2 GB of ram. Then again, I had started it on 12th August. I use Firefox as my other constantly running browser and it has crashed innumerably many times in the same span. Daaang! Mine usually starts doing weird poo poo around 4 GB (takes about a month to hit, usually) and I assumed it was because the binary was compiled with a 4 GB limit.
|
#
¿
Oct 10, 2014 06:24
|
|
|
|
| # ¿ May 22, 2024 08:24 |
|
|
Mithaldu posted:Same here. Maybe they changed something with the SSL on those sheets. 12 only supports old, generally-considered-broken TLS implementations, so it's going to get harder and harder to use as everyone gets better about/at encrypting everything. The only solution I can think of is connecting through a proxy that speaks the new TLS suites to the world and the old ones to Opera, which is basically MITMing yourself  Can Opera use a proxy that's not set up as the web proxy for the whole system? This is really only feasible if only Opera 12 (and any other old un-patched software) can be shunted through the proxy or if the proxy can silently pass through newer implementations because modern browsers will probably start throwing up error pages for outdated crypto pretty soon.
|
|
#
¿
Feb 9, 2016 17:36
|
|
|
Mithaldu posted:See thread title. Hah, fair enough. quote:You can actually switch proxy usage on/off per *site* (though not which proxy). Nope, sorry. Just a thing I've been thinking about because of the headlong rush into https everyone's been on: what happens to all this legacy stuff people still use? I don't think it'd be all that hard to get a simple passthrough proxy working on Windows, but working properly without making the user even less secure is a whole 'nother thing.
|
|
#
¿
Feb 10, 2016 21:50
|
|
|
Mithaldu posted:I think as long as i only run it on my local machine, security is not an isue. I poked stackoverflow to see if maybe something falls out. As long as it's only local, only responds to local traffic, only Opera uses it to 'upgrade' its security and the proxy doesn't have an even more broken TLS implementation*, yeah. Might be moot now that .18 is out, which is blowing my loving mind. I half expected it to be a stealth installer for Chropera *I can easily imagine a poorly written proxy silently failing to do TLS to the server and falling back to plaintext while still presenting the client a TLS connection, for example. People are real loving stupid sometimes.
|
|
#
¿
Feb 16, 2016 04:00
|
|
|
At least they're trying to differentiate themselves from Chrome 
|
|
#
¿
Jan 24, 2017 18:39
|
|
|
|
| # ¿ May 22, 2024 08:24 |
|
|
Could be one of the ad scripts started using newer Javascript features than Opera supports, so the script would very likely fail to parse and appear blocked to other scripts, but that's just a guess.
|
|
#
¿
Oct 5, 2017 16:37
|
|