New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 680712 link

Starred by 1 user

Issue metadata

Status: Duplicate
Owner: ----
Closed: Jan 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

Seeing frequent crashes on stable

Project Member Reported by sgmc@google.com, Jan 12 2017

Issue description

Google Chrome	55.0.2883.103 (Official Build) (64-bit)
Revision	0
Platform	8872.73.0 (Official Build) stable-channel samus

Please specify Cr-* of the system to which this bug/feature applies (add
the label below).

Steps To Reproduce:
(1) crash/3d323e3080000000
(2)
(3)

Expected Result:

Actual Result:

How frequently does this problem reproduce? (Always, sometimes, hard to
reproduce?)

What is the impact to the user, and is there a workaround? If so, what is
it?

Please provide any additional information below. Attach a screen shot or
log if possible.

For graphics-related bugs, please copy/paste the contents of the about:gpu
page at the end of this report.


 

Comment 1 by sgmc@google.com, Jan 26 2017

This appears to be correlated with switching profiles.
Components: Internals>GPU
Looks like an OOM in GPU process.
Cc: dongseon...@intel.com reve...@chromium.org
This is not a general OOM situation. This is failing to specifically allocate DMA buffers:
From client_native_pixmap_dmabuf.cc:
-----
 data_ = mmap(nullptr, map_size, (PROT_READ | PROT_WRITE), MAP_SHARED,
               dmabuf_fd_.get(), 0);
  if (data_ == MAP_FAILED) {
    PLOG(ERROR) << "Failed mmap().";
    base::TerminateBecauseOutOfMemory(map_size);
  }
----
this is what it's failing.

I think this is possibly related with Issue 629521 that was fixed very recently.

Mergedinto: 629521
Status: Duplicate (was: Unconfirmed)

Sign in to add a comment