On a hunch I disabled the todo plug-in (in the src/plugins/plugins.pro file), and found qtcreator doesn't show signs of a memory leak anymore. This meets my current needs, though the plugin sounds handy (I think there are hundreds of todo comments in our codebase that nobody is looking at)
I tried running in valgrind, but on my 32-bit system and project there isn't enough memory to do more than start and exit qt creator before valgrind runs out of memory. (I thought I found a work around, but the power went off, and given the speed of valgrind I don't want to try again). -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of André Pönitz Sent: Tuesday, May 08, 2012 5:18 PM To: Miller Henry Cc: [email protected] Subject: Re: [Qt-creator] possible leak in 2.5 rc with parsing after cmake? On Tue, May 08, 2012 at 02:36:58PM -0500, Miller Henry wrote: > I’ve been running 2.5 rc for a while, and have noticed that memory usage often > climbs – after a day or two top shows qtcreator is using around 1700M of > virtual memory, compared to around 450 when I first load my project. (I know > this isn’t accurate, but it is easy and shows a trend). I see memory jumps > everytime I run cmake right around the time the parse phase starts. > > This might not be a leak, but memory refereced that shouldn’t be: when qt > creator is in the consumes a lot of memory state it takes a lot longer to quit > than if I start do a few things and then quit. > > This did not happen with the beta, but I lack time to go back and figure out > where it started. Just running Creator under valgrind might give some insight. Andre' _______________________________________________ Qt-creator mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/qt-creator
