Re: [hlcoders] memory leak

2006-10-31 Thread Nick
how big is the leak? On 11/1/06, Oliver <[EMAIL PROTECTED]> wrote: -- [ Picked text/plain from multipart/alternative ] We've got a memory leak in our code somewhere. I've looked through the wiki articles on memory leaks and haven't been able to fix it. Does anyone know a memory manager viewer

Re: [hlcoders] memory leak

2006-10-31 Thread Nick Darnell
-- [ Picked text/plain from multipart/alternative ] Big :) That's one of the problems. We know there is a leak, but we are unsure just how big we are talking. Which is why we are interested in hearing what programs, libraries some of you may use to debug, detect these things. -Nick On 10/31/06

Re: [hlcoders] memory leak

2006-10-31 Thread Heimo Stieg
maybe this tool will help you http://www.codeproject.com/cpp/MemoryHooks.asp Nick Darnell schrieb: -- [ Picked text/plain from multipart/alternative ] Big :) That's one of the problems. We know there is a leak, but we are unsure just how big we are talking. Which is why we are interested in

Re: [hlcoders] memory leak

2006-10-31 Thread Adam "amckern" Mckern
Grab a code coverage tool profiler like perforce or the shader profiler (that also has leek support) from nvidia (it will bitch about no support in the engine, but will show leeks in the output log). http://www.google.com/search?lr=&ie=UTF-8&oe=UTF-8&q=Code%20coverage%20tools http://developer.nvid

RE: [hlcoders] memory leak

2006-10-31 Thread Ben Everett
BoundsChecker, but it isn't cheap. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Nick Darnell Sent: Tuesday, October 31, 2006 4:57 PM To: hlcoders@list.valvesoftware.com Subject: Re: [hlcoders] memory leak -- [ Picked text/plain from mult

RE: [hlcoders] memory leak

2006-10-31 Thread bloodykenny
6 4:57 PM >To: hlcoders@list.valvesoftware.com >Subject: Re: [hlcoders] memory leak > >-- >[ Picked text/plain from multipart/alternative ] >Big :) That's one of the problems. We know there is a leak, but we are >unsure just how big we are talking. Which is why we are interested in >hea

Re: [hlcoders] memory leak

2006-10-31 Thread Nick Darnell
cker, but it isn't cheap. > > > >-Original Message- > >From: [EMAIL PROTECTED] > >[mailto:[EMAIL PROTECTED] On Behalf Of Nick Darnell > >Sent: Tuesday, October 31, 2006 4:57 PM > >To: hlcoders@list.valvesoftware.com > >Subject: Re: [hlcoders] memory leak > >

Re: [hlcoders] memory leak

2006-11-01 Thread Nick
ap. (Free.) > > At 2006/10/31 07:52 PM, Ben Everett wrote: > >BoundsChecker, but it isn't cheap. > > > >-Original Message- > >From: [EMAIL PROTECTED] > >[mailto:[EMAIL PROTECTED] On Behalf Of Nick Darnell > >Sent: Tuesday, October 31, 2006 4:57 PM

Re: [hlcoders] memory leak

2006-11-01 Thread Nick Darnell
AIL PROTECTED] > > > >[mailto:[EMAIL PROTECTED] On Behalf Of Nick > Darnell > > > >Sent: Tuesday, October 31, 2006 4:57 PM > > > >To: hlcoders@list.valvesoftware.com > > > >Subject: Re: [hlcoders] memory leak > > > > > > >

Re: [hlcoders] Memory Leak - Long debug txt!!!

2002-04-26 Thread David Sassen
question: Does "{2492} normal block at 0x054A6FD8, 264 bytes long. Data: < A7 say_team mov> 10 41 37 05 73 61 79 5F 74 65 61 6D 20 6D 6F 76" come up every time you say something to your team? These look like part of the networking protocol, is it possible that you're misdeclaring the lengths of o

Re: [hlcoders] Memory Leak - Long debug txt!!!

2002-04-26 Thread Jeff Fearn
> question: Does "{2492} normal block at 0x054A6FD8, 264 > bytes long. > Data: < A7 say_team mov> 10 41 37 05 73 61 79 5F 74 > 65 61 6D 20 6D 6F > 76" come up every time you say something to your team? > These look like part of the networking protocol, is it > possible that you're misdeclaring th