Trying to get status on 703029
Reported by
dku...@salesforce.com,
Aug 7 2017
|
|||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.78 Safari/537.36 Steps to reproduce the problem: I'm really just trying to get an update on an issue I submitted that was closed as a duplicate of 703029, which is a private bug. I have no insight into this case so I don't know what I should tell my client, is this issue related to a Chrome defect that will be addressed? Is it specific to 32 bit Chrome? What is the expected behavior? What went wrong? No updates are being provided on my original ticket (https://bugs.chromium.org/p/chromium/issues/detail?id=729692) now that this has been marked as a duplicate. Crashed report ID: 703029 How much crashed? Just one tab Is it a problem with a plugin? N/A Did this work before? N/A Chrome version: 60.0.3112.78 Channel: n/a OS Version: OS X 10.12.6 Flash Version: Shockwave Flash 26.0 r0
,
Aug 8 2017
dkurtz@ - The issue https://bugs.chromium.org/p/chromium/issues/detail?id=729692 that has be marked as a duplicate of issue id: 703029, seems to be an Out Of Memory issue as per comment #7. The issue id: 703029 has been marked WontFix by a dev stating that "When the machine is out of memory, the out of memory handling code gets called. That does not mean there is a bug in the OOM handling code." please let us know if anything else is needed from our side. Thanks...!!
,
Aug 10 2017
dkurtz@ - when a bug is marked duplicate there's a note about the bug it was duplicated into. You can always check the status of that other bug. You should not file new bugs to try to learn the status of any other bug.
,
Aug 11 2017
@shrike as stated the other bug is private and I cannot read it. |
|||
►
Sign in to add a comment |
|||
Comment 1 by nyerramilli@chromium.org
, Aug 8 2017