Nouveau - Feb 2008 - [Bug 14345] New: Image with width greater than 8176 pixel make firefox crash with X error

http://bugs.freedesktop.org/show_bug.cgi?id=14345

           Summary: Image with width greater than 8176 pixel make firefox
                    crash with X error
           Product: xorg
           Version: 7.2
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Driver/nouveau
        AssignedTo: nouveau at lists.freedesktop.org
        ReportedBy: mjulien.m at gmail.com
         QAContact: xorg-team at lists.x.org


Created an attachment (id=14113)
 --> (http://bugs.freedesktop.org/attachment.cgi?id=14113)
Image 8177x1 pixel, make firefox crash

Hi,

with Nouveau, image greater than 8176 pixel make firefox (2.x and 3.0) crash
with this error :

The program 'gecko' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
  (Details: serial 2281 error_code 11 request_code 53 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)


Konqueror doesn't crash but doesn't display the image and print :

X Error: BadAlloc (insufficient resources for operation) 11
  Major opcode:  53
  Minor opcode:  0
  Resource id:  0x26003c3
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
  Major opcode:  72
  Minor opcode:  0
  Resource id:  0x26003c3
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
  Major opcode:  72
  Minor opcode:  0
  Resource id:  0x26003c3
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
  Major opcode:  72
  Minor opcode:  0
  Resource id:  0x26003c3
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
  Major opcode:  72
  Minor opcode:  0
  Resource id:  0x26003c3
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
  Major opcode:  72
  Minor opcode:  0
  Resource id:  0x26003c3
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
  Major opcode:  72
  Minor opcode:  0
  Resource id:  0x26003c3
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
  Major opcode:  72
  Minor opcode:  0
  Resource id:  0x26003c3
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
  Major opcode:  72
  Minor opcode:  0
  Resource id:  0x26003c3
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
  Major opcode:  72
  Minor opcode:  0
  Resource id:  0x26003c3
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
  Major opcode:  72
  Minor opcode:  0
  Resource id:  0x26003c3
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
  Major opcode:  72
  Minor opcode:  0
  Resource id:  0x26003c3
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
  Major opcode:  72
  Minor opcode:  0
  Resource id:  0x26003c3
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
  Major opcode:  72
  Minor opcode:  0
  Resource id:  0x26003c3
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
  Major opcode:  72
  Minor opcode:  0
  Resource id:  0x26003c3
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
  Major opcode:  72
  Minor opcode:  0
  Resource id:  0x26003c3
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
  Major opcode:  155
  Minor opcode:  4
  Resource id:  0x26003c3
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
  Major opcode:  62
  Minor opcode:  0
  Resource id:  0x26003c3
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
  Major opcode:  62
  Minor opcode:  0
  Resource id:  0x26003c3
X Error of failed request:  RenderBadPicture (invalid Picture parameter)
  Major opcode of failed request:  155 (RENDER)
  Minor opcode of failed request:  7 (RenderFreePicture)
  Picture id in failed request: 0x26003c6
  Serial number of failed request:  9414
  Current serial number in output stream:  9827


Opera display the image fine

With nv driver and proprietary nvidia driver, firefox displays the image and
doesn't crash.

I don't see anything in logs related to this problem (though I didn't
insert
drm with debug option).


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

http://bugs.freedesktop.org/show_bug.cgi?id=14345





--- Comment #1 from Mjules <mjulien.m at gmail.com>  2008-02-03 04:29:46
PST ---
real website which exhibit the bug (as reported by gQuigs 
http://people.freedesktop.org/~ahuillet/irclogs/nouveau-2008-02-03.htm#0522 )

www.howtoforge.com


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

http://bugs.freedesktop.org/show_bug.cgi?id=14345





--- Comment #2 from Maarten Maathuis <madman2003 at gmail.com>  2008-02-03
06:27:43 PST ---
The bug is hopefully gone now, but please verify.


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

http://bugs.freedesktop.org/show_bug.cgi?id=14345





--- Comment #3 from Mjules <mjulien.m at gmail.com>  2008-02-03 07:58:03
PST ---
Bug still here with latest git (same error) :/ 

commit 9d9a5acae1deae8c76b512362634066e0c32a817
Author: Jaime Velasco Juan <jsagarribay at gmail.com>
Date:   Sun Feb 3 15:45:32 2008 +0100

    Don't FIRE_RING() when in NoAccel mode.



I just inserted drm with debug=1 et no relevant message appears in syslog/dmesg


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

http://bugs.freedesktop.org/show_bug.cgi?id=14345





--- Comment #4 from Maarten Maathuis <madman2003 at gmail.com>  2008-02-03
10:00:08 PST ---
I couldn't reproduce your issue and i'm not sure what the issue is.


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

http://bugs.freedesktop.org/show_bug.cgi?id=14345





--- Comment #5 from Mjules <mjulien.m at gmail.com>  2008-02-03 12:10:09
PST ---
I'm using Xserver 1.3 (Xorg 7.2) on x86_64 arch.

With option NoAccel, the bug doesn't occur, so it may be related to EXA.

If I remember correctly,  you are using Xserver 1.4.x, maybe it's a bug
already
fixed in this release.


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

http://bugs.freedesktop.org/show_bug.cgi?id=14345





--- Comment #6 from Maarten Maathuis <madman2003 at gmail.com>  2008-03-08
05:30:39 PST ---
Still an issue?


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

http://bugs.freedesktop.org/show_bug.cgi?id=14345





--- Comment #7 from Mjules <mjulien.m at gmail.com>  2008-03-08 07:01:32
PST ---
(In reply to comment #6)
> Still an issue?
> 
yes, still occurs  with fresh git


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

http://bugs.freedesktop.org/show_bug.cgi?id=14345


Victor Stinner <victor.stinner at haypocalc.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |victor.stinner at haypocalc.com




--- Comment #8 from Victor Stinner <victor.stinner at haypocalc.com> 
2008-03-26 08:15:31 PST ---
Using Xorg 7.3 / Xserver 1.4 and today git, it still crashs with:
 The program 'firefox-bin' received an X Window System error.
 This probably reflects a bug in the program.
 The error was 'BadAlloc (insufficient resources for operation)'.
   (Details: serial 22204 error_code 11 request_code 53 minor_code 0)
   (Note to programmers: normally, X errors are reported asynchronously;
    that is, you will receive the error a while after causing it.
    To debug your program, run it with the --sync command line
    option to change this behavior. You can then get a meaningful
    backtrace from your debugger if you break on the gdk_x_error() function.)


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

http://bugs.freedesktop.org/show_bug.cgi?id=14345


Michel D?nzer <michel at tungstengraphics.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
          Component|Driver/nouveau              |Acceleration/EXA
         Resolution|                            |FIXED




--- Comment #9 from Michel D?nzer <michel at tungstengraphics.com> 
2008-03-26 08:41:12 PST ---
This should be fixed in xserver commit
bc2d516f16d94c805b4dfa8e5b9eef40ff0cbe98, which is part of the upcoming 1.5
release. Please reopen if that turns out not to be the case.


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.