dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 54057] New: opengl apps crash at run
Date: Sat, 25 Aug 2012 16:39:59 +0000	[thread overview]
Message-ID: <bug-54057-502@http.bugs.freedesktop.org/> (raw)

https://bugs.freedesktop.org/show_bug.cgi?id=54057

             Bug #: 54057
           Summary: opengl apps crash at run
    Classification: Unclassified
           Product: Mesa
           Version: git
          Platform: x86-64 (AMD64)
        OS/Version: Linux (All)
            Status: NEW
          Severity: critical
          Priority: medium
         Component: Drivers/Gallium/r300
        AssignedTo: dri-devel@lists.freedesktop.org
        ReportedBy: son_of_the_osiris@interia.pl


Created attachment 66111
  --> https://bugs.freedesktop.org/attachment.cgi?id=66111
xorg.log

Hardware : radeon 9600 agp
using mesa-git xorg-server-git pixman-git xf86-video-ati-git
>From few days I segfault when I run opengl app.
here is what valgrind says when run glxgears:

Running synchronized to the vertical refresh.  The framerate should be
approximately the same as the monitor refresh rate.
==16783== Warning: set address range perms: large range [0x394c9040,
0x594c9040) (undefined)
==16783== Invalid write of size 8
==16783==    at 0x7D5DF2A: memory_pool_malloc (in
/usr/lib/xorg/modules/dri/r300_dri.so)
==16783==    by 0x7D5824D: rc_alloc_instruction (in
/usr/lib/xorg/modules/dri/r300_dri.so)
==16783==    by 0x7D6C1DF: ??? (in /usr/lib/xorg/modules/dri/r300_dri.so)
==16783==    by 0x7D6CD8B: rc_emulate_loops (in
/usr/lib/xorg/modules/dri/r300_dri.so)
==16783==    by 0x7D56E9D: rc_run_compiler_passes (in
/usr/lib/xorg/modules/dri/r300_dri.so)
==16783==    by 0x7D56F46: rc_run_compiler (in
/usr/lib/xorg/modules/dri/r300_dri.so)
==16783==    by 0x7D675AF: r3xx_compile_fragment_program (in
/usr/lib/xorg/modules/dri/r300_dri.so)
==16783==    by 0x7D5E6D9: ??? (in /usr/lib/xorg/modules/dri/r300_dri.so)
==16783==    by 0x7D5F7E6: r300_pick_fragment_shader (in
/usr/lib/xorg/modules/dri/r300_dri.so)
==16783==    by 0x7D51AF7: r300_update_derived_state (in
/usr/lib/xorg/modules/dri/r300_dri.so)
==16783==    by 0x7D489B9: ??? (in /usr/lib/xorg/modules/dri/r300_dri.so)
==16783==    by 0x7F7EE9A: ??? (in /usr/lib/xorg/modules/dri/r300_dri.so)
==16783==  Address 0x0 is not stack'd, malloc'd or (recently) free'd
==16783== 
==16783== 
==16783== Process terminating with default action of signal 11 (SIGSEGV)
==16783==  Access not within mapped region at address 0x0
==16783==    at 0x7D5DF2A: memory_pool_malloc (in
/usr/lib/xorg/modules/dri/r300_dri.so)
==16783==    by 0x7D5824D: rc_alloc_instruction (in
/usr/lib/xorg/modules/dri/r300_dri.so)
==16783==    by 0x7D6C1DF: ??? (in /usr/lib/xorg/modules/dri/r300_dri.so)
==16783==    by 0x7D6CD8B: rc_emulate_loops (in
/usr/lib/xorg/modules/dri/r300_dri.so)
==16783==    by 0x7D56E9D: rc_run_compiler_passes (in
/usr/lib/xorg/modules/dri/r300_dri.so)
==16783==    by 0x7D56F46: rc_run_compiler (in
/usr/lib/xorg/modules/dri/r300_dri.so)
==16783==    by 0x7D675AF: r3xx_compile_fragment_program (in
/usr/lib/xorg/modules/dri/r300_dri.so)
==16783==    by 0x7D5E6D9: ??? (in /usr/lib/xorg/modules/dri/r300_dri.so)
==16783==    by 0x7D5F7E6: r300_pick_fragment_shader (in
/usr/lib/xorg/modules/dri/r300_dri.so)
==16783==    by 0x7D51AF7: r300_update_derived_state (in
/usr/lib/xorg/modules/dri/r300_dri.so)
==16783==    by 0x7D489B9: ??? (in /usr/lib/xorg/modules/dri/r300_dri.so)
==16783==    by 0x7F7EE9A: ??? (in /usr/lib/xorg/modules/dri/r300_dri.so)
==16783==  If you believe this happened as a result of a stack
==16783==  overflow in your program's main thread (unlikely but
==16783==  possible), you can try to increase the size of the
==16783==  main thread stack using the --main-stacksize= flag.
==16783==  The main thread stack size used in this run was 8388608.
==16783== 
==16783== HEAP SUMMARY:
==16783==     in use at exit: 1,075,765,942 bytes in 2,709 blocks
==16783==   total heap usage: 16,262 allocs, 13,553 frees, 1,078,507,740 bytes
allocated
==16783== 
==16783== LEAK SUMMARY:
==16783==    definitely lost: 1,136 bytes in 2 blocks
==16783==    indirectly lost: 144 bytes in 2 blocks
==16783==      possibly lost: 76,237 bytes in 1,069 blocks
==16783==    still reachable: 1,075,688,425 bytes in 1,636 blocks
==16783==         suppressed: 0 bytes in 0 blocks
==16783== Rerun with --leak-check=full to see details of leaked memory
==16783== 
==16783== For counts of detected and suppressed errors, rerun with: -v
==16783== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 2 from 2)
Memory protection fault

aslo I add my xorg.log

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

             reply	other threads:[~2012-08-25 16:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-25 16:39 bugzilla-daemon [this message]
2012-08-25 17:11 ` [Bug 54057] opengl apps crash at run bugzilla-daemon
2012-08-25 17:12 ` bugzilla-daemon
2012-08-25 17:15 ` bugzilla-daemon
2012-08-27  9:22 ` bugzilla-daemon
2012-08-27 14:20 ` bugzilla-daemon
2012-08-27 14:46 ` bugzilla-daemon
2012-08-27 15:44 ` bugzilla-daemon
2012-08-28  0:57 ` [Bug 54057] r300g: opengl apps crash at run - possible build problem bugzilla-daemon
2012-08-28  1:05 ` bugzilla-daemon
2012-08-28  3:07 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-54057-502@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox