Issue metadata
Sign in to add a comment
|
Error in dxva_picture_buffer_win.cc on line 828
Reported by
hakerh403@gmail.com,
Oct 8
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.100 Safari/537.36 Steps to reproduce the problem: 1. Open Chrome 2. Use for a while 3. Go to chrome://gpu 4. Observe a lot of errors What is the expected behavior? No errors. What went wrong? We see a lot of errors in the chrome://gpu page. The most common errors that appear are the following: - GpuProcessHostUIShim: The GPU process crashed! - Error in dxva_picture_buffer_win.cc on line 828 - The GPU process hung. Terminating after 15000 ms - MessageAttachmentSet destroyed with unconsumed attachments - GL ERROR: GL_INVALID_OPERATION: glCreateAndConsumeTextureCHROMIUM: invalid mailbox name - WARNING X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them - RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering We didn't see any crashes or other manifestations of these errors, but we think it may be useful to report them. The whole gpu.htm file is also attached. The Chrome version used is 67.0.3396.87, we didn't test with other versions so far. Did this work before? N/A Chrome version: 69.0.3497.100 Channel: stable OS Version: 6.3 Flash Version: /
,
Oct 9
Unable to reproduce the issue on chrome reported version# 69.0.3497.100 using Windows-10 with steps mentioned below: 1) Launched chrome reported version and used it for a while 2) Navigated to Chrome://gpu and didn't observed any errors in it. @Reporter: Please find the attached for your reference and could you please try to test this issue by creating new person with no apps and extensions in it and let us know if the issue still persists. Note: Tentatively adding Internals>GPU component to it. Thanks!
,
Oct 9
Reported version is 67.0.3396.87 and not 69.0.3497.100 (see comment C0 - last paragraph, and 69.0.3497.100 is generated automatically for some reason - probably the issue wizard extracted it from our user agent string). It is not surprising that the issue is not easily reproducible. We reported it because we experience it and since it originates from Chrome's file (dxva_picture_buffer_win.cc), we think it may be useful for developers to investigate what may be causing the error to appear. The issue is probably related to graphical drivers or some system-specific parameters, so it may not be reproducible on every machine. Our profile is already clean (clean Chrome installation from x64 offline setup) - no extensions, apps or plugins are installed.
,
Oct 9
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Oct 12
This report doesn't give us much to work with, so we may close it without more information that is actionable. Would you be able to paste the crash ID associated with this hang when it happens? You can get the crash ID after noticing a crash by opening 'chrome://crashes'.
,
Oct 15
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Oct 19
That is just a local crash id (which has not been uploaded), and so we can't take a look at this. Can you turn on "Automatically send usage statistics and crash reports to Google" in chrome://settings, and then send the id of the crash once it has been uploaded? It will say something like "Uploaded Crash Report ID XXXXXXXXXX".
,
Oct 19
The PC on which we observed the error messages is offline, so enabling crash reporting is useless. If we can help in any other way, please let us know.
,
Oct 19
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Oct 19
Sorry, without a crash report or a solid way to reproduce this problem, there's not that much we can do.
,
Nov 12
The NextAction date has arrived: 2018-11-12 |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by susan.boorgula@chromium.org
, Oct 8