Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. The Lounge
  3. Memory leak in ConvertStringToBSTR

Memory leak in ConvertStringToBSTR

Scheduled Pinned Locked Moved The Lounge
helpcombeta-testingperformancequestion
9 Posts 4 Posters 0 Views 1 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.
  • P Offline
    P Offline
    prasad_som
    wrote on last edited by
    #1

    Few days back, I reported this[^] issue to micorsoft.I'm sure you might have comes across this issue before. Initially, it was set to 'Not reproducible' by them. Again, after some more inputs, it is set to 'Resolved(wont fix)', and with no comment. Does this mean, issue does exist , but they are not going to fix it.

    J P J 3 Replies Last reply
    0
    • P prasad_som

      Few days back, I reported this[^] issue to micorsoft.I'm sure you might have comes across this issue before. Initially, it was set to 'Not reproducible' by them. Again, after some more inputs, it is set to 'Resolved(wont fix)', and with no comment. Does this mean, issue does exist , but they are not going to fix it.

      J Offline
      J Offline
      John M Drescher
      wrote on last edited by
      #2

      I believe that Memory Validator stated a few years ago something like the way the memory is allocated in this routine generates false positive. It has been a long time since I have read about that so I may have not got it exactly correct.

      John

      1 Reply Last reply
      0
      • P prasad_som

        Few days back, I reported this[^] issue to micorsoft.I'm sure you might have comes across this issue before. Initially, it was set to 'Not reproducible' by them. Again, after some more inputs, it is set to 'Resolved(wont fix)', and with no comment. Does this mean, issue does exist , but they are not going to fix it.

        P Offline
        P Offline
        peterchen
        wrote on last edited by
        #3

        You can (a) do a visual trace of the code to figure out whether there actually is a leak 8sources are available), or (b) Call ConvertStringToBSTR repeatedly, an release the string and see if you succeed in exhausting memory. (c) both of the above :) Generally, I found Memory Validators very tricky beasts indeed. Like Ferraris with only 4th gear and booster start. So I wouldn't trust them 100%


        Developers, Developers, Developers, Developers, Developers, Developers, Velopers, Develprs, Developers!
        We are a big screwed up dysfunctional psychotic happy family - some more screwed up, others more happy, but everybody's psychotic joint venture definition of CP
        Linkify!|Fold With Us!

        P 1 Reply Last reply
        0
        • P peterchen

          You can (a) do a visual trace of the code to figure out whether there actually is a leak 8sources are available), or (b) Call ConvertStringToBSTR repeatedly, an release the string and see if you succeed in exhausting memory. (c) both of the above :) Generally, I found Memory Validators very tricky beasts indeed. Like Ferraris with only 4th gear and booster start. So I wouldn't trust them 100%


          Developers, Developers, Developers, Developers, Developers, Developers, Velopers, Develprs, Developers!
          We are a big screwed up dysfunctional psychotic happy family - some more screwed up, others more happy, but everybody's psychotic joint venture definition of CP
          Linkify!|Fold With Us!

          P Offline
          P Offline
          prasad_som
          wrote on last edited by
          #4

          I'm amused/confused by microsoft's reply. Really cant understand resolved(won't fix).

          Prasad Notifier using ATL | Operator new[],delete[][^]

          P 1 Reply Last reply
          0
          • P prasad_som

            Few days back, I reported this[^] issue to micorsoft.I'm sure you might have comes across this issue before. Initially, it was set to 'Not reproducible' by them. Again, after some more inputs, it is set to 'Resolved(wont fix)', and with no comment. Does this mean, issue does exist , but they are not going to fix it.

            J Offline
            J Offline
            Joe Woodbury
            wrote on last edited by
            #5

            prasad_som wrote:

            Does this mean, issue does exist , but they are not going to fix it.

            It means, they aren't going to change how it works so your memory leak detector doesn't generate a false report. (I have a class that use to do this once with BoundsChecker--it may still do it, but haven't run it through BC in a long while. I had to just tell BoundsChecker to ignore it.)

            Anyone who thinks he has a better idea of what's good for people than people do is a swine. - P.J. O'Rourke

            P 1 Reply Last reply
            0
            • J Joe Woodbury

              prasad_som wrote:

              Does this mean, issue does exist , but they are not going to fix it.

              It means, they aren't going to change how it works so your memory leak detector doesn't generate a false report. (I have a class that use to do this once with BoundsChecker--it may still do it, but haven't run it through BC in a long while. I had to just tell BoundsChecker to ignore it.)

              Anyone who thinks he has a better idea of what's good for people than people do is a swine. - P.J. O'Rourke

              P Offline
              P Offline
              prasad_som
              wrote on last edited by
              #6

              Does this mean, memory leak detector tool is generating false report ? I thought, it is somewhere related to this[^] KB article.

              Prasad Notifier using ATL | Operator new[],delete[][^]

              J 1 Reply Last reply
              0
              • P prasad_som

                Does this mean, memory leak detector tool is generating false report ? I thought, it is somewhere related to this[^] KB article.

                Prasad Notifier using ATL | Operator new[],delete[][^]

                J Offline
                J Offline
                Joe Woodbury
                wrote on last edited by
                #7

                prasad_som wrote:

                Does this mean, memory leak detector tool is generating false report?

                Hard to say. A more sophisticated tool may establish that. It's also possible there is a one time leak, which should still be fixed, but which isn't a big concern.

                Anyone who thinks he has a better idea of what's good for people than people do is a swine. - P.J. O'Rourke

                1 Reply Last reply
                0
                • P prasad_som

                  I'm amused/confused by microsoft's reply. Really cant understand resolved(won't fix).

                  Prasad Notifier using ATL | Operator new[],delete[][^]

                  P Offline
                  P Offline
                  peterchen
                  wrote on last edited by
                  #8

                  I guess your case is to weak to be considered a bug. At least, you would have to proof that it's not a bug in the validator itself. [edit] typical bug tracking options are "By design", "Not reproducible", and "Won't fix". None of these clearly fits your scenario. [/edit]


                  Developers, Developers, Developers, Developers, Developers, Developers, Velopers, Develprs, Developers!
                  We are a big screwed up dysfunctional psychotic happy family - some more screwed up, others more happy, but everybody's psychotic joint venture definition of CP
                  Linkify!|Fold With Us!

                  P 1 Reply Last reply
                  0
                  • P peterchen

                    I guess your case is to weak to be considered a bug. At least, you would have to proof that it's not a bug in the validator itself. [edit] typical bug tracking options are "By design", "Not reproducible", and "Won't fix". None of these clearly fits your scenario. [/edit]


                    Developers, Developers, Developers, Developers, Developers, Developers, Velopers, Develprs, Developers!
                    We are a big screwed up dysfunctional psychotic happy family - some more screwed up, others more happy, but everybody's psychotic joint venture definition of CP
                    Linkify!|Fold With Us!

                    P Offline
                    P Offline
                    prasad_som
                    wrote on last edited by
                    #9

                    Browsing though CP, come across similar[^] issue, but it's long back. Just in case you have not noticed, MS today added one more comment to reported issue(have a look at link provided in OP), and marked issue as Close(won't fix). :)

                    Prasad Notifier using ATL | Operator new[],delete[][^]

                    1 Reply Last reply
                    0
                    Reply
                    • Reply as topic
                    Log in to reply
                    • Oldest to Newest
                    • Newest to Oldest
                    • Most Votes


                    • Login

                    • Don't have an account? Register

                    • Login or register to search.
                    • First post
                      Last post
                    0
                    • Categories
                    • Recent
                    • Tags
                    • Popular
                    • World
                    • Users
                    • Groups