Difference between revisions of "Talk:Chadius: SwordDraw"
(One intermediate revision by one other user not shown) | |||
Line 8: | Line 8: | ||
For the record...25 victories, and 63 max damage! Haha. I want a "max damage" display like it keeps track of victories, because I don't always see the damage before it flashes off. :) | For the record...25 victories, and 63 max damage! Haha. I want a "max damage" display like it keeps track of victories, because I don't always see the damage before it flashes off. :) | ||
--[[User:Ratri|Ratri]] 12:22, 18 Dec 2005 (CST) | --[[User:Ratri|Ratri]] 12:22, 18 Dec 2005 (CST) | ||
+ | |||
+ | Oops...it was a 750K memory leak! | ||
+ | |||
+ | I sat down for a good 2 hours this morning and fixed all the leaks valgrind told me. Chris and I did some testing with other profiler tools, and it looks like I took care of the leaks. | ||
+ | |||
+ | Sorry I didn't notice them before...Linux and Mac don't have memory leak issues...unlike other OSes XD | ||
+ | |||
+ | --[[User:Chadius|Chadius]] 20:52, 18 Dec 2005 (CST) | ||
+ | |||
+ | Nice. So I can grab a new version and try to break it again now? :) | ||
+ | |||
+ | I think I've totally found a new still-awake-at-half-past-midnight toy. | ||
+ | --[[User:Ratri|Ratri]] 09:16, 19 Dec 2005 (CST) |
Latest revision as of 10:16, 19 December 2005
Too funny -- I like the monster names. However, about halfway through the third game I play without relaunching, I get Windows telling me it's out of virtual memory. Win2000 (SP 4), I think with 128 meg RAM. Might just be another wonder of my magical craptop though... --Ratri 00:38, 18 Dec 2005 (CST)
It's not just you. Version 007 is leaking like a fire hose. I plugged the worst ones on my copy, but there are several which would take me a while to fix. I'll work With Chadius on it later. --Nybble 03:44, 18 Dec 2005 (CST)
Zing. Flexing my l33t breaking-people's-code skills at work and at home! For the record...25 victories, and 63 max damage! Haha. I want a "max damage" display like it keeps track of victories, because I don't always see the damage before it flashes off. :) --Ratri 12:22, 18 Dec 2005 (CST)
Oops...it was a 750K memory leak!
I sat down for a good 2 hours this morning and fixed all the leaks valgrind told me. Chris and I did some testing with other profiler tools, and it looks like I took care of the leaks.
Sorry I didn't notice them before...Linux and Mac don't have memory leak issues...unlike other OSes XD
--Chadius 20:52, 18 Dec 2005 (CST)
Nice. So I can grab a new version and try to break it again now? :)
I think I've totally found a new still-awake-at-half-past-midnight toy. --Ratri 09:16, 19 Dec 2005 (CST)