Posted on 03/21/2015 7:36:39 PM PDT by Utilizer
No browsers are safe as proved yesterday at Pwn2Own, but crashing one of them with just one line of special code is slightly different. A developer has discovered a hack in Google Chrome which can crash the Chrome tab on a Mac PC.
The code is a 13 character special string which appears to be written in Assyrian script
*break*
Matt C has reported the bug to Google, who have marked the report as duplicate. This means that Google are aware of the problem and are reportedly working on it.
(Excerpt) Read more at techworm.net ...
*ahem* “paltry pills” should read “paltry pill effects”, LOL.
Typing too fast to proofread. :)
Intel introduced the Itanium 64 before AMD which is strange they would have to cross license from the weaker of the two companies. I say that as a supporter of AMD since before the Athlon processor days of the late 90’s.
Yeah, but IA64 didn’t really take off—it has a niche in the HP server market.
Around the turn of the century, Chipzilla and AMD were working on 64-bit word machines—Intel was committed to IA64—a radically different instruction set—Windows Vista for IA64 STILL required a [slow] emulator to run IA32 code, which was held over from the Windows 2000 IA64 betas—Windows 2000 Server LE.
AMD, however, decided to simply extend the IA32 ISA—the result being an architecture that seamlessly ran 32-bit and 64-bit apps at full speed—without abandoning the original x86 architecture; much like the 80286, where you have to switch between real and protected mode manually, the same procedure exists in AMD64 for switching between long mode and protected mode—this is why AMD64 versions of Windows cannot run 16-bit apps.
This, of course, was a lot simpler than IA64, so the first chips were released in 2003. Intel was now behind the curve; hence, the lawsuits, and the settlements, which involved cross-licencing agreements—AMD got a licence to the original IA32 architecture, and Intel got a licence to continue manufacturing AMD64/EM64T/Intel64 chips.
I am certainly not going to bother the Apple/Mac ping list over a GOOGLE CHROME flaw that causes it to crash when an string of ASCII codes is input into a tab which instantly causes just that tab to close. It is picayune idiocy. AND add to that the poster of this thread immediately started with the anti-Apple and anti-Swordmaker insults and expects me to do anything to get attention to ITS thread? Not on ITS insulting TROLLISH life. That's just the way it is. ;^)
The anti-Apple hecklers have to distort the facts of this problem. . . which is not an Apple problem but a Google Chrome coding problem . . . and lie claiming it "crashes the machine" and is a hack into the computer. Nothing could be further from the truth of this issue. The browser does not even crash.
I generally open 7-10 tabs at a time as I go through the posts. Haven't had problems with Chrome getting the hiccups with it though.
Running Win7 Prof with 8GB RAM and also usually have about 50 tunes queued up in WinAmp (using older version 5.581 after years of vers 2.81 because of simplicity and utility).
I remember back in the 90’s a site named Crash My Browser, click the link and your browser closed. OK. The mean one was the unmarked one elsewhere that, when clicked on unsuspectingly, shut your machine down... Mean, you say? Back then, when the pimples got home from school, my ISP would overload with users and it was damn hard to get a modem. TG for autodial, 50 tries sometimes to get on!
I also remember several sites that when you viewed them provided a link that when clicked showed that they could see exactly what was on your hard drive.
Made more than one person nervous about that possibility.
Got any URL's, or are they long gone? I'd like to plug them into the Internet Archive and see what's there, I'm just that freakin' nosy! ;)
*laugh* Hate to break it to you, but it was a scare-tactic for people who did not know all that much about computers.
You can do the same thing that the link did by just opening up a terminal window and pinging 127.0.0.1. Or, if you are comfortable with the command line, list the directories under 127.0.0.1. if you are brave enough. :)
Ah, I dig. Thought they mighta had something there. Figures. Learned DOS 20 yrs back and farted around with BASIC on a Timex-Sinclair 1000 in the early 80’s. Fun, fun!
Disclaimer: Opinions posted on Free Republic are those of the individual posters and do not necessarily represent the opinion of Free Republic or its management. All materials posted herein are protected by copyright law and the exemption for fair use of copyrighted works.