Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Mobile and Embedded
  4. makeCurrent(): no EGLSurface, likely Surface destroyed by Android.
Forum Updated to NodeBB v4.3 + New Features

makeCurrent(): no EGLSurface, likely Surface destroyed by Android.

Scheduled Pinned Locked Moved Unsolved Mobile and Embedded
6 Posts 3 Posters 159 Views 2 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • Z Offline
    Z Offline
    Zerozany
    wrote last edited by
    #1

    Qt for Android 6.9

    This problem always occurs when switching between the front-end and back-end of the application, and it still cannot be solved. Please help

    1 Reply Last reply
    0
    • Z Offline
      Z Offline
      Zerozany
      wrote last edited by
      #2

      makeCurrent(): no EGLSurface, likely Surface destroyed by Android.
      QRhiGles2: Failed to make context current. Expect bad things to happen.
      Failed to start frame

      ---- I've been troubled for a long time

      1 Reply Last reply
      0
      • T Offline
        T Offline
        Torsten_Wier
        wrote last edited by
        #3

        The same in android-Qt6.9.3. It worked in android-Qt5.15.

        Context: App runs in Kiosk mode. Short power button click shall not stop the app but only switches off the screen.

        1 Reply Last reply
        0
        • A Offline
          A Offline
          assam
          wrote last edited by
          #4

          @Torsten_Wier @Zerozany this looks like https://qt-project.atlassian.net/browse/QTBUG-139606, however, usually the log print of "makeCurrent(): no EGLSurface, likely Surface destroyed by Android." is qFatal() so the app would crash, which is not the case in the mentioned bug report, could you provide a reproduction example, ideally in a new bug report?

          1 Reply Last reply
          0
          • A Offline
            A Offline
            assam
            wrote last edited by
            #5

            I just realized from the name that you have a bug about it, I think this is the same case https://qt-project.atlassian.net/browse/QTBUG-142195.

            1 Reply Last reply
            0
            • Z Offline
              Z Offline
              Zerozany
              wrote last edited by
              #6

              @assam Thank you for using a method that cannot completely solve the problem, but it can greatly avoid the probability of occurrence and the issue of switching between the front-end and back-end of the app,

              1 Reply Last reply
              0

              • Login

              • Login or register to search.
              • First post
                Last post
              0
              • Categories
              • Recent
              • Tags
              • Popular
              • Users
              • Groups
              • Search
              • Get Qt Extensions
              • Unsolved