Tom Ramcigam (magicmarmot) wrote,
Tom Ramcigam

Oh for fun.
Working on a bug in this program. There is a huge memory leak in one particular portion, and I've managed to trace the memory leak to a particular element. You see, the debugger keeps track of the individually allocated chunks that are lost, and the vast majority of them are chunks that are 6750000 bytes long.
The function that is supposed to handle the releasing of these blocks is returning an error code, and the error code does not correspond to any error code that they have listed.

The monkey, she dances.

  • (no subject)

    It finally happened. It had to, really. I was in the bottom two cut from LJ-Idol this week. I made it to the top 50, from some rather larger…

  • Mayville

    "Too many bats in the belfry, eh?" The question came from a small man in the scrubs-and-robe garb of an inmate. He looked a little like a garden…

  • LJ-Idol

    Another batch of entries. Consistently amazed at how good the writing is. Voting is open for…

  • Post a new comment


    default userpic

    Your reply will be screened

    Your IP address will be recorded 

    When you submit the form an invisible reCAPTCHA check will be performed.
    You must follow the Privacy Policy and Google Terms of use.