• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 100 subscribers
  • Views 151 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

GPU opengles glTexImage2D memory out of bounds

li daming
Prodigy 200 points

rootfs: 7.2

We detected an array out-of-bounds BUG through the asan software,
In the OpenglES program, we use the cube texture. There is a picture with a width and height of 2*2, the type is GL_RGB8, and a total of 12 bytes. When using the following code, asan detects that the glTexImage2D function has overread 6 bytes.

Fullscreen
1
2
void *imagePtr = malloc(12);
glTexImage2D(GL_TEXTURE_CUBE_MAP_POSITIVE_X + j, i, GL_RGB8, 2, 2, 0, GL_RGB, GL_UNSIGNED_BYTE, imagePtr);
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

This is asan's log

Please help to confirm whether it is a bug?

Regards,

lidaming

  • 0
    TI__Mastermind 36307 points

    Hello,

    What is this asan software? Is this checking the memory access are in-bounds for your program?

    Does this error happen if you do not use this asan software? Does glGetError() report any errors before or after this function call?

    Regards,

    Erick

  • 0 in reply to Erick Narvaez
    Prodigy 200 points

    Hello,

    Yes, asan is a memory boundary detection software full name AddressSanitizer.
    When not using asan detection, use glGetError() before and after the program will not have error prompts.

    Regards,

    lidaming

  • 0 in reply to li daming
    TI__Mastermind 36307 points

    Hello,

    Let me try to replicate this on my end. Are you running on Linux or Linux+RTOS (Vision Apps)?

    I'll see if I can replicate this.

    Thanks,

    Erick

  • 0 in reply to Erick Narvaez
    Prodigy 200 points

    Thanks,

    Linux

    Regards,

    lidaming

  • 0 in reply to li daming
    TI__Mastermind 36307 points

    Hello,

    I am running this using a wayland application and am seeing different memory leaks, not from the driver but from wayland interface.

    What kind of application are you running? Is it simple enough to share? It seems you are directly making calls, like a surfaceless render or similar? I can see the issue when I run in a Vision Apps setup with surfaceless renders.

    Regards,

    Erick