Last Comment Bug 635464 - Crash in TextStageManager::MapTextureTransferSurface while switching from ATI/AMD's to Intel's GPU with Intel driver versions 8.15.10.2141 and below
: Crash in TextStageManager::MapTextureTransferSurface while switching from ATI...
Status: NEW
[platform-rel-Intel]
: crash, leave-open
Product: Core
Classification: Components
Component: Graphics (show other bugs)
: Trunk
: x86 Windows 7
: -- critical with 3 votes (vote)
: ---
Assigned To: Nobody; OK to take it and work on it
:
:
Mentors:
Depends on: 628129 715921
Blocks: 601079 605779 605780 1297204
  Show dependency treegraph
 
Reported: 2011-02-19 02:50 PST by Scoobidiver (away)
Modified: 2016-08-29 04:38 PDT (History)
15 users (show)
See Also:
Crash Signature:
QA Whiteboard:
Iteration: ---
Points: ---
Has Regression Range: ---
Has STR: ---
?
-
affected

MozReview Requests
Submitter Diff Changes Open Issues Last Updated
Loading...
Error loading review requests:
Show discarded requests

Attachments
Bug 635464: Diagnostic crash in nightly and aurora, to see if we are asking basic content client for alpha. (58 bytes, text/x-review-board-request)
2016-07-19 09:52 PDT, Milan Sreckovic [:milan]
bas: review+
Details | Review

Description Scoobidiver (away) 2011-02-19 02:50:41 PST
It is a crash signature that still happens in certain conditions, that is the switching from ATI's GPU to Intel's GPU.
It is #236 crasher in 4.0b11 over the last week.

Stack traces are various.

Correlations by module give:
     95% (21/22) vs.   2% (1435/62097) igd10umd32.dll
         41% (9/22) vs.   0% (9/62097) 8.15.10.2125
         55% (12/22) vs.   0% (12/62097) 8.15.10.2141
Intel's driver blocklisting is not taken into account because when Firefox is launched, the vendor ID is ATI/AMD.


Comments say:
"ThinkPad W500 with "switchable graphics": crashed after completing switch from ATI Mobility FireGL V5700 to Intel Mobile Graphics. Web content area of Firefox window was black for a moment, then content displayed, then crash."
"ThinkPad W500 switch from discrete ATI Mobility FireGL V5700 to (chipset) Intel Accelerated graphics. Current web content tries to display, but crashes."
"after switching AMD graphics to Intel graphics O:-)"

More reports at:
https://crash-stats.mozilla.com/report/list?range_value=4&range_unit=weeks&signature=_VEC_memzero&version=Firefox%3A4.0b11
Comment 1 kitchin 2011-02-28 05:34:22 PST
FYI, those are driver versions Microsoft is blocking from getting Win7 SP1.
http://support.microsoft.com/kb/2498452
* Igdkmd32.sys (32-bit), versions 8.15.10.2104 through 8.15.10.2141
* Igdkmd64.sys (64-bit), versions 8.15.10.2104 through 8.15.10.2141
Comment 2 GMA 2011-03-01 03:02:49 PST
The only way to solve this at the moment is to ask G45 chipset(X4500HD/MHD IGP) users to update to latest drivers 8.15.10.2281 if possible.

32bit
http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&ProdId=2991&DwnldID=19788

64bit
http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&ProdId=2991&DwnldID=19784

And for HD Graphics(Clarkdale/Arrandale) users to update to latest drivers 8.15.10.2291 if possible.

32bit
http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&ProdId=3319&DwnldID=19807

