MacBook Pro retina freez while using chrome

Chrome is not an Apple product. Have you tried using Safari instead?

i don't think that's the point. the operating system isn't supposed to freeze when using any program. +1 for this, it's happening to me too on a 15 inch retina mbp with chrome 25.0.1323.1 and 10.8.2. the mouse freezes, and none of the buttons but the power button respond.

winterslove wrote:

i don't think that's the point. the operating system isn't supposed to freeze when using any program.

That is a myth. Any program run by a local user can bring down your system. The trick is to make sure that you only run legitimate, reliable software software. This is not a Mountain Lion issue. I have run scripts that brought down big UNIX servers without any adminstrator rights.

Chrome is based on Apple's WebKit which, although open source, it run and tested by Apple. Unfortunately, Google adds additional open-source components that are not up to Apple's quality levels. It is like running a little bit of Linux on your Mac. Who wrote that code? How much experience, if any, do they have? There is no way to tell other than observing it lock up your machine.

i'm sorry but you're simply wrong. it is unacceptable for an unprivileged, userspace application to cause a kernel halt. while it might be possible to eventually exhaust resources as an unprivileged userspace application, leading to an eventual denial of service, that is not what is going on here. this is a bug, an immediate crash triggered somewhere in apple's graphics rendering code that is called by chrome. please refrain from commenting on myths unless you actually know what you are talking about.

Since you are such an expert on the OS X kernel, why don't you just go in there and fix it for us?

Google has known about this problem since June. Yet Google continues to push Chrome with "A faster way to browse the web" slogan on its search portal. Normally, if your software is causing things like kernel panics on users' machines, you fix the code rather than blame someone else. If Google thinks Apple is at fault, Google can file a bug report and publicly blame Apple, which is what Google has done. It would also be nice if Google would fix their code so it didn't cause kernel panics. Neither Safari nor Firefox has problems like this. Before Apple releases a change to the kernel, Apple has to regression test it against all the other software that didn't cause kernel panics before. That's a lot of work. Since Google doesn't have such responsibilities, it is much easier for Google to change its code so that its software doesn't crash people's machines.

Also experiencing this issue. Seems to happen in long intervals.

I have exactly the same problem. It seems it started after the most recent system update of OSX - which happened 13 Nov (rather than after Chrome update) - so i'd certainly attribute it to Apple rather than Google.

It seems to happening when i am scrolling some form field inside the chrome fast using the touch pad. It happened to me first time some 3 days ago, and already three times today and tomorrow - always in the same circumstances - when scrolling fast the content of some form field when in Chrome.

There are no entries in the system.log to indicate what's happened - the logs that appear just before the crash are also appearing elsewhere in logs, so they are probably not related:

Nov 17 13:27:57 Weathertop kernel[0]: Sandbox: sandboxd(10799) deny mach-lookup com.apple.coresymbolicationd

Nov 17 13:27:57 Weathertop sandboxd[10799] ([10798]): mdworker(10798) deny mach-lookup com.apple.ls.boxd

Nov 17 13:30:33 localhost bootlog[0]: BOOT_TIME 1353155433 0

Nov 17 13:57:37 Weathertop sandboxd[676] ([675]): mdworker(675) deny mach-lookup com.apple.ls.boxd

Nov 17 13:57:37 Weathertop sandboxd[676] ([674]): mdworker(674) deny mach-lookup com.apple.ls.boxd

Nov 17 13:57:37 Weathertop kernel[0]: Sandbox: sandboxd(676) deny mach-lookup com.apple.coresymbolicationd

Nov 17 13:57:54 Weathertop kernel[0]: CODE SIGNING: cs_invalid_page(0x106631000): p=679[python] clearing CS_VALID

Nov 17 13:58:00 Weathertop kernel[0]: CODE SIGNING: cs_invalid_page(0x10fd49000): p=684[python] clearing CS_VALID

