Results 1 to 4 of 4

Thread: GL ERROR - after deleteUnusedTextures() glError (0x502)

  1. #1
    Sencha User riyaad's Avatar
    Join Date
    Jul 2011
    Location
    Cape Town
    Posts
    245
    Answers
    6
    Vote Rating
    2
      0  

    Default GL ERROR - after deleteUnusedTextures() glError (0x502)

    Hi All,

    I have an application that's already live in the iTunes store. I'm now testing the same application for the Android store. When testing on my device (a Nexus 7 running Android 4.2), I get the following error when scrolling up and down my dataview and/or when displaying and hiding my overlay.

    GL ERROR - after deleteUnusedTextures() glError (0x502)

    There's very limited documentation regarding this error (some claim to be an Android issue) See here.

    ST versions tested: ST2.0 & ST2.1

    Could anyone assist regarding this?

    Thanks
    Riyaad

  2. #2
    Sencha - Sr Software Engineer mitchellsimoens's Avatar
    Join Date
    Mar 2007
    Location
    Gainesville, FL
    Posts
    39,556
    Answers
    3931
    Vote Rating
    1272
      0  

    Default

    This happened in 2.0 also when scrolling?
    Mitchell Simoens @LikelyMitch
    Sencha Inc, Senior Software Engineer
    ________________
    Learn BBCode and use it! Checkout the CODE tag!

    Check out my GitHub, lots of nice things for Ext JS and Sencha Touch
    https://github.com/mitchellsimoens

  3. #3
    Sencha User riyaad's Avatar
    Join Date
    Jul 2011
    Location
    Cape Town
    Posts
    245
    Answers
    6
    Vote Rating
    2
      0  

    Default

    Hi Mitchell

    Thank you for your reply. That is correct and actually the reason I decided to upgrade to 2.1. Ver 2.0 gave the same problem when scrolling. This error appears when debugging using a physical device. The emulator however doesn't report anything.

    Regards,
    Riyaad

  4. #4
    Sencha User
    Join Date
    Nov 2011
    Location
    England
    Posts
    136
    Answers
    11
    Vote Rating
    7
      0  

    Default

    I always receive this error when testing on a device too. I just ignore it as it doesn't seem to have any noticeable effect on the app.

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •