• State Accepted Answer
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 1 reply
  • Subscribers 136 subscribers
  • Views 3482 views
  • Users 0 members are here
Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Not able to Trace App using MGD

Nemo

facing currently 2 issues

1) using processlist.cfg "process = com .xxxx.xxx" is Not logging my app , but not having this log am able to Log the System.

     i use the Following command   to generate the processlist.cfg  : echo     "process = com .xxxx.xxx" > /system/lib/egl/processlist.cfg  , the File Gets Generated but no output on trace.

2) even though i use VBO  -  i see the Following warning

" Detected 150 calls to glVertexAttribPointer without a bound vertex buffer object " .

Please Let me know How to resolve Profiling my app & what does the above error mean ??

Thanks in Advance

Parents
  • +1

    Hi subrymanyam,

    The processlist.cfg is intended to be a line separated list of process names. Your processlist.cfg file should therefore contain just the process name "com.xxxx.xxx", not "process = com.xxxx.xxx". So your command becomes:

    echo "com.xxxx.xxx" > /system/lib/egl/processlist.cfg


    For your second question, MGD is helpfully reporting that for those 150 calls, the value of GL_ARRAY_BUFFER_BINDING was zero, indicating no VBO being bound. The report itself does not imply an error in either your application or MGD, it is just reporting a potential inefficiency in your application, as those 150 calls would have referenced client buffers. Whether this is a problem/potentially sub-optimal situation is completely dependent on your particular situation, we are just highlighting the situation so you can make a judgement call.

    Can you please check your trace output and if you believe there is in fact a VBO bound and MGD is reporting incorrect information, please provide a reproducer or a partial trace showing the problem?

    Thanks,

    Chris

Reply
  • +1

    Hi subrymanyam,

    The processlist.cfg is intended to be a line separated list of process names. Your processlist.cfg file should therefore contain just the process name "com.xxxx.xxx", not "process = com.xxxx.xxx". So your command becomes:

    echo "com.xxxx.xxx" > /system/lib/egl/processlist.cfg


    For your second question, MGD is helpfully reporting that for those 150 calls, the value of GL_ARRAY_BUFFER_BINDING was zero, indicating no VBO being bound. The report itself does not imply an error in either your application or MGD, it is just reporting a potential inefficiency in your application, as those 150 calls would have referenced client buffers. Whether this is a problem/potentially sub-optimal situation is completely dependent on your particular situation, we are just highlighting the situation so you can make a judgement call.

    Can you please check your trace output and if you believe there is in fact a VBO bound and MGD is reporting incorrect information, please provide a reproducer or a partial trace showing the problem?

    Thanks,

    Chris

Children
No data