Memory Leak

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #47656
    Support
    Keymaster

      Hello

      Can you show it remotely?

      #47663
      emailaya
      Participant

        I don't even know how to reproduce it

        I get this report when I close the app so I can't connect between action and leak

        I had it only once though

        #47931
        guyinwonder
        Participant
          'emailaya' wrote:

          I'm using AC760, here is the entry from the FASTMM report:

          A memory block has been leaked. The size is: 36

          This block was allocated by thread 0xC90, and the stack trace (return addresses) at the time was:

          403446

          40802F

          407630

          4A783E [DB.pas][DB][DB.TWideStringField.GetValue][5264]

          7454FEAD

          74550DDA

          745524D5

          745524FC

          516D80 [Controls.pas][Controls][Controls.TWinControl.WndProc][9336]

          61248B [sSkinManager.pas][sSkinManager][sSkinManager.TsSkinManager.IsValidSkinIndex][1753]

          5CC587 [sPanel.pas][sPanel][sPanel.TsPanel.WndProc][507]

          The block is currently used for an object of class: UnicodeString

          The allocation number is: 1725449

          Current memory dump of 256 bytes starting at pointer address 7EA4DE30:

          B0 04 02 00 01 00 00 00 0B 00 00 00 52 00 65 00 63 00 79 00 63 00 6C 00 65 00 20 00 62 00 69 00

          6E 00 00 00 1D 3C E3 CE 00 00 00 00 51 DC A4 7E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

          0C 94 01 00 46 34 40 00 2F 80 40 00 30 76 40 00 28 9B 46 00 DD 9A 46 00 8E 88 48 00 20 74 48 00

          93 7E 48 00 12 77 48 00 51 76 48 00 9E 02 51 00 90 0C 00 00 90 0C 00 00 C9 61 40 00 CD 84 40 00

          15 84 40 00 53 4E 40 00 96 4D 40 00 11 53 40 00 D6 D8 4E 00 4E F4 48 00 44 F2 48 00 E4 FF 50 00

          9D 4D 40 00 1C 00 00 00 B0 04 02 00 D2 C2 A6 84 78 A1 D3 00 80 80 80 80 80 80 80 80 80 80 80 80

          80 80 80 80 80 80 80 80 80 80 80 80 2D 3D 59 7B 80 80 80 80 80 80 80 80 00 00 00 00 91 E4 A4 7E

          00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 C0 94 01 00 46 34 40 00 7F 4D 40 00 C6 52 40 00

          ° . . . . . . . . . . . R . e . c . y . c . l . e . . b . i .

          n . . . . < ד ־ . . . . Q  ₪ ~ . . . . . . . . . . . . . . . . . ” . . F 4 @ . / € @ . 0 v @ . ( › F .  š F . Ž ˆ H . t H . “ ~ H . . w H . Q v H . ž . Q . . . . . . . ֹ a @ . ֽ „ @ . . „ @ . S N @ . – M @ . . S @ . ײ ״ N . N פ H . D ע H . ה  P . M @ . . . . . ° . . . ׂ ֲ ¦ „ x ¡ ׃ . € € € € € € € € € € € € € € € € € € € € € € € € – = Y { € € € € € € € € . . . . ‘ ה ₪ ~ . . . . . . . . . . . . . . . . ְ ” . . F 4 @ .  M @ . ֶ R @ .

          this leak caused by some of the unicode string or variable being used without proper initialization and finalization,

          on my case usually when i use record to store string data (which on 2010 above string considered as unicode and using string in record need to be initialized.)

          on your case it looks like u use some TDataset Decendant which later on the data you stored some where else without proper finalization.

          so in my opinion this leak is not caused by the SkinManager, but leak happened at somewhere else.

        Viewing 3 posts - 1 through 3 (of 3 total)
        • You must be logged in to reply to this topic.