dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 32768] VBO rendering using glDrawArrays causes program termination and "cs IB too big" message
Date: Tue, 25 Jan 2011 11:49:04 -0800 (PST)	[thread overview]
Message-ID: <20110125194904.E332A13004E@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-32768-502@http.bugs.freedesktop.org/>

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

--- Comment #3 from RCX Slinger <rcxslinger@gmail.com> 2011-01-25 11:49:04 PST ---
(In reply to comment #2)
> Created an attachment (id=42437)
 View: https://bugs.freedesktop.org/attachment.cgi?id=42437
 Review: https://bugs.freedesktop.org/review?bug=32768&attachment=42437

> try to use base_vtx as index offset for auto_index 
> 
> Can you try if the attached patch works

Perfect, this solves the bug!

Since the patch makes the instruction buffer stay at the same reliable size, it
might even solve (any) similar bugs. (it also solves some rendering artefacts
noticed but not mentioned)

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

  parent reply	other threads:[~2011-01-25 19:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-32768-502@http.bugs.freedesktop.org/>
2011-01-01 16:11 ` [Bug 32768] VBO rendering using glDrawArrays causes program termination and "cs IB too big" message bugzilla-daemon
2011-01-01 16:33 ` bugzilla-daemon
2011-01-25  8:54 ` bugzilla-daemon
2011-01-25 19:49 ` bugzilla-daemon [this message]
2011-03-07 19:29 ` bugzilla-daemon
2011-04-07 13:04 ` bugzilla-daemon
2011-06-22  8:40 ` bugzilla-daemon
2011-06-22 16: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=20110125194904.E332A13004E@annarchy.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;
as well as URLs for NNTP newsgroup(s).