Jump to content

  • Log In with Google      Sign In   
  • Create Account

We're offering banner ads on our site from just $5!

1. Details HERE. 2. GDNet+ Subscriptions HERE. 3. Ad upload HERE.


#ActualKhatharr

Posted 26 January 2013 - 02:31 AM

All you've told us about is the problem itself. Without more context we have no way of knowing what's causing it.

 

If the code is indeed not being run then obviously it's not directly leaking memory, but it may be something else in that compilation unit that's screwing up the heap and removing that line simply hides the problem.


#1Khatharr

Posted 26 January 2013 - 02:27 AM

All you've told us about is the problem itself. Without more context we have no way of knowing what's causing it.


PARTNERS