Forums - Adreno profiler crash

4 posts / 0 new
Last post
Adreno profiler crash
ronan.bel
Profile picture
Join Date: 24 Oct 14
Location: Montpellier
Posts: 13
Posted: Tue, 2014-11-04 03:17

Hi,

trying to debug some code, the profiler crashes while dumping a frame on a texture "capture"

#define GL_R8                           0x8229
#define GL_RED                        0x1903
#define GL_UNSIGNED_BYTE  0x1401
 

In DirectX API, it would be  DXGI_FORMAT_R8_UNORM

 

  • Up0
  • Down0
Dave Astle
Profile picture
Join Date: 19 Oct 12
Location: San Diego, CA
Posts: 101
Posted: Thu, 2014-11-06 11:18

I don't think we have much content that uses R8, so that could very well be a bug in the texture converter code. We'll look into it.

  • Up0
  • Down0
ronan.bel
Profile picture
Join Date: 24 Oct 14
Location: Montpellier
Posts: 13
Posted: Fri, 2014-11-14 13:18

Hi Dave.

To be more "explicit" (sorry for my poor french-glish), it doesn't crash, you can skip the error clicking on the "ignore" button.

R16UI are handled, but all R8UI raise this assert.

From today (I spend most of the day updating all the devices that I can get, to have one with Android 5.0 and the "magic" v95 driver) I can go further in my code.

I've just launched "Adreno profiler", captured a frame, and now, it crashes a the end of the capture.

in "QXProfilerControls.ScrubberViewES20.PrivateRender"

I can send you (the same way as before) an APK so that you can reproduce the crash if you want.

 

And by the way, concerning the "driver", one pass of my code renders to a R10G10B10A2 (unorm) texture (shader emits a vec4 value)

I'm using these parameters for texture settings (GL_RGB10_A2, GL_RGBA, GL_UNSIGNED_INT_2_10_10_10_REV)

it works fine in OpenGL (nvidia,ati,intel), in OpenGL ES 3.0 (intel), but raises a warning in the eclipse logcat on an Android 5.0 v95 device :

Tag : Adreno-ES20

Text : <oxili_check_sp_rb_fmt_mismatch:86>: WARNING : Rendertarget does not match shader output type

I don't know if the fault comes from my code, if it's a wrong warning, if it's a true warning that I don't understand.

If you want to try ... it's the same APK that causes a crash in the profiler.

 

  • Up0
  • Down0
ronan.bel
Profile picture
Join Date: 24 Oct 14
Location: Montpellier
Posts: 13
Posted: Fri, 2014-11-14 14:21

And another question [11PM in France, will be the last one for today :) ]

on my test v95 driver device, now I can use gl_VertexID

(replace mpo_GLInterface by gl to get standard code)(and forget about the ReportError)

when I use a VS with only gl_VertexID has input (no VB), the following code runs fine on

OpenGL (intel,nvidia,ati), OpenGL ES 3.0 (intel), now runs on Adreno v95 but issues this warning in the logcat

Tag : Adreno ES-20

<validate_vertex_attrib_state:55>: validate_vertex_attrib_state: No vertex attrib is enabled in a draw call!

if I uncomment the (Bind dummyVB, fake attrib) sequence, the GPU renders the same way, but without warning in the logcat

Is this warning really meaning something ?

 

mpo_GLInterface->BindVertexArray( mo_DummyVertexArray );
mpo_GLInterface->ReportError( "BindVertexArray" );
/*
mpo_GLInterface->BindBuffer( GL_ARRAY_BUFFER, mo_DummyVertexBuffer );
mpo_GLInterface->ReportError( "BindBuffer" );
mpo_GLInterface->VertexAttribIPointer( 0, 1, GL_BYTE, 1, 0 );
mpo_GLInterface->ReportError( "VertexAttribPointer" );
mpo_GLInterface->VertexAttribDivisor( 0, 0 );
mpo_GLInterface->EnableVertexAttribArray( 0 );
mpo_GLInterface->ReportError( "EnableVertexAttribArray" );
mpo_GLInterface->BindBuffer(GL_ARRAY_BUFFER, 0);
mpo_GLInterface->ReportError( "BindBuffer" );
*/
 
  • Up0
  • Down0
or Register

Opinions expressed in the content posted here are the personal opinions of the original authors, and do not necessarily reflect those of Qualcomm Incorporated or its subsidiaries (“Qualcomm”). The content is provided for informational purposes only and is not meant to be an endorsement or representation by Qualcomm or any other party. This site may also provide links or references to non-Qualcomm sites and resources. Qualcomm makes no representations, warranties, or other commitments whatsoever about any non-Qualcomm sites or third-party resources that may be referenced, accessible from, or linked to this site.