Jump to content

  • Log In with Google      Sign In   
  • Create Account


#ActualNightCreature83

Posted 31 July 2013 - 04:35 PM

Yeah as I posted the code here I thought wouldn't a vector cause some cleaner code as well so I tried that with no luck, instead of the new I do a reserve and when that is done in the same call as before it messes the vector up dramatically, the capacity and size members go to large numbers sadly, with the size being bigger then the capacity so something is seriously going wrong here.

 

The memory handling here isn't the issue, the issues is that the code changes a value that is on the stack from code that shouldn't touch that variable at all. The code that is generated for this call is some how just wrong.


#2NightCreature83

Posted 31 July 2013 - 04:32 PM

Yeah as I posted the code here I thought wouldn't a vector cause some cleaner code as well so I tried that with no luck, instead of the new I do a reserve and when that is done in the same call as before it messes the vector up dramatically, the capacity and size members go to large numbers sadly.

 

The memory handling here isn't the issue, the issues is that the code changes a value that is on the stack from code that shouldn't touch that variable at all. The code that is generated for this call is some how just wrong.


#1NightCreature83

Posted 31 July 2013 - 04:30 PM

Yeah as I posted the code here I thought wouldn't a vector cause some cleaner code as well so I tried that with no luck, instead of the new I do a reserve and when that is done in the same call as before it messes the vector up dramatically, the capacity and size members go to large numbers sadly.


PARTNERS