New issue
Advanced search Search tips

Issue 689898 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Feb 2017
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Security



Sign in to add a comment

Crashes on longstring

Reported by mishra.d...@gmail.com, Feb 8 2017 
UserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Firefox/52.0

Steps to reproduce the problem:
Steps to reproduce:
1. Open cc.html 

Wait for a while if the page is kill the crash ID is generated. 

What is the expected behavior?

What went wrong?
Crash ID 4212b6f1-0a28-42ce-bb37-5e6b4d92e8bb
It doesn't generate crash ID in linux but for windows works perfect.

Did this work before? N/A 

Chrome version: 56.0.2924.87 (Official Build) (64-bit)  Channel: stable
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: Shockwave Flash 24.0 r0
cc.html
1.1 KB View Download

Comment 1 by palmer@chromium.org, Feb 8 2017

Status: WontFix (was: Unconfirmed)
Thanks for reporting this issue! However, we do not consider renderer crashes due to out-of-memory conditions to be security issues. For more information, please see the Chrome Security FAQ (https://sites.google.com/a/chromium.org/dev/Home/chromium-security/security-faq?pli=1#TOC-Are-denial-of-service-issues-considered-security-bugs-) and the Vulnerability Severity Guidelines (https://www.chromium.org/developers/severity-guidelines).
Project Member

Comment 2 by sheriffbot@chromium.org, May 18 2017

Labels: -Restrict-View-SecurityTeam allpublic
This bug has been closed for more than 14 weeks. Removing security view restrictions.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
►

Sign in to add a comment