Uploaded image for project: 'Qt'
  1. Qt
  2. QTBUG-20724

ShaderEffectItems don't work on Symbian/OpenGL graphics system after app background/forground switch

    XMLWordPrintable

Details

    • 4eb50fbbf414103fb2f9dfb8260f4db5d61190c4

    Description

      On Symbian OpenGL graphics system releases all GL resources (including GL context) when app goes to background and recreates them when app comes back to foreground.
      Shaders plugin don't release its GL resources and after app background/foreground those resources are still binded to invalid/destroyed context. Shaders plugin
      should track GL contexts and release its GL resources when contexts is cleaned up.

      Attachments

        1. Fix_to_QTBUG-20736_and_QTBUG-20736_v2.patch
          15 kB
          Marko Niemelä
        2. shadereffects.zip
          1.26 MB
          Jani Hautakangas
        3. shaders.patch
          14 kB
          Jani Hautakangas

        Issue Links

          is required for

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-20736 ShaderEffectItems start consuming GPU memory already at load time even if they are not shown. Also they consume GPU memory while application is in background.

          • P1: Critical - Urgent and Important, will STOP the release if matched with set FixVersion field. This includes regressions from the last version that are not edge cases; Data loss; Build issues; All but the most unlikely crashes/lockups/hanging; Serious usability issues and embarrassing bugs & Bugs critical to a deliverable. This is the highest possible priority for requirements.
          • Closed
          relates to

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-20736 ShaderEffectItems start consuming GPU memory already at load time even if they are not shown. Also they consume GPU memory while application is in background.

          • P1: Critical - Urgent and Important, will STOP the release if matched with set FixVersion field. This includes regressions from the last version that are not edge cases; Data loss; Build issues; All but the most unlikely crashes/lockups/hanging; Serious usability issues and embarrassing bugs & Bugs critical to a deliverable. This is the highest possible priority for requirements.
          • Closed

          Activity

            People

              jhautaka Jani Hautakangas
              jhautaka Jani Hautakangas
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: