Developer forums (C::B DEVELOPMENT STRICTLY!) > Development
HUGE MEMORY LEAK pinpointed!
mandrav:
I will have a look at this today.
Patch applied, thanks dmoore.
thomas:
--- Quote from: mandrav on June 25, 2007, 01:21:45 pm ---I will have a look at this today.
Patch applied, thanks dmoore.
--- End quote ---
Something is not good with that, I think... I am getting access violations at startup from within BackgroundThread::Entry with r4170 now, but only if CC is enabled, and if I had a project open when closing Code::Blocks in the previous session.
I'm not sure what it is (something being deleted too early?), but it's strange, and it didn't happen before... :(
Der Meister:
Really strange as the code from the patch doesn't delete anything. It just does not create FileLoader instances in some situations.
dmoore:
the patch doesn't change the placement of any deletes. the only way this patch could be directly responsible is if (a) the loader pointer is being acessed when NULL or (b) the Tokenizer class expects to find a loader for a given file, but it hasn't been instantiated because of the new placement of the Load call, causing unexpected behavior. Trawling through the only other places the loader is accessed: ParserThread::InitTokenizer, Tokenizer::Init, Tokenizer::Read, and ParserThread::~ParserThread, I don't think this is the case.
there has been lots of other CC activity...
dmoore:
Der Meister: do you have the same problem with the patch (without other recent CC changes)?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version