Bug 22299

Summary:	Mesa 7.4.2: invalid reference to a deleted texture object
Product:	Mesa	Reporter:	Deniz Sarikaya <daimler3>
Component:	Mesa core	Assignee:	mesa-dev
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	medium
Version:	unspecified
Hardware:	x86 (IA32)
OS:	FreeBSD
Whiteboard:
i915 platform:		i915 features:
Attachments:	blend file which could(!?) cause a crash

Description Deniz Sarikaya 2009-06-15 11:18:27 UTC

I reported this bug, because Mesa told me so. ;)
Unfortunately, I don't know why this happens.

Steps to Reproduce:

1) Start Blender (I used 2.49)
2) Render Anything (e.g. the default cube)

or
1) Start ioquake3 (1.36)
2) Close it.


Actual Results:

The application(s) did what it should do (except ioquake3 which crashed with a segmentation fault: "[insert here the Mesa error]...Program received signal SIGABRT, Aborted.
[Switching to Thread 0x28901040 (LWP 100250)]
0x2839c16b in thr_kill () from /lib/libc.so.7
" (gdb output with ioquake3-release build) and then it doesn't change to my default desktop resolution).

Build Date & Platform: 

Build 2009-05-17 on FreeBSD 7.2-STABLE


Here is the Mesa error:

"Mesa 7.4.2 implementation error: invalid reference to a deleted texture object
Please report at bugzilla.freedesktop.org
Assertion failed: (valid_texture_object(oldTex)), function _mesa_reference_texobj, file main/texobj.c, line 305."

Comment 1 Brian Paul 2009-06-15 14:47:15 UTC

I've got blender but don't know how to reproduce the bug.  I rendered a cube but didn't see any failed assertions or anything.

Which driver are you using?

Can you send me a blender project file that fails for you?

Comment 2 Michel Dänzer 2009-06-15 23:25:35 UTC

Which driver are you using? Does it also happen with current Git mesa_7_4_branch?

Comment 3 Deniz Sarikaya 2009-06-16 03:36:08 UTC

I'm using xf86-video-intel-2.7.1.

New Steps to Reproduce (with blender):

1) Start Blender (I used 2.49)
2) Render Anything (e.g. the default cube)
3) Close the window with the rendered image

But strangely I did not do anything new and now the crash only happens rarely (so it's easier to reproduce with ioquake3) when closing the window. Therefore I don't know if the blend file is one which causes a crash. 
The behaviour of ioquake3 is still the same.


I haven't tested the current git version. (I'll do it as fast as possible. :))

Comment 4 Deniz Sarikaya 2009-06-16 03:36:57 UTC

Created attachment 26845 [details]
blend file which could(!?) cause a crash

Comment 5 Deniz Sarikaya 2009-06-16 05:48:38 UTC

I couldn't build the current git branch due to some missing #includes in several files and I don't have the time to fix them all and so now I am going to try building Mesa 7.5 RC3.

Comment 6 Deniz Sarikaya 2009-06-16 06:06:50 UTC

Unfortunately, building Mesa 7.5 RC 3 ends with the same errors (missing #include, definition of MAP_ANON, ...)
If I have the time, I will fix the errors and try building the current git branch again.

...I think I chose the wrong target ("freebsd"). Maybe I should choose "freebsd-dri". :)
If that is not the solution, I am not able to test it with a newer Mesa Version. :(

Comment 7 Deniz Sarikaya 2009-06-16 07:04:38 UTC

Good News!
Building was successful (after copying files from src/dri/intel to /src/dri/i[915/965])!

and it doesn't happen anymore ;)

Comment 8 Michel Dänzer 2009-06-16 07:16:00 UTC

Note that I was asking about the 7.4 branch, not 7.5.

Comment 9 Deniz Sarikaya 2009-06-17 06:25:46 UTC

Oh, really? :D

Sorry, but I'm not familiar with git. So, can you tell me how to checkout the Mesa 7.4 branch? :)

The command I used to checkout mesa was: 
'git clone git://anongit.freedesktop.org/git/mesa/mesa'.
    '

Comment 10 Michel Dänzer 2009-06-17 06:34:56 UTC

(In reply to comment #9)
> 'git clone git://anongit.freedesktop.org/git/mesa/mesa'.

cd mesa
git checkout -b {,origin/}mesa_7_4_branch

Comment 11 Deniz Sarikaya 2009-06-19 14:44:03 UTC

with mesa_7_4_branch this does not happen anymore (but a new intel bug appeared which I've already reported: "Bug 22377").

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.