64bit
http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&ProdId=3319&DwnldID=19809
Comment 3 Scoobidiver (away) 2011-03-01 03:08:15 PST
> The only way to solve this at the moment is to ask G45 chipset(X4500HD/MHD IGP)
> users to update to latest drivers 8.15.10.2281 if possible.
No because these users use an ATI's driver not an Intel's one.
Comment 4 Scoobidiver (away) 2012-01-20 01:37:58 PST
An unknown bug added _VEC_memzero to the skiplist (see https://github.com/mozilla/socorro/blob/master/scripts/config/processorconfig.py.dist).
Comment 5 Robert Kaiser 2012-01-20 04:32:24 PST
(In reply to Scoobidiver from comment #4)
> An unknown bug added _VEC_memzero to the skiplist (see
> https://github.com/mozilla/socorro/blob/master/scripts/config/
> processorconfig.py.dist).

bug 715921 (as mentioned in the commit message for this line - https://github.com/mozilla/socorro/commit/ef1bfa72005612d560bd4feea7a1fe93bf8e8a88 ) as requested by :mats.

I'm also not sure if this updated skiplist has even been deployed to production yet.
Comment 6 Sheila Mooney 2012-02-06 16:18:59 PST
Kairo, do you know when it's supposed to be added?
Comment 7 Benoit Jacob [:bjacob] (mostly away) 2012-02-06 19:08:16 PST
Note that these driver versions (8.15.10.2141 and below) are *already* blacklisted. On Win7 / Intel GMA X4500/HD , everything under 8.15.10.2202 is blacklisted, see 
https://wiki.mozilla.org/Blocklisting/Blocked_Graphics_Drivers#Intel_cards

As Scoobidiver notes in comment 3, this is explained by the fact that we get confused by the fact that there are two GPUs.

CC'ing Ali. At some point there was a proposal to require, in case of dual GPUs, that we require both driver versions to be high enough, regardless of which GPU is currently in use. Is there a bug number for this? I would support that move now.
Comment 8 Scoobidiver (away) 2012-02-06 23:24:20 PST
This bug is about switching GPUs (12%) and bug 711656 is about startup crashes (88%).

(In reply to Benoit Jacob [:bjacob] from comment #7)
> As Scoobidiver notes in comment 3, this is explained by the fact that we get
> confused by the fact that there are two GPUs.
For startup crashes, the GPU is Intel and the driver version looks like 8.15.10.xxxx in almost all cases so there's no confusion.
Comment 9 Ali Juma [:ajuma] 2012-02-07 07:05:22 PST
(In reply to Benoit Jacob [:bjacob] from comment #7)
 > As Scoobidiver notes in comment 3, this is explained by the fact that we get
> confused by the fact that there are two GPUs.
> 
> CC'ing Ali. At some point there was a proposal to require, in case of dual
> GPUs, that we require both driver versions to be high enough, regardless of
> which GPU is currently in use. Is there a bug number for this? I would
> support that move now.

Filed Bug 724874 for this.
Comment 10 Benoit Jacob [:bjacob] (mostly away) 2012-02-07 07:48:32 PST
(In reply to Scoobidiver from comment #8)
> This bug is about switching GPUs (12%) and bug 711656 is about startup
> crashes (88%).
> 
> (In reply to Benoit Jacob [:bjacob] from comment #7)
> > As Scoobidiver notes in comment 3, this is explained by the fact that we get
> > confused by the fact that there are two GPUs.
> For startup crashes, the GPU is Intel and the driver version looks like
> 8.15.10.xxxx in almost all cases so there's no confusion.

So, these users are already blacklisted, so I really don't see how they can crash?

Are volumes low enough to allow for the hypothesis that it's power-users who have set .force-enabled in about:config?
Comment 11 Scoobidiver (away) 2012-02-07 08:36:03 PST
(In reply to Benoit Jacob [:bjacob] from comment #10)
> So, these users are already blacklisted, so I really don't see how they can
> crash?
These users are no longer blacklisted from 11.0a1/20111215. See bug 711656 comment 16 (same crash signature but only for startup crashes).
Comment 13 Anthony Hughes (:ashughes) [GFX][QA][Mentor] 2014-06-02 10:02:03 PDT
This has come back again, #7 on Aurora, but may just be the random AMD issue we've been having for over a year.
Comment 14 Sylvestre Ledru [:sylvestre] 2014-06-03 05:13:19 PDT
Topcrash, tracking!
Comment 15 Sylvestre Ledru [:sylvestre] 2014-06-12 08:41:00 PDT
It is not longer in the top #20. It could have been the AMD bug. Untracking.
Comment 16 Milan Sreckovic [:milan] 2016-07-19 09:52:53 PDT
Created attachment 8772465 [details]
Bug 635464: Diagnostic crash in nightly and aurora, to see if we are asking basic content client for alpha.

Review commit: https://reviewboard.mozilla.org/r/65260/diff/#index_header
See other reviews: https://reviewboard.mozilla.org/r/65260/
Comment 17 Bas Schouten (:bas.schouten) 2016-07-19 18:53:26 PDT
Comment on attachment 8772465 [details]
Bug 635464: Diagnostic crash in nightly and aurora, to see if we are asking basic content client for alpha.

https://reviewboard.mozilla.org/r/65260/#review62424

::: gfx/layers/client/ContentClient.cpp:131
(Diff revision 1)
>                                   RefPtr<gfx::DrawTarget>* aBlackDT,
>                                   RefPtr<gfx::DrawTarget>* aWhiteDT)
>  {
>    MOZ_ASSERT(!(aFlags & BUFFER_COMPONENT_ALPHA));
> +  if (aFlags & BUFFER_COMPONENT_ALPHA) {
> +    gfxDevCrash(LogReason::AlphaWithBasicClient) << "Asking basic content client for alpha";

I'd prefer adding 'Component alpha' explicitly in the message here to avoid confusion. It's common place to ask it for regular alpha clients.
Comment 18 Milan Sreckovic [:milan] 2016-07-20 07:26:51 PDT
Comment on attachment 8772465 [details]
Bug 635464: Diagnostic crash in nightly and aurora, to see if we are asking basic content client for alpha.

Review request updated; see interdiff: https://reviewboard.mozilla.org/r/65260/diff/1-2/
Comment 19 Pulsebot 2016-07-21 07:47:55 PDT
Pushed by msreckovic@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/115209d4f543
Diagnostic crash in nightly and aurora, to see if we are asking basic content client for alpha. r=bas
Comment 20 Carsten Book [:Tomcat] 2016-07-22 03:02:20 PDT
https://hg.mozilla.org/mozilla-central/rev/115209d4f543
Comment 21 Milan Sreckovic [:milan] 2016-07-25 11:26:37 PDT
No crashes with this extra info over the weekend.
Comment 22 Chris Pearce (:cpearce) 2016-08-23 15:38:07 PDT
I see this crash 100% of the time when I load netflix.com in current Win32 Nightly on my Lenovo W530 running Win7 x64.

For example:

https://crash-stats.mozilla.com/report/index/b371e24e-f2e9-4e6c-b2dc-da97d2160823

Is there any debug information I can collect to help fix this bug?
Comment 23 Bas Schouten (:bas.schouten) 2016-08-24 04:49:29 PDT
(In reply to Chris Pearce (:cpearce) from comment #22)
> I see this crash 100% of the time when I load netflix.com in current Win32
> Nightly on my Lenovo W530 running Win7 x64.
> 
> For example:
> 
> https://crash-stats.mozilla.com/report/index/b371e24e-f2e9-4e6c-b2dc-
> da97d2160823
> 
> Is there any debug information I can collect to help fix this bug?

Can you catch it in a debugger and get a full stack? The stack on that is pretty useless.
Comment 24 Milan Sreckovic [:milan] 2016-08-25 11:27:40 PDT
This is a much better stack: https://crash-stats.mozilla.com/report/index/a7f4d884-7033-44e5-a218-7ac122160822

Bas - thoughts?
Comment 25 Bas Schouten (:bas.schouten) 2016-08-29 04:36:35 PDT
(In reply to Milan Sreckovic [:milan] from comment #24)
> This is a much better stack:
> https://crash-stats.mozilla.com/report/index/a7f4d884-7033-44e5-a218-
> 7ac122160822
> 
> Bas - thoughts?

Note that that stack is an EXCEPTION_BREAKPOINT, it also appears from the metadata to be happening during a device reset. That's problematic in itself, but a little less worrying than the other one which seems to have happened in a clean situation and in a reproducible manner. Then again, they might simply be totally different bugs.
Comment 26 Bas Schouten (:bas.schouten) 2016-08-29 04:38:07 PDT
(In reply to Bas Schouten (:bas.schouten) from comment #25)
> (In reply to Milan Sreckovic [:milan] from comment #24)
> > This is a much better stack:
> > https://crash-stats.mozilla.com/report/index/a7f4d884-7033-44e5-a218-
> > 7ac122160822
> > 
> > Bas - thoughts?
> 
> Note that that stack is an EXCEPTION_BREAKPOINT, it also appears from the
> metadata to be happening during a device reset. That's problematic in
> itself, but a little less worrying than the other one which seems to have
> happened in a clean situation and in a reproducible manner. Then again, they
> might simply be totally different bugs.

Note the latter stack trace is more likely to occur on a GPU switch. But if in that situation something inside the driver decides to throw a random exception (i.e. int 3), there's not much we can do other than handle it? But that would require wrapping a lot of commands in exception handlers which I doubt we'll want to do. Contacting AMD may be the best option.

Note You need to log in before you can comment on or make changes to this bug.