Bug 92783

Summary:	MESA_DEBUG=incomplete_tex prints warnings from glClear which doesn't use the state
Product:	Mesa	Reporter:	Glenn Kennard <glenn.kennard>
Component:	Mesa core	Assignee:	mesa-dev
Status:	RESOLVED MOVED	QA Contact:	mesa-dev
Severity:	minor
Priority:	low	CC:	ben
Version:	git
Hardware:	All
OS:	All
Whiteboard:
i915 platform:		i915 features:

Description Glenn Kennard 2015-11-02 23:17:58 UTC

Reproducible by running the  arb_texture_view-sampling-2d-array-as-2d-layer piglit test case, the first call to glClear ends up checking the currently bound shader's state for texture completeness and prints the following warning:
Mesa: Texture Obj 0 incomplete because: Image[baseLevel=0] == NULL

As far as I can tell this is due to _mesa_Clear calling _mesa_update_state which eventually gets to _mesa_test_texobj_completeness where the warning is printed.

Checking texture completeness in glClear strikes me as rather odd, in particular since the check is on the api bound shader, not the internal state used for the clear itself.

Comment 1 GitLab Migration User 2019-09-18 20:24:35 UTC

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/996.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.