| Recurring |
one_organization |
(a) The software failure incident related to Chrome causing crashes on Apple's new MacBook systems is an issue that has happened again within the same organization, Google. The incident involved a resource leak in the Chrome browser related to the drawing of plugins on Mac OS X, specifically impacting Mac hardware containing the Intel HD 4000 graphics chip. Google acknowledged the issue and mentioned that a true fix was in the works to address the problem [12749].
(b) The incident involving Chrome causing crashes on Apple's new MacBook systems is not explicitly mentioned to have occurred at other organizations or with their products and services. The focus of the incident was on the specific interaction between Google's Chrome browser and Apple's new MacBook Air systems with Intel HD 4000 graphics chips. |
| Phase (Design/Operation) |
design, operation |
(a) The software failure incident in Article 12749 was related to the design phase. Google acknowledged that the crashes on Apple's new MacBook Air systems were caused by a resource leak in the Chrome browser related to the drawing of plugins on Mac OS X. This issue was identified as a design flaw in Chrome that triggered kernel panics on Mac hardware containing the Intel HD 4000 graphics chip. Google mentioned that work was ongoing to find and fix the root cause of the leak, indicating a problem introduced during the development phase [12749].
(b) The software failure incident in Article 12749 was also related to the operation phase. While Chrome was causing the crashes, Google suggested that the problem also lay with how some of Apple's drivers were built. The crashes were triggered by actions like closing tabs and managing windows in the Chrome browser, indicating that the operation or misuse of the system contributed to the failure. Google mentioned that they were temporarily disabling some of Chrome's GPU acceleration features on the affected hardware to address the issue, highlighting operational factors impacting the incident [12749]. |
| Boundary (Internal/External) |
within_system |
(a) The software failure incident in the article is primarily within_system. Google acknowledged that the crashes on Apple's new MacBook Air were caused by a resource leak in the Chrome browser related to the drawing of plugins on Mac OS X. They mentioned that the root cause of the leak is being fixed, and they are temporarily disabling some of Chrome's GPU acceleration features on the affected hardware to address the issue [12749]. |
| Nature (Human/Non-human) |
non-human_actions |
(a) The software failure incident in Article 12749 occurred due to non-human actions. Google acknowledged the issue with its Chrome browser causing crashes on Apple's new MacBook Air systems. The root cause was identified as a resource leak in the Chrome browser related to the drawing of plugins on Mac OS X, specifically impacting hardware containing the Intel HD 4000 graphics chip. This resource leak was causing kernel panics on the affected hardware, leading to system crashes. Google mentioned that while Chrome was causing the crashes, the problem also lay with how some of Apple's drivers were built, indicating a non-human factor contributing to the failure [12749]. |
| Dimension (Hardware/Software) |
hardware |
(a) The software failure incident in Article 12749 occurred due to contributing factors that originate in hardware. Google acknowledged that the crashes on Apple's new MacBook Air systems were rooted in actions like closing tabs and managing windows in Google's Chrome browser, but they also mentioned that the problem lies with how some of Apple's drivers are built. Specifically, a resource leak related to the drawing of plugins on Mac OS X was identified as causing kernel panics on Mac hardware containing the Intel HD 4000 graphics chip. Google filed a bug with Apple regarding the kernel panics, indicating that the issue was related to the hardware configuration [12749]. |
| Objective (Malicious/Non-malicious) |
non-malicious |
(a) The software failure incident described in the articles is non-malicious. Google acknowledged the issue with its Chrome browser causing crashes on Apple's new MacBook Air systems, attributing the problem to a resource leak related to the drawing of plugins on Mac OS X. Google mentioned that the crashes were not intentional and were caused by a leak of graphics resources in Chrome, leading to kernel panics on Mac hardware containing the Intel HD 4000 graphics chip. Google also mentioned that the issue lies with how some of Apple's drivers are built, indicating that the failure was not due to malicious intent but rather a technical flaw in the software and its interaction with the hardware [12749]. |
| Intent (Poor/Accidental Decisions) |
poor_decisions |
(a) The software failure incident related to the Chrome browser causing crashes on Apple's new MacBook Air systems was primarily due to poor decisions. Google acknowledged the issue and mentioned that the problem was rooted in a resource leak in the Chrome browser related to the drawing of plugins on Mac OS X. They also mentioned that the crashes were ultimately triggered by Apple's drivers, indicating that the issue was not solely caused by Chrome but also by how some of Apple's drivers were built [12749]. |
| Capability (Incompetence/Accidental) |
accidental |
(a) The software failure incident in Article 12749 was not attributed to development incompetence. Instead, it was acknowledged by Google that the issue with Chrome causing crashes on Apple's new MacBook Air systems was related to a resource leak in the Chrome browser specifically related to the drawing of plugins on Mac OS X. Google mentioned that work was ongoing to find and fix the root cause of the leak, indicating a technical issue rather than incompetence [12749].
(b) The software failure incident in Article 12749 was more aligned with an accidental failure. Google acknowledged the issue with Chrome causing crashes on Apple's new MacBook Air systems and mentioned that the problem also lay with how some of Apple's drivers were built. The incident was described as a resource leak causing kernel panics on Mac hardware containing the Intel HD 4000 graphics chip, and Google was working on fixes to address the issue [12749]. |
| Duration |
temporary |
From the provided article [12749], the software failure incident related to Google Chrome causing crashes on Apple's new MacBook Air systems was temporary in nature. Google acknowledged the issue and mentioned that a workaround was immediately available, with a true fix in the works. They temporarily disabled some of Chrome's GPU acceleration features on the affected hardware via an auto-updated release to address the crashes. Additionally, they recommended installing the latest development or Canary releases which had workarounds implemented to prevent system crashes. This indicates that the software failure incident was not permanent but rather a temporary issue that was actively being addressed. |
| Behaviour |
crash, other |
(a) crash: The software failure incident described in the articles is related to crashes caused by Google's Chrome browser on Apple's new MacBook Air systems. The crashes were severe enough to cause kernel panics, leading to the entire system requiring rebooting [12749].
(b) omission: There is no indication in the articles that the software failure incident was due to the system omitting to perform its intended functions at an instance(s).
(c) timing: The software failure incident is not related to the system performing its intended functions correctly, but too late or too early.
(d) value: The software failure incident is not related to the system performing its intended functions incorrectly.
(e) byzantine: The software failure incident is not related to the system behaving erroneously with inconsistent responses and interactions.
(f) other: The software failure incident is specifically related to a resource leak in the Chrome browser causing kernel panics on Mac hardware with Intel HD 4000 graphics chips. The incident also involves a collaboration between Google and Apple to address the issue, indicating a cooperative effort to resolve the problem [12749]. |