fred_temento
Occasional Contributor
Joined 9 years ago
User Profile
User Widgets
Contributions
Re: Monitor panel is empty
Yes I read the doc ! and zoom in/out only works on the displayed area so within the "monitored interval". only solution I found is to increase the monitored interval. which is not a good idea when profiling a large cycle. the second doc (I also read !) do not talk about Monitor panel... It seems that the monitor values are not saved (only runtime)... anyway thank you for answering !6.2KViews0likes0CommentsRe: Monitor panel is empty
thanks Alex Your first hint was the good one ! Do you know if it is possible to add horizontal scroller to the monitor view (graph) in order to see the whole data(and not only the bufferized ones) ? or maybe log all data to a file (in order to recreate it with xl) ? thanks in advance !6.2KViews0likes2CommentsMonitor panel is empty
Hi all, I don't know why (surely I did something wrong with an unwanted drag'n'drop), my monitor panel is an empty window... no graph, no grid, no contextual menu to edit data... (see attached) I can't find how to add new monitor grid or graph inner control without the contextual menu... ...need a little help from my friends...! thanksSolved6.2KViews0likes4CommentsRe: Do not see fake memory leak in a DLL
Hi Alex, Thanks for all your comments. I did follow the recommandation for building native c++ projects : I had to change my 52 projects of my application since an option was disabled and AQtime needs it (Function Level Linking). This was a great think since it generates a lot of link errors that were real errors (indeed I don't undestand how the code was working before !). I must say that my application was last converted from VC6 to VS2013 ! So the project file settings were automatically translated from VC6 to VS2013 (+ some manual action)... and those both compilers are REALLY different ! So switch FLL ON was a good thing ! I also set all my project to use /Zi (since all my project can not use /ZI because of /SEshc settings) I verified and setup the directory to use PDB files (indeed it was good, only vc120.pdb was missing) I studied your screen shot (that was helpfull regarding the small button !) I verified the "Project Search Drectories" for source picking. and I can see the same results as yours. I don't understand why it is mandatory to create a "class level area" since, by definition, we don't know where are memory leaks ! but I created it and put the DLL into which I create a memory leak (malloc without free). Finally I can see the same results as yours + source file and line number ! (see attached) BUT still no source code can be viewed when double click on a Call tree CTSString line item.... (no more error message saying that there are no source code available or no debug info) So, I must really thank you all the time you spent for me. I think there is something abnormal in my application solution that do not please AQTime. I will know try with a dummy "hello world" like native C++ MFC application build from scratch using the VS2013 wizard and see if the results a re more accurate. and finally open a support ticket ! Once again, many thanks to you ! oops : last minute ! I just saw that the line number of leak is really innacurate since it do not point on the malloc but on the ctor opening brace... at line 42 (see attached) very last minute ! Finally after trying on another mushc smaller app, reading more help, clicking everywhere..; I finally found what I am looking for days : The "Classes Data" view is not the better place to find leaking code but just if there are leak The "Objects" view is better ! Associated with the Details view, Creation Call Stack pane, allow to double-click on a symbol and see the source code ... BUT this must be used with the "View project class only" button DISABLED ! (so thanks for that !). So now I find my dummy leak (see attached). My point of view is that having memory leak information is not a straight forward process ! To much information makes real information noisy. (I was thinking that purrify was too verbose... but AQTime is much more graphically noisy!). Also the "Object Name" column that list "C++ native memory.xxxx" is not really helpful. I think that a simplified unique view can be done in order to directly point on the memory leak. Now I can refine my question: - What is the aim of the magic button "View project class only" ?? It seems strange to disable it in order to see the leak of the class of my project! Is project meaning only the executable ?? why my DLL behing part of my project is not considered as included in my project ?? Anyway, I set this post as Answered. Thanks again Alex.13KViews0likes1CommentRe: Do not see fake memory leak in a DLL
Thanks for your help. First, I wanted to tell you that I thought you were a support staff guy from Smartbear ! I just realized that I was wrong ! So sorry for asking you to solve my issues ! I will surely redirect my message to the support staff since there is something strange in the beahvior of AQTime with my code. Thanks for the link to setup VS2013 (I did not find it before). But I agree with you that the SmartBear documentation is one of the best of the world ! So regarding the fact that you are not a c++ expert : what you say about debug/release build is true and I know that (I am very familiar with c++ maybe an expert !). Except that debug code contains "NO" optimization at all. So I don't understand why the article you sent me tells to use a Release build to add debug info in it since it will be still optimized (unless you disable it by /Od) >So, your code was compiled as debug one (...) but did not have associated debug info. Since all my project can be debugged with VS2013 and all settings are set on all modules... I don't know how it's possible Anyway I checked once again that all settings are compliant with AQTime. Except the "Enable Function-Level Linking option" it was OK. Unfortunatly this option makes my code no more link. I am investigating. So I can understand that because there are explaining how to profil for performance. Indeed profiling for performance should included compiler optimization but not profiling for memory. AQtime is the only soft I use for memory leak hunting that behave like this regarding memory management. I never had any issue with boundchecker or purify to hunt for memory leak with my debug builds... Anyway thanks to the article you sent me I think that I have a possible solution to solve my issue (what you call Debug build with debug info). My build sperates bianries from pdb files. So maybe AQTime needs PDB files to consider it is debug build... I will tell you (and the community) if it solves my issue when I will succeed to solve the Enable Function-Level Linking issue. Thanks for your help.13KViews0likes3CommentsRe: Do not see fake memory leak in a DLL
Thanks for your reply. What you say is realy confusing me ! First you say that you need to download the DEBUG redistributable of VS2013 (sorry for not shipped it; I thought you had them installed since Memory profiling DO needs debug builds) So this mean that my binaries do need debug version of MFC and CRT libraries. Right ? and after you say that ALL my binaries has NO DEBUG INFO ! I can say that VS2013 is able to debug all my binaries ! so I think all my binaries is build with debug info. I just verify that the size of TSFC.DLL is really different between debug and release build : 283K for debug version and 57K for release version. (and I double check that this is the 283K version that I sent you !) Do you know a way to guess if a DLL is a debug or release build ? Anyway, there are many compiler option to build a debug version. And unfortunatly I did not find the settings to put on my vcxproh VS2013 project to suit the AQtime needs. I only find delphy ones... that do not help me. I think the issue is there : What are the debug compiler flag/option to use in Visual Studio 2013, to be compliant with AQTime ? I did not know about the diatem3.6_Results directory ! but I can't send it because it is too large : " The attachment diatem3.6_Results.7z is too large and has been removed. The maximum file size is: 20,000,000 bytes." Thanks a lot for your feedback.13KViews0likes5CommentsRe: Do not see fake memory leak in a DLL
Hi Alex, thanks for your feed back. >Have you added this dll to the list of project modules to be profiled? of course ! I did it manually on my standalone AQtime project and it was done automatically by the intergrated version. So, I think it's done ! >Can you attach here your AQtime project (and .exe and .dll) ? I zip it... I suppose that an AQTime project is only made of the *.aqt file ! For information the fake memory leak is in the TSFC.dll module, TSString.cpp file, CTSString class default ctor which is called many times (I check with a breakpoint in debug mode) Here is the code: CTSString::CTSString () { m_Size = 0; m_BufferSize = STARTING_BUFFER_SIZE; m_pBuffer = NULL; SetNeededBufferSize (false); m_pBuffer[0] = 0; char * p = (char *)malloc(10); // p is never free to check for ML } You will see, with Windbg, that the MSVCRT embeded memory check, see my fake memory leak (but without reporting line information) Detected memory leaks! Dumping objects -> {650} normal block at 0x006FE5D8, 10 bytes long. Data: < > CD CD CD CD CD CD CD CD CD CD You'll find attached a 7Z file containing my AQTime (standalone version) projet and minimal subset version of my exe with it's DLL as requested. (I cannot use ZIP since the ZIP file is more than your limit of 20,000,000 bytes !) Running Diatem.exe stops at checking licence time but it's not an issue since the CTSString default ctor is called a lot of time before this. So it's enought for test prupose. Thanks for your help.13KViews0likes7CommentsDo not see fake memory leak in a DLL
Hello, I am new to AQtime. In order to understand how AQtime show memory leak (that i can understand) I decide to create a fake memory leak in a DLL of my exe : just a malloc(10) without free in a ctor of a call being instanciated ton of time. When I quit my application... a ton of memory leak appears (not my code!) but not mine ! Furthermore, I did not find tuto or sample for pure C++ (not managed) memory profiling. So I peak information on some tuto talking about delphi or C++ .net... I did try with AQtime standalone and integrated in Visual Studio 2013. can you help on why my fake memory leak is not find ?Solved13KViews0likes9Comments