Re: [Interest] Memory Leak when instantiating QWidget based windows

On Thursday, 8 September 2016 17:16:27 WEST Mike Jackson wrote: > Does QtCreator come with suppression files for Qt5? I ran valgrind "by > hand" on the command line and while I was able to actually find some of > our leaks (yeah Valgrind..) I had to wade through 20,000 Qt leaks to > find my leaks.

Re: [Interest] Memory Leak when instantiating QWidget based windows

(Must be something wrong with the mail system - received this 2 days later...) I'm not sure if there's a suppression file in there, but with Qt Creator I only get a handful of leaks at the end of my run that don't look like they are related to my code. Looks like something related to

Re: [Interest] Memory Leak when instantiating QWidget based windows

Den 08-09-2016 kl. 12:55 skrev Konstantin Shegunov: On Wed, Sep 7, 2016 at 11:23 PM, Mike Jackson > wrote: We monitor the memory use before and after the loop using OS X's Activity monitor. At the end of the loop there is more

Re: [Interest] Memory Leak when instantiating QWidget based windows

Does QtCreator come with suppression files for Qt5? I ran valgrind "by hand" on the command line and while I was able to actually find some of our leaks (yeah Valgrind..) I had to wade through 20,000 Qt leaks to find my leaks. Would be nice to filter those out somehow. -- Michael A. Jackson

Re: [Interest] Memory Leak when instantiating QWidget based windows

I too am using valgrind-3.11.0 (on Mac OS X 10.10.5), but I've never seen that in the Application Output window. I don't usually look there when using Memcheck. Is there anything at all in the Memcheck panel? Sometimes if your application crashes when using valgrind there is useful info there.

Re: [Interest] Memory Leak when instantiating QWidget based windows

On Sep 8, 2016, at 8:18 AM, Andy > wrote: Ah - sorry. I can see how that's unclear (pre-coffee email). I meant the Debug section on the left-hand side of the main window: Welcome, Edit, Design, Debug,... >0Then the bottom pane pops up below

Re: [Interest] Memory Leak when instantiating QWidget based windows

Ah - sorry. I can see how that's unclear (pre-coffee email). I meant the Debug section on the left-hand side of the main window: Welcome, Edit, Design, Debug,... Then the bottom pane pops up below the editor and has a dropdown at the top-left - Debugger, Clang Static Analyzer, Memcheck,... ---

Re: [Interest] Memory Leak when instantiating QWidget based windows

Hi Andy, Could you please elaborate on step #3? I cannot find a Memcheck option under Preferences > Debugger. Thanks for the tips! -Ed Qt Creator 4.01 with Qt 5.6.1 On Sep 8, 2016, at 7:56 AM, Andy > wrote: Mike: If you haven't already tried

Re: [Interest] Memory Leak when instantiating QWidget based windows

Mike: If you haven't already tried it, using Qt Creator in combination with valgrind works really well to track these kinds of things down. The basics: 1) install valgrind (I used homebrew) 2) point Qt Creator at it in the prefs (Analyzer->Valgrind) 3) Click the Debug tab, set the tool to

Re: [Interest] Memory Leak when instantiating QWidget based windows

On 09/07/2016 04:23 PM, Mike Jackson wrote: We are attempting to track down a memory leak that we _think_ we have. We have reduced our code to the point where all we do is invoke a new QWidget instance, show() it, hide() it and then delete it. We do this in a loop 100 times. We monitor the

Re: [Interest] Memory Leak when instantiating QWidget based windows

On Wed, Sep 7, 2016 at 11:23 PM, Mike Jackson wrote: > We monitor the memory use before and after the loop using OS X's Activity > monitor. At the end of the loop there is more memory being used than before > the loop, by about 2~3MB worth. > This isn't reliable.

[Interest] Memory Leak when instantiating QWidget based windows

We are attempting to track down a memory leak that we _think_ we have. We have reduced our code to the point where all we do is invoke a new QWidget instance, show() it, hide() it and then delete it. We do this in a loop 100 times. We monitor the memory use before and after the loop using OS