New issue
Advanced search Search tips

Issue 842390 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 836230
Owner: ----
Closed: May 2018
Cc:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 3
Type: Bug



Sign in to add a comment

black boxes on chrome browser - multiple systems - persists after full wipe@restore

Reported by steelh...@gmail.com, May 12 2018

Issue description

Chrome Version       : 66.0.3359.139
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
URLs (if applicable) :
Other browsers tested:
  Add OK or FAIL after other browsers where you have tested this issue:
     Safari:
    Firefox:ok
    IE/Edge:

What steps will reproduce the problem?
1. browsing
2.
3.

What is the expected result?
No black boxes



What happens instead of that?


Please provide any additional information below. Attach a screenshot if
possible.



UserAgentString: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.139 Safari/537.36

posted in forum
https://productforums.google.com/forum/?utm_medium=email&utm_source=footer#!topic/chrome/f5HfBZb_9xY;context-place=forum/chrome

Thus spake every Google Rep for 2+ years we don't see a problem w Black squares by me  4:46 PM  


ADD A REPLY
I have been fighting the problem of the black boxes for so long I cannot think of when the problem began.



It showed as random black squares in a window at random times and constantly being repainted.  sometimes, a single box, other times it was like a crazy pitching machine throwing black boxes on black boxes, making the screen unusable. I made inquiries in other places realizing it was strictly a browser issue.



I remember seeing this behavior in the early 90's when there was a problem with a video card or memory modules.  It was related to the mapping and painting of data chunks in those days. The remedy then was replacement of memory modules or chips on the graphics cards or the mainboard. 



Slipping up to the last couple of months I made inquires and, with no response, determined it might be a malware and the best resolution might be a complete factory restore.  So I waited until time and budget allowed me to purchase a new drive and the break in activities to do a reinstall.



24 hours later, after a few buggy reinstalls I decided that any updates from Microsoft were causing bluescreens and thus I ended up with a naked Win7 home premium OS. And the black boxes were still there.



I ran memory diagnostics repeatedly and then system diagnostics. Another 24 hours of fun.



In the meantime I started using this laptop and noticed it too was having black boxes, It had been restored from HP Factory provided media and is of a similar age, but the video subsystem is different.



Probook 4530s vs Elitebook 8560p

16 gb ram vs 4 gb ram 



I tested every memory module to death and changed the placement in slots to insure it was not hardware.



Were I charging a client for this problem resolution, I would have the billing frozen at 4 hours, $280, plus a new 2tb Seagate drive with no resolution.  And it would have made me look like a failure.  Meaning, in good conscience I could only bill the client 1 hour plus the new drive. $150, and no good results.



Few things are common between the two systems... The Chrome Browser, Win 7 installs from HP from factory media across retail consume and enterprise laptops. No antivirus. Sandy Bridge based mobile CPU's. 



My strong suspicion is a badass coder or coding team tried some oddball coding that is easily broken and or not compatible with Mobile Sandy Bridge cpu's.  Why?  because, as I mentioned at the top of this post, the issue looks like memory block problems.  I expect the mapping algorithms used by the browser are faulty.  Not buggy, faulty.  I have seen posts at least into 2015 describing the issue.



Meanwhile, I will be depending on Mozilla Firefox 60 to provide quality and stability over most of my internet browsing.



Chrome browser is dead to me.



The screenshot with the truck in the upper left corner is on the Elitebook 8560p with 4gb ram, the screenshot of a Chrome Forum page about black squares with a black square is the same Elitebook 8560p with 10gb of ram. The Elitebook is a backup system. The Probook is my primary workhorse due to size and power consumption.














 
Chrome Browser Fail again.PNG
93.9 KB View Download
Chrome Browser Fail.PNG
624 KB View Download
This one has been fixed already; see  issue 836230 

Comment 2 by steelh...@gmail.com, May 12 2018

Why has this issue persisted through development since at least 2015?  The claim is placed that it is fixed, but I expect it is a patch that will flake away again because the overarching algorithm flaw is still in place.

Amateur Hour rush coding is not a way to fix the deeper structural failure.

Read my posted comment for more details suggesting how deep this issue is.

Meanwhile I'm moving to Firefox.


Labels: Needs-Triage-M66

Comment 4 by steelh...@gmail.com, May 14 2018

Thank you krajshree@chromium.org
Cc: susan.boorgula@chromium.org
Labels: Triaged-ET
Mergedinto: 836230
Status: Duplicate (was: Unconfirmed)
steelhoof@ Thanks for the issue

The issue looks similar to  issue 836230 . Hence, merging into issue id 836230.

Thanks...

Sign in to add a comment