[Mesa-dev] Crash when watching netflix

[Jason Ekstrand]

Nikolay,
First off, it would be good if you'd make an actual bug for it.  Second,
what mesa version are you using and can you build mesa master and try
running against that?  If you're still having problems, Try and run it in
gdb and break on "_mesa_error" and see if you can get a good backtrace.
--Jason Ekstrand

On Fri, Sep 12, 2014 at 11:13 PM, Nikolay Martynov <mar.kolya at gmail.com>
wrote:

> Sorry, forgot the subject.
>
> 2014-09-13 2:06 GMT-04:00 Nikolay Martynov <mar.kolya at gmail.com>:
> > Hi.
> >
> >   When I watch netflix it crashes with this:
> >
> > err:d3d:wined3d_debug_callback 0x10972478: "GL_OUT_OF_MEMORY in
> glTexSubImage".
> > err:d3d_surface:surface_upload_data >>>>>>>>>>>>>>>>> GL_OUT_OF_MEMORY
> > (0x505) from glTexSubImage2D @ surface.c / 1559
> > err:d3d:wined3d_debug_callback 0x10972478: "GL_OUT_OF_MEMORY in
> glTexSubImage".
> > err:d3d_surface:surface_upload_data >>>>>>>>>>>>>>>>> GL_OUT_OF_MEMORY
> > (0x505) from glTexSubImage2D @ surface.c / 1559
> > err:d3d:wined3d_debug_callback 0x10972478: "GL_OUT_OF_MEMORY in
> glTexSubImage".
> > err:d3d_surface:surface_upload_data >>>>>>>>>>>>>>>>> GL_OUT_OF_MEMORY
> > (0x505) from glTexSubImage2D @ surface.c / 1559
> > err:d3d:wined3d_debug_callback 0x10972478: "GL_OUT_OF_MEMORY in
> glTexSubImage".
> > err:d3d_surface:surface_upload_data >>>>>>>>>>>>>>>>> GL_OUT_OF_MEMORY
> > (0x505) from glTexSubImage2D @ surface.c / 1559
> > wine: Unhandled page fault on write access to 0x00000000 at address
> > 0x7d151a37 (thread 0023), starting debugger...
> > Unhandled exception: page fault on write access to 0x00000000 in
> > 32-bit code (0x7d146a37).
> > Register dump:
> >  CS:0023 SS:002b DS:002b ES:002b FS:0063 GS:006b
> >  EIP:7d146a37 ESP:015ee3f0 EBP:0000c000 EFLAGS:00210202(  R- --  I   - -
> - )
> >  EAX:00000000 EBX:7d379000 ECX:00000000 EDX:00000004
> >  ESI:7bd1f588 EDI:00000000
> > Stack dump:
> > 0x015ee3f0:  7bd0047c 00000004 00000004 7bd1f590
> > 0x015ee400:  7bd1f594 00000021 00000000 7d379000
> > 0x015ee410:  7bd0047c 7bd0047c 7bd0047c 7d1675da
> > 0x015ee420:  7bd0047c 7bd1f588 00000004 00000004
> > 0x015ee430:  7bd1f590 7bd1f594 00000000 7d379000
> > 0x015ee440:  7bd0047c 7bd0047c 7d379000 7d167606
> > Backtrace:
> > =>0 0x7d146a37 in i965_dri.so (+0x337a37) (0x0000c000)
> >   1 0x7d1675da in i965_dri.so (+0x3585d9) (0x0000c000)
> >   2 0x7d167606 in i965_dri.so (+0x358605) (0x0000c000)
> >   3 0x7d1b5226 in i965_dri.so (+0x3a6225) (0x0000c000)
> >   4 0x7d16576c in i965_dri.so (+0x35676b) (0x7bd0047c)
> >   5 0x7d1a1b91 in i965_dri.so (+0x392b90) (0x7bd2e218)
> >   6 0x7d1a24a7 in i965_dri.so (+0x3934a6) (0x7bd2e218)
> >   7 0x7d1533dc in i965_dri.so (+0x3443db) (0x00000100)
> >   8 0x7ce4c567 in i965_dri.so (+0x3d566) (0x00000004)
> >   9 0x7e069fe0 in wined3d (+0x39fdf) (0x015ee818)
> >   10 0x7e066d16 in wined3d (+0x36d15) (0x015ee868)
> >   11 0x7e06632b in wined3d (+0x3632a) (0x015ee888)
> >   12 0x7e066eab in wined3d (+0x36eaa) (0x015ee8a8)
> >
> >
> > I have Ubuntu 14.04, FF and Oibaf ppa installed. It was working fine
> > about a week ago and FF wasn't updated since then. So I suspect it's
> > mesa or Intel driver.
> >
> > What would be best way to debug this?
> > Thanks!
> >
> > --
> > Martynov Nikolay.
> > Email: mar.kolya at gmail.com
> > _______________________________________________
> > mesa-dev mailing list
> > mesa-dev at lists.freedesktop.org
> > http://lists.freedesktop.org/mailman/listinfo/mesa-dev
>
>
>
> --
> Martynov Nikolay.
> Email: mar.kolya at gmail.com
> _______________________________________________
> mesa-dev mailing list
> mesa-dev at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/mesa-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/mesa-dev/attachments/20140913/aad24bcc/attachment.html>