Nov 17 13:58:04 Weathertop kernel[0]: CODE SIGNING: cs_invalid_page(0x10b01e000): p=685[python] clearing CS_VALID

Nov 17 13:58:25 Weathertop kernel[0]: CODE SIGNING: cs_invalid_page(0x104871000): p=686[python] clearing CS_VALID

Nov 17 13:58:38 Weathertop kernel[0]: CODE SIGNING: cs_invalid_page(0x103157000): p=687[python] clearing CS_VALID

Nov 17 13:59:46 localhost bootlog[0]: BOOT_TIME 1353157186 0

higrys wrote:

I have exactly the same problem. It seems it started after the most recent system update of OSX - which happened 13 Nov (rather than after Chrome update) - so i'd certainly attribute it to Apple rather than Google.

Google's Chrome problems pre-date that update. As samanth's link shows, Chrome has been unstable for months. High quality software should continue to run well even if the operating system is updated. One of the identifiying traits of low-quality software is that it breaks or degrades on X.X.n operating system updates. Chrome began causing kernel panics immediately upon the release of the Retina machines. Google made some changes, but apparently not enough.

It is certainly true that the OS X kernel should be more resilient to misbehaving software. It is also true that Google Chrome is, as far as I know, unique in its ability to cause kernel panics without kernel extensions. If this issue affected more than just a single program, I'm sure Apple would put a higher priority on fixing it. Currently, if Apple makes a change to fix a single 3rd party program, it risks breaking many other programs that weren't broken before. That is a lot of risk and requires a lot of testing. The workaround is super-easy - just use Safari or Firefox.

Well, I so much utterly disagree with you etresoft.. I am a 3rd party developer and what I expect from a platform developers is to give me the platform (OS) that I can rely on. This problem was not happening before - i am a MacBook Pro Retina (and Chrome with that) user for months and I had no problems whatsoever, I don't even know what your statements are based on - I do NOT know if it happens with Safari or Firefox, I know it happens with certain operations on web page in Chrome - that's it. I don't use Safari or Firefox (I did use both for some longer and shorter periods of time as well as IE and Opera, but none of them lived to my expectations). Unless your post is paid by Apple (honestly - it looks like), I have no idea where your conclusions are drawn from- that they are free of that problem? Have you checked it? Chrome worked super-stable for me with many upgrades and the problem started after most recent update.

As a long time programmer I can only confirm what winterslove wrote: the OS/platform is there to deliver stable behaviour for 3rd party developers and isolate 3rd party apps from each other and the OS itself. It's totally unacceptable to allow a bug in one application to freeze the whole OS. This is an absolute base of what operating systems is all about and what I was taught at University and where my all IT development experience is based on (I programmed for Windows, Linux, Solaris, OSX and many other smaller telecom OS's) - and other than resource exhaustion all other forms of crashing/hanging kernel by user space application are considered CRITICAL security problem that should be patched by kernel developers in days if not hours (some of such problems have been used to elevate privilleges and break into the OS itself).

I also recall time when my user space program crashed an OS of telecom operating system and within days they provided full replacement of the hardware + OS running my programs (worth hundreds of thousands of dollars), because this was really unacceptable behaviour. No matter what - this is a kernel problem to allow this to happen, not any 3rd-party developer app. Please: Apple developers - make it so that Chrome crashes if it is buggy (they would fix it in hours/days likely) but DO NOT let it hang the whole OS. This is unaccceptable.

Neither Safari nor Firefox are super-easy replacement - Chrome gives so much more (starting from syncing with my Chrome on Android phone, and ending with being faster, have better extensions than either of them) that it looks like a joke when you write it super-easy. Safari has mabye few percent share comparing to Chrome, and if Apple wants to boost Safari usage by introducing problems that only affect Chrome - well, that might be very well the last Appe computer I own - because I am not going to switch to so much inferior browser.

For everyones information: I also opened a Google Chrome forum discussion for that, which I hope can help Google Chrome devs to point Apple's developers in the right direction and help them to solve the problem (which I strongly believe is Apple's root cause to fix): http://productforums.google.com/forum/#!category-topic/chrome/mac/cztpS-TqGQ4 .

Rather than blaming the other side, they should talk to each other and find/fix the problem together. Which I am pretty sure Google guys want to do....

higrys wrote:

I don't use Safari or Firefox (I did use both for some longer and shorter periods of time as well as IE and Opera, but none of them lived to my expectations).

Running IE on a Mac is an impressive trick.

Unless your post is paid by Apple (honestly - it looks like)

The pot calling the kettle black, eh?

crashing/hanging kernel by user space application are considered CRITICAL security problem that should be patched by kernel developers in days if not hours

Utter nonsense. You really expect any vendor is going to make a change to the kernel, in a matter of hours, to fix one buggy program and put all other software at risk?

I also recall time when my user space program crashed an OS of telecom operating system and within days they provided full replacement of the hardware + OS running my programs (worth hundreds of thousands of dollars), because this was really unacceptable behaviour.

I recall many occasions developing satellite command and control systems when we found bugs that would cause the software, not to mention the satellite, to crash and burn. What did we do? Issue a bug fix in hours? No. That took six months of development and testing. We just didn't do whatever it was that would crash the software and/or satellite. In all cases, if there was some critical vendor bug, we would never just sit on our hands and wait for a fix, we would work around it.

Modern computers with GPU acceleration aren't like your old telecom hardware. GPU acceleration is a direct channel to the hardware. That's the point of it. It requires that the developers know how to do that sort of thing. If they don't, they should avoid that.

Neither Safari nor Firefox are super-easy replacement - Chrome gives so much more (starting from syncing with my Chrome on Android phone, and ending with being faster, have better extensions than either of them) that it looks like a joke when you write it super-easy. Safari has mabye few percent share comparing to Chrome, and if Apple wants to boost Safari usage by introducing problems that only affect Chrome - well, that might be very well the last Appe computer I own - because I am not going to switch to so much inferior browser.

And you accuse me of being paid by Apple? You are aware that Chrome is just a fork of Safari with some added bugs, aren't you?

Rather than blaming the other side, they should talk to each other and find/fix the problem together. Which I am pretty sure Google guys want to do....

This is a user-to-user tech support forum for Apple products. If you are having a problem with 3rd party software, report it to them. A forum post in a Chrome support forum is better than one here, but an actual bug report for Chrome would be better. If Chrome's developers decide that the bug is in OS X, then they will send a bug report to Apple. They should also release a patch to work around the problem.

etresoft wrote:

higrys wrote:

I don't use Safari or Firefox (I did use both for some longer and shorter periods of time as well as IE and Opera, but none of them lived to my expectations).

Running IE on a Mac is an impressive trick.

Who said it was on Mac? I didn't. Quite the opposite - as I mentioned in my post I change my OS's often. It happens that currently it is OSX, but it might well be that tomorrow it will be something completely different (it happened in the past too). If you read what I wrote: Windows, Linux, Solaris, OSX - these are all OS's I used/still use. Sometimes Apple fanboys are blindfolded and forget that there are other OS's out there.

Unless your post is paid by Apple (honestly - it looks like)

The pot calling the kettle black, eh?

I am just the user of the software. That's my interest here - to get help. I am not sure what's your interest promoting switching to other browsers from chrome is, when it's clearly not a solution to the problem.

Utter nonsense. You really expect any vendor is going to make a change to the kernel, in a matter of hours, to fix one buggy program and put all other software at risk?

Please, try to read what I wrote: days (if not hours). I do expect. Other software vendors do that (usually days rather than hours of course - hours are there for really critical security problems with exploits in the wild). Some examples: Ubuntu, RedHat,
Microsoft, even Apple did itin response to this vulnerability (side note: that was vulnerability that was manifesting itself in Safari - and many people advised to switch to Firefox then). I am not sure if this is a security vulnerability, but any crash which seems to reach and block kernel is rather a sign of elevating privilleges, and clever hackers could find a way to use that backdoor to get control over the OS itself - that's hacker's heaven. Such issues should be immediately investigated by OS dev team to see if they can be exploited.

I recall many occasions developing satellite command and control systems when we found bugs that would cause the software, not to mention the satellite, to crash and burn. What did we do?

That's not a very good example. It was not a "general purpose" OS that someone delivered to 100s of millions of people to let them run any programs. I bet you have not allowed to run 3rd-party software on your satllite, it was fully controlled by your team, so you could do whatever you deemed appropriate at given time, and (because of risk involved) your procedures/QA process/development time/testing methodologies are very much different than that of general purpose OS. General purpose OS is very different beast. It has to handle many situations and cases and protect properly against any 3rd party software, because it's the bread-and-butter of the OS. The OS should be largely invisibe to the user - there is no other purpose in writing such OS: it should let other, 3rd-party programs to run. Of course, I did many workaround myself around OS limitations and bugs in the past, and I have no doubts Chrome team will try to find it as well (as they had to many times already in the past to workaround OSX and other OS's limitations). But this should not stop OS vendor from investigating and fixing the problem permanently - because other 3rd party software might soon (if not already) hit the same problems. Also - since the bug is triggered by the recent OSX update (as it is clear from Chris's comment) - it WAS introduced by Apple. Chrome scrolling WAS working ok before and STOPPED working after the OS update (not the chrome update). Guess who should be ultimately responsible for the problem?

Modern computers with GPU acceleration aren't like your old telecom hardware. GPU acceleration is a direct channel to the hardware. That's the point of it. It requires that the developers know how to do that sort of thing. If they don't, they should avoid that.

True. I am CTO in a company which now deals largely with GPU acceleration and we are often running our code directly on the hardware (mobile apps) so I know all about it. Standards like OpenGL, CUDA, etc. are written in the way to let the software access hardware in secure way. The job of OS is to implement the standards properly to not allow the application to abuse it by programming mistake. Sometimes even not allow to do certain operations if they find impossible to protect. If they fail in doing so - they should not open up for 3rd-party developers with these (or be prepared for quick fixes). There are 100s of thousands of developers out there developing 3rd-part apps for OSX. By just saying "don't do that if you are not experts" is not a good way to protect your own OS against bad impression. If Apple opens up buggy OpenGL/CUDA which allow other apps to crash the whole OS, soon they migh be flooded by a number of apps doing it and the reputation of OS will be at stake. So better they patch the problem rather than telling others that they should not use interfaces they open-up themselves.

And you accuse me of being paid by Apple? You are aware that Chrome is just a fork of Safari with some added bugs, aren't you?

That is not true statement, obviously. Chrome is (similiarly as Safari) built on top of WebKit rendering engine. WebKit is open-source and originates from KDE starting in 1998 (which was not Apple bound but cross-platform: GNU/Linux, FreeBSD, Solaris, Microsoft Windows, and OS X) and those guys should be credited for clean codebase, good modularity, separation from platform dependencies, conformance to standards. Apple obviously forked from that code - and since 2001 contributed most to development of WebKit. But then Apple open-sourced the engine in 2005. Open Source/BSD Licence = anyone can take it and contribute or build on top of it, that's the intention of open-sourcing under the BSD licence. Many other companies since contributed a lot as well. including Google Chrome team, Adobe and many others. So eventually - both Safari and Chrome are built on top of the rendering engine that was created by KDE originally and then evolved by Apple and many others. So Chrome is not Safari fork at all. While there is a common code which is shared (and many parties contribute to it), there a many things that Chrome does so much better (and is not forking of Safari by any means): syncing between browser on many OS's, better tab support, powerful extension mechanism with 1000s of good extensions out there, hardware GPU support (yes!), v8 javascript engine which gets faster with every relese, and a number of others - so nearly everything that is geared towards better usability in general (WebKit just renders HTML pages and that's about it).

This is a user-to-user tech support forum for Apple products. If you are having a problem with 3rd party software, report it to them. A forum post in a Chrome support forum is better than one here, but an actual bug report for Chrome would be better. If Chrome's developers decide that the bug is in OS X, then they will send a bug report to Apple. They should also release a patch to work around the problem.

Again, as in case of Webkit, Safari and Chrome - you are mixing products. The link you specified is for CHROMIUM not Chrome. I don't use Chromium. These are two different products (albeit sharing almost all code). Chromium is an open-source project which has a lot of the same functionality as Chrome, and is not officially supported by Google employees (though mostly them contribute). Chrome, on the other hand is supported by Google employees and the official way of reporting problem is through the forums under "Report an Issue and Get Troubleshooting Help" Category. And it's a good way to keep such issues as forum entries, because other people (like Chris) can see that they are not alone and add their own comments - which can help others or Vendor to find out what the problem is. That's how Google employees do it - they are reading the forums and often responding and helping to fix the problem. It happened to me several times that I found workarounds there before official fix was out (which I hope will happen soon).

But since - what I gather from you - no Apple employees visit the forum here, I would love to be able to create such an issue on some official Apple issue tracking/forum where Apple employees are looking at and helping - so that the guys from Google and Apple could work together on it and get Apple issue a permanent fix. That's why I cross referenced this discussion and the Google discussion hoping that it might help. Do you know of any way I can officially open an issue to Apple other than through feedback form ? The feedback form is largely a black-box which ***** everything and never gives any info about what's happening with the issue - no other people can contribute and Apple explicitely states that they "never respond" to such feedback.... Is there any other way I can report that Apple OS's bug to them?

higrys wrote:

Sometimes Apple fanboys are blindfolded and forget that there are other OS's out there.

So do you normally go onto Linux or Chrome and insult people who use those products too? I believe you've got it backwards. It is Windows and Linux users who think they are the centre of the world. This is an Apple forum and other operating systems mean nothing here.

I am just the user of the software. That's my interest here - to get help. I am not sure what's your interest promoting switching to other browsers from chrome is, when it's clearly not a solution to the problem.

People come here complaing that their Macs are crashing because of Chrome. I suggest they switch to Safari. That is a 100% guaranteed solution. They could switch to Firefox or Opera too. I can't change the code in either Chrome or OS X, but I can solve this problem. If Chrome is causing kernel panics - stop using it.

Please, try to read what I wrote: days (if not hours). I do expect. Other software vendors do that (usually days rather than hours of course - hours are there for really critical security problems with exploits in the wild).

Yes. Companies fix critical security problems with exploits in the wild in hours. That is, all those times that it doesn't take months.

It was not a "general purpose" OS that someone delivered to 100s of millions of people to let them run any programs. I bet you have not allowed to run 3rd-party software on your satllite, it was fully controlled by your team, so you could do whatever you deemed appropriate at given time, and (because of risk involved) your procedures/QA process/development time/testing methodologies are very much different than that of general purpose OS.

I make no pretentions about knowing anything about your claimed "telecom" field, so why do you claim to be an expert in satellite systems? For the record, we deployed these systems on HP-UX, Solaris, VMS, Windows, and VxWorks. The schedule was chisled in stone and entirely out of our control.

I have no doubts Chrome team will try to find it as well (as they had to many times already in the past to workaround OSX and other OS's limitations). But this should not stop OS vendor from investigating and fixing the problem permanently

You should have no doubt because that is exactly what happened the last time Chrome was causing kernel panics. Apple in fact did fix a kernel bug that Chrome was exploiting to cause the panic. Then Google removed their workarounds. What Google apparently failed to do was improve the quality of the code to avoid future kernel panics. No other applications, including graphics intensive games, cause kernel panics like this. There is something that Google is doing wrong that no one else is doing wrong. If Google keeps reporting kernel bugs to Apple, I'm sure Apple will keep fixing them, just like they have done in the past.

At some point, Google needs to stop punishing its users and write better code that doesn't cause kernel panics. Perhaps it is Google that is purposelly finding and exploiting kernel bugs to market Linux and Android? It wouldn't be the first time Google has gone out of its way to hack Apple software for its own profit.

I am CTO in a company which now deals largely with GPU acceleration

Why do I doubt that?

If Apple opens up buggy OpenGL/CUDA which allow other apps to crash the whole OS, soon they migh be flooded by a number of apps doing it and the reputation of OS will be at stake.

That's curious. Any 3rd party software can use the same graphics acceleration that Chrome uses. Yet we aren't flooded by apps causing kernel panics. Only Chrome does that.

The link you specified is for CHROMIUM not Chrome. I don't use Chromium. These are two different products

If you are looking for experts on Chrome, you should consult a Chrome forum. It is not my responsibility to help Chrome users report bugs in Chrome.

But since - what I gather from you - no Apple employees visit the forum here

Correct. Just fanbois like me.

Is there any other way I can report that Apple OS's bug to them?

Use The Apple Bug Reporter

If Chrome is causing kernel panics - stop using it.

I might as well stop using OS which after update caused Chrome to freeze it. It's also valid "solution". This happened after OS update and Chrome might not have the same problem on Windows/Linux. But I think I would rather wait for some workarounds, other browser are not good enough and it would cost me more to switch browsers than to switch OS (really - I've done that many times, both browsers and OS's).

The schedule was chisled in stone and entirely out of our control.

I am not talkin about the schedule, but about the software (that you had in full control). You did not have other 3rd party software written for your satelite, so you were in control of the whole ecosystem. Don't tell me please that as a 3rd party software company you could burn a satellite by just uploading software to it.

That's what I was talking about. The other "telecom" platform I was talking about was Telsis application server: http://www.telsis.com/products/application-server.asp using hich many 3rd-party companies wrote their software (including ours) - and it started to misbehave and crash randomly - we buit an application that was apparenly triggering some limitations of the older switch (but it was not supposed to). Guess what - in a few days we go the whole new (bigger, more powerful) ardware delivered to us and replaced.

What Google apparently failed to do was improve the quality of the code to avoid future kernel panics. No other applications, including graphics intensive games, cause kernel panics like this.

Future is the key here. How gogle could prevent and workaround it, before the bug was introduced in the new OS update? I do not know what you base your statements on, but this is clearly a new bug introduced in the new OS update. I never had any problems with Chrome on OSX before like that. And I am pretty sure you will get some repoerts soon from others. Simply Chrome is so widely used that you get first reports about Chrome....

I'm sure Apple will keep fixing them, just like they have done in the past.

This is all I want to hear... Please Apple devs: let us know when it's fixed.

I am CTO in a company which now deals largely with GPU acceleration

Why do I doubt that?

I have no idea why. but yet, that's what I do currently. And pretty good at that, I believe. And for the record - i did work as Tech Lead Manager in Google and left the company 4 years ago to build my own businesses. And there are many things does good and many they do not-that-good... We use many Google and Apple products that help us to build our business. Chrome is more on the better side of it, I am pretty sure of it.

BTW. What's your relation to Apple? You mentioned "we" once or twice when mentioning Apple.

Use The Apple Bug Reporter

You must be kidding me.. I was talking about real open issue list, that I can see and track and have others contribute to the issue, and can pop-up in search engines when I look for them (this is what happens now with both issues I opened : here and the one in google chrome forum)... The link is for Developers, not users (and I am user in this case). And it's so old and antiquated and not used by Apple, that noone, really noone is using it. First of all it writes that it needs Safari 1.0 (?). Secondly, guess what happens if i search for "crash" or "hang" or any other search criteria (say 'OSX')?: No problems were found that match the search criteria.

What's the use of such system that I cannot see issues raised by others and contribute to them?

higrys wrote:

I might as well stop using OS which after update caused Chrome to freeze it.

If using Chrome is more important to you than OS X, then perhaps that is the right solution. People often complain that some expensive, 3rd party hardware or software no longer works with Lion or Mountain Lion. They need to decide if they are customers of Apple or that 3rd party. If that 3rd party software is most important, then you ask them before upgrading your OS.

other browser are not good enough and it would cost me more to switch browsers than to switch OS (really - I've done that many times, both browsers and OS's).

The idea that one browser or another is not good enough is just ridiculous. Except for Opera, which always lags behind, they are all equivalent. The last time I heard talk like that was when people were trashing Parallels in favor of VMWare. Aside form its tendancy to cause kernel panics, Chrome isn't any different from Safari or Firefox. It's just a web browser for crying out loud.

I am not talkin about the schedule, but about the software (that you had in full control). You did not have other 3rd party software written for your satelite, so you were in control of the whole ecosystem. Don't tell me please that as a 3rd party software company you could burn a satellite by just uploading software to it.

Fine. I won't tell you that if it makes you uncomfortable. In some ways, a satellite command and control system is like an operating system. It includes many different modules from different groups and companies. Our users wrote extensive scripts to perform tasks like calibration, imaging, and maneuvers, including de-orbiting the spacecraft.

we buit an application that was apparenly triggering some limitations of the older switch (but it was not supposed to). Guess what - in a few days we go the whole new (bigger, more powerful) ardware delivered to us and replaced.

So that's your solution? Apple sound send new machines with bigger video cards to all Chrome users so they will be less likely to panic?

Future is the key here. How gogle could prevent and workaround it, before the bug was introduced in the new OS update? I do not know what you base your statements on

I base my statements on experience. It is quite common for people to code something up on Windows or Linux, port it to the Mac, see it crash, and then blame Apple. After all, it worked perfectly before.

Just because it worked doesn't mean it was right. One of the primary ways to tell if some programmer was wrong, but lucky, is if the software starts arbitrarily crashing if the operating system gets updated or the software gets ported to another platform. That is probably the root of Google's problems. Linux is simply more forgiving of bad code.

This is all I want to hear... Please Apple devs: let us know when it's fixed.

There are no Apple devs here. If there is an update that says something like "fixes some kernel panics related to GPU resource exhaustion"' then it might help. If it doesn't say that, then Chrome could crash even more.

i did work as Tech Lead Manager in Google

I'm shocked.

BTW. What's your relation to Apple? You mentioned "we" once or twice when mentioning Apple.

None whatsoever. I used "we" several times to refer to my old satellite projects. I used "we" once to refer to Apple users who aren't flooded by apps causing kernel panics.

You must be kidding me.. I was talking about real open issue list, that I can see and track and have others contribute to the issue, and can pop-up in search engines when I look for them (this is what happens now with both issues I opened : here and the one in google chrome forum)...

Apple is not github project. You are free to report bugs but only you and Apple can contribute to them.

The link is for Developers, not users (and I am user in this case).

You do need a free Developer account to log in. After that it is just a standard bug reporting database. I would think that a CTO would not be so easily deterred.

And it's so old and antiquated and not used by Apple, that noone, really noone is using it.

You accuse me of working for Apple but you have some kind of insider knowledge about what Apple really uses for bug reporting? And what might that be? We (those of us who don't work at Apple) would love to hear about it.

First of all it writes that it needs Safari 1.0 (?). Secondly, guess what happens if i search for "crash" or "hang" or any other search criteria (say 'OSX')?: No problems were found that match the search criteria.

What's the use of such system that I cannot see issues raised by others and contribute to them?

That just means you haven't entered any bug reports yet. The reason Apple requires a developer account is to try to keep out people like yourself who are expecting some kind of free-for-all forum. It is a bug reporting tool. If you have evidence of a bug and steps to reproduce, then file a report. Otherwise, don't waste their time.