QPlainTextEdit memory leak











up vote
0
down vote

favorite












I wrote a simple app with Qt 5.9.6, I ran that and wondered the used memory is growing.
After tracing/debugging my application, I realized something about QPlainTextEdit !!!



The memory leak was for a qplaintextedit as a scratchpad in my app, but after every use of that, I used the clear() function to blank it for next use.



But the used memory by that scratchpad woudn't be released!



I decided to test it



I opened a new project, containing a QPlainTextEdit & a QPushButton(to use clear() function).




  • After run, the used memory was 9.7MiB

  • Entered some long text to QPlainTextEdit, the used memory was 52MiB

  • Pressed the QPushButton(clear() the QPlainTextEdit), the expected used memory is 9.7MiB, but it was 52MiB.


I tried delete, static allocation, dynamic allocation..., many ways to manage that, but no different!



I found something in here, but it couldn't solve the problem.



Is this a bug in QPlainTextEdit or I'm doing wrong?










share|improve this question


























    up vote
    0
    down vote

    favorite












    I wrote a simple app with Qt 5.9.6, I ran that and wondered the used memory is growing.
    After tracing/debugging my application, I realized something about QPlainTextEdit !!!



    The memory leak was for a qplaintextedit as a scratchpad in my app, but after every use of that, I used the clear() function to blank it for next use.



    But the used memory by that scratchpad woudn't be released!



    I decided to test it



    I opened a new project, containing a QPlainTextEdit & a QPushButton(to use clear() function).




    • After run, the used memory was 9.7MiB

    • Entered some long text to QPlainTextEdit, the used memory was 52MiB

    • Pressed the QPushButton(clear() the QPlainTextEdit), the expected used memory is 9.7MiB, but it was 52MiB.


    I tried delete, static allocation, dynamic allocation..., many ways to manage that, but no different!



    I found something in here, but it couldn't solve the problem.



    Is this a bug in QPlainTextEdit or I'm doing wrong?










    share|improve this question
























      up vote
      0
      down vote

      favorite









      up vote
      0
      down vote

      favorite











      I wrote a simple app with Qt 5.9.6, I ran that and wondered the used memory is growing.
      After tracing/debugging my application, I realized something about QPlainTextEdit !!!



      The memory leak was for a qplaintextedit as a scratchpad in my app, but after every use of that, I used the clear() function to blank it for next use.



      But the used memory by that scratchpad woudn't be released!



      I decided to test it



      I opened a new project, containing a QPlainTextEdit & a QPushButton(to use clear() function).




      • After run, the used memory was 9.7MiB

      • Entered some long text to QPlainTextEdit, the used memory was 52MiB

      • Pressed the QPushButton(clear() the QPlainTextEdit), the expected used memory is 9.7MiB, but it was 52MiB.


      I tried delete, static allocation, dynamic allocation..., many ways to manage that, but no different!



      I found something in here, but it couldn't solve the problem.



      Is this a bug in QPlainTextEdit or I'm doing wrong?










      share|improve this question













      I wrote a simple app with Qt 5.9.6, I ran that and wondered the used memory is growing.
      After tracing/debugging my application, I realized something about QPlainTextEdit !!!



      The memory leak was for a qplaintextedit as a scratchpad in my app, but after every use of that, I used the clear() function to blank it for next use.



      But the used memory by that scratchpad woudn't be released!



      I decided to test it



      I opened a new project, containing a QPlainTextEdit & a QPushButton(to use clear() function).




      • After run, the used memory was 9.7MiB

      • Entered some long text to QPlainTextEdit, the used memory was 52MiB

      • Pressed the QPushButton(clear() the QPlainTextEdit), the expected used memory is 9.7MiB, but it was 52MiB.


      I tried delete, static allocation, dynamic allocation..., many ways to manage that, but no different!



      I found something in here, but it couldn't solve the problem.



      Is this a bug in QPlainTextEdit or I'm doing wrong?







      memory-management memory-leaks g++ qwidget qplaintextedit






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 19 at 16:08









      mohammads

      1706




      1706





























          active

          oldest

          votes











          Your Answer






          StackExchange.ifUsing("editor", function () {
          StackExchange.using("externalEditor", function () {
          StackExchange.using("snippets", function () {
          StackExchange.snippets.init();
          });
          });
          }, "code-snippets");

          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "1"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














           

          draft saved


          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53378583%2fqplaintextedit-memory-leak%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown






























          active

          oldest

          votes













          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes
















           

          draft saved


          draft discarded



















































           


          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53378583%2fqplaintextedit-memory-leak%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          Wiesbaden

          Marschland

          Dieringhausen