[Mesa-dev] [Bug 27924] [TTM] Illegal buffer object size. Black screen with Compiz
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Tue May 4 15:25:38 PDT 2010
https://bugs.freedesktop.org/show_bug.cgi?id=27924
--- Comment #10 from Xavier <shiningxc at gmail.com> 2010-05-04 15:25:38 PDT ---
(In reply to comment #9)
> FWIW I get textures of size 0x0 in resource_create when texture_from_pixmap is
> used. I guess it might be the reason the buffer allocation is failing. It's
> reproducible via piglit/tfp.
I can indeed reproduce the problem with nv50 on both compiz and tfp.
I've noticed that the commit changed firstImage->base.Width2(,height,depth) to
stObj->width0(,height,depth)
I've enabled DBG and added one printf below :
/* If we already have a gallium texture, check that it matches the texture
* object's format, target, size, num_levels, etc.
*/
if (stObj->pt) {
printf("stobj->pt %dx%dx%d stobj %dx%dx%d firstimage %dx%dx%d\n",
stObj->pt->width0, stObj->pt->height0, stObj->pt->depth0,
stObj->width0, stObj->height0, stObj->depth0,
firstImage->base.Width2, firstImage->base.Height2,
firstImage->base.Depth2);
And this is the ouput with tfp :
st_NewTextureObject
st_NewTextureImage
stobj->pt 2x2x1 stobj 0x0x0 firstimage 2x2x1
Mesa: User error: GL_OUT_OF_MEMORY in glTexImage
stobj->pt 2x2x1 stobj 0x0x0 firstimage 2x2x1
st_NewTextureObject
st_NewTextureImage
st_FreeTextureImageData
stobj->pt 2x2x1 stobj 0x0x0 firstimage 2x2x1
stobj->pt 2x2x1 stobj 0x0x0 firstimage 2x2x1
I doubt this helps, but just in case...
I don't understand what stobj, stobj->pt and firstimage are respectively.
I don't understand that comment below either, but from the output above, the
image dimensions don't seem to match.
/* If both firstImage and stObj point to a texture which can contain
* all active images, favour firstImage. Note that because of the
* completeness requirement, we know that the image dimensions
* will match.
*/
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the mesa-dev
mailing list