Chrome developers are working to end one of the internet’s long standing gags, that of Chrome munching every bit of RAM it can get it's hands on. The Chromium Gerrit project is in very early days and we don't have much information on it all except that they are working to develop a version of Chrome which "sets budgets for certain resource types". The idea being that when you stop interacting with a page or tab, Chrome will stop large scripts from running until you start using that tab again.
In theory this should provide a way to reduce the amount of system resources an idle page gobbles up, and The Inquirer, among others, hopes this will be more effective that current add-ons designed to do this. With Microsoft intending to move Edge to Chromium, this will benefit quite a few people if ever successfully implemented.
"Full details are held on an unreleased design document, and we're far too early for even the Canary channel users to be seeing it in the wild – it may never happen at all, though it's very much hoped that it will."
Here is some more Tech News from around the web:
- AMD allocates Blighty fewer than 100 Radeon 7 GPUs, claims retailer @ The Inquirer
- New Technique Allows Scientists To Create Materials That Get Stronger With More Use @ Slashdot
- Is this a wind-up? Planet Computers boss calls time on ZX Spectrum reboot firm @ The Register
- Researcher Reveals a Severe, Unpatched Mac Password Flaw To Protest Apple Bug Bounty @ Slashdot
- RIP, RDP… nearly: Security house Check Point punches holes in remote desktop tools @ The Register
- Microsoft fixes pricing for Windows 7 extended support @ The Inquirer
All browsers should force any
All browsers should force any ads/ad scritps to run on a dedicated core that users can select with each ad given a limited amount of RAM and processor time, that is also very limited by design.
That should force the ad folks to optimize their crappy ad scripts and limit the amount of processor time and system RAM/other resources that ads can take up.
While we are at it all ads/ad scritps should have to be registered with an industry wide ad registration organization that vetts that the ad/ad script as non nefarious and registers a unique identifier for that ad and its script package as well as a digital signature that is encrypted by the ad registration organization and only accessable via the ad registration organization for verification uses.
Let’s fruther sandbox the ads/ad scripts to running in a VM like environment that’s running on that single dedicated CPU core with the VM environment set to a hard limit on System RAM and only twice that RAM Linit of virtual memory swap file space that’s managed by the VM/Sandbox envrironment.
Enough with these repeating Video ads and other such resource thiefs. Because we all know that it’s the ads/ad scripts and the attendant Scripted snooping services that come packaged with the ads via those scripts that are what’s taking up all of that system RAM/resources. It’s also causing the system page faults to go off of the charts with memory to SSD/Hard-Drive paging activity that can wear out SSD based storage devices or cause their warranty period drive write limits to expire sooner even if the SSD has not failed.
Also under your Tech Talk sub-headlines section that’s also up for discussion.
“• AMD allocates Blighty fewer than 100 Radeon 7 GPUs, claims retailer @ The Inquirer”
That’s just one retailer’s limits and not every Retailer in the Land Of Big British Smiles! [Ralphie Wiggum screams in Terror!]
Sure limit those Radeon VIIs to only the largest consumer markets while any smaller markets will have to wait for it, wait for it! Wait for Navi! Who do those Redcoats think that they are!
And one one other Tech Talk subject:
“• Microsoft fixes pricing for Windows 7 extended support @ The Inquirer”
And that’s a great deal to many businesses/enterprises that Have Had very expensive to vett/certify mission critical software that cost a bundle to get vetted/certified to run properly under Windows 7. So that’s 3 more years time that any company, without the funds to be doing that expensive vetting/certifing on any new OS, has to get/arrange some funding. That was true for the reasons many enterprise/SMBs/Mom-and-Pops, and even government agencies, purchased the XP extended support when M$ offerd that to business/enterpries license holders on that OS version.
This is especially true for the terrible innards of Windows 10 that are always in a constant state of BETA Flux and one hell of a moving target to try and certify and vett any businesses mission critical software for the kind of uninterrupted business operations that are necessary least chapter 7/11 may be required. When XP and 7 where in development and service M$ had a QA/QC department and not some farmed out like exists for Windows 10 and all that 10 nonsense!
The problem is that then the
The problem is that then the browser needs to figure out what is an ad to render the page. It’s not a bad idea, just really complicated to implement. (Sure, you can just force everything to run in the background. But then it might break for other valid use cases, like video inline in a Facebook feed.)
Easy because the ad has a
Easy because the ad has a unique identifier and is registered as and ad with an –>industry wide ad registration organization<-- so the browser will have no problems! And because the ad has to be registersd and vetted/certified by an -->industry wide ad registration organization<-- before the ad can be pushed out to the browser that's already a solved problem. And to pass the -->industry wide ad registration organization’s<-- Vetting/Certification process the ad has to be scanned as well as the ad's script for any nefarious Code/Images(steganographically embedded) nafaroous payloads with all that attack vector nefarious ad nonsense being reduced to as little as possible. Other script standards can be applied by the -->industry wide ad registration organization<-- such as disallowing any ad script from messing with the browsing experience by flipping the scroll functionality of the browser up/down to move point the window to the ad and disrupting the user's browsing experience. ditto for autoplaying video ad content and ad scripts that mess with the browsing history to load more ads when the user uses the browser's navigation buttons to navigate backwards or forwards. There are loads of disruptive ads that are taking advantage of the HTML standards and the browser's navigation/UI fuctionality to really break the user's balls with those annoying ads that play with the Browser's UI functionality beyond the user's control!
Chrome developers lack of
Chrome developers lack of relevant ideas so they thought it could be “cool” to reimplement the process scheduler inside the web browser…
That’s so sad the silly-cost valley have too much cash to burn in that sh!t! :-/
So this will be what, the
So this will be what, the 15th time we’ve had a story about Google’s new update to lower Chrome’s memory leaks, errmm usage. By now it should be providing RAM back to the system. I call BS like all the other measures that have done bugger all. Admit it, they are crap coders.