TestStand 3.1 Report Memory Leak

Hi everyone,
I been looking at the memory usage of my TestStand code lately.  I noticed I have a memory leak with On The Fly Reporting using XML report file.  I'm currenlty using labview 7.1.1 and TestStand 3.1f for development.   I came about this program from seeing test station go to a snails crawl.  The program starts out around 100MB and will keep growing using up all the systems memory, the largest I seen was 500MB.   What is happening is the testers like to keep the on the fly report screen up during the test  and not view the execusion window.  At the end of each run the program will grow 10MB to 30MB.    I know the problem can be solved by turning off on the fly reporting, but I would like to try find a programing option first.
I have looked at the other forum entries about:
Turning off database collection
Editing  model options : ModelOptions.DiscardUnusedResults = True and Parameters.ModelOptions.NumTestSockets = 1
Adjusted the array size of the report to 300
None of the options seem to have worked for me, most the post say move to teststand 3.1 cause it an 3.0 issue.
I was wondering if there are any other options to try  in teststand, or any way to turn off/close IE to release memory between tests.
I'm currently running the code on Windows XP SP2 
IE6/IE7 depending on the test station
P4 or Centrino  with 512MB to 1GB of ram
The GUI window is a modifed  example of the basic VI EXE that calls teststand
The code is installed using labview and Teststand  deployment builders, so the test machine are using runtime labview 7.1.1  and runtime TestStand 3.1
Thanks to any one who can offer alittle extra help on the topic

Actually the reports are XML not HTML.
There are alot of pass steps, usualy after a couple of failed steps, the sequence will terminate.
The memory leak seem to exaggerated, since the technicians like to view the Reports Tab instead of Execution Tab when running program.  If the operator keeps the view on the execution tab during the program, the report screen is not being updated, so less memory is taken up.  Since the techs like to keep the report screen up during the entire test, the xml file constantly being update and  the program increases +50MB after the first run.   So turning off Reports on the fly, they can not view the report during the test and the memory usuage stays low.
I do not see a leak at all if I do not click on the reports tab,  and the leak seems to only happen with XML files, TXT and HTML reports do not cause a memory leak, even when viewed on the fly for the entire test.   I wanted to keep XML-expandable cause it easier to see what sequences failed then scanning through the entire report.
I'm using Test UUT call up the test.    The executable terminated if you press the exit button on the executable.  After test is finished, the standard Pass/Fail comes up then the standard  enter UUT serial number comes up.
I'm including the reports option INI  I use .
Thanks for you help in this matter, sorry being little late with replying. 
Attachments:
report.ini ‏4 KB

Similar Messages

  • Memory Leak Issue With Win7 64 bit and Youtube.

    I have a Win7 64 bit using IE9 with version 11.4.402.265 installed. 4 MB installed.
    Whenever I go to Youtube or Liveleak, and watch videos, over time it uses up to 4gigs of my memory! Even if I close the window, it does not free up the memory until I Ctrl/Alt/Delete and shut down the window(s).
    I normally only keep open 1-2 windows. Google toolbar is about the only thing installed. I can open 5 and more tabs, but as long as the site does not use flash, I don't have issues and each window usually uses under 200k memory watching them in task manager.
    When I go to open and watch a youtube video, it slowly climbs to 200k and within an hour, I can be at 2 gigs or more memory and up to 4 gigs within 2 hours (or sometimes much sooner). Closing the window does not release the memory until I end task on it and then after a minute or so, the memory seems to clear and everything is back to normal.
    I searched the forums and seems lots of users, report memory leaks, some using yahoo toolbar installed, which is not my case. I do use yahoo as my e-mail address, no idea if that is related or not. I had the same issue when I had the prior Flash version installed, this has been going on for months. Right now having only this window open, using 129, 192 memory. If I open one more window (using the 64 or 32 bit browser) and start youtube, the memory in that window keeps climbing about 50-100kb a second, so it adds up quickly. I have kaspersky running in the background and that is about it other then my nvida driver setup.
    Really frustrating that so many people here and across the internet have reported this. I did have IE8 a few weeks ago and still had the same issue, upgraded to IE9 to see if that helped.
    Interesting side note, if I pause a video, it slows way down on the memory leak, but still rises at a slower pace. I don't know if this is an IE thing or Flash. I have had this setup since 2009 and don't recall having issues with IE7. I use Youtube so much as a teaching instrument as a music teacher, so constantly have lessons going on it.
    Thanks and hope someone has come up with something. I also build computers and have done some programming, so I could modify a file if needed with clear instructions.

    This could be similar to bug https://bugbase.adobe.com/index.cfm?event=bug&id=3334814

  • Memory leaks in C++(OCCI ) for OTT generated C++ mapping objects with Oracl

    Our application is in C++ which interfaces with Oracle 10g database using OCCI. The mapping objects are created using OTT. The type of these mappisng objects in PersistentObject. Our development machine(Solaris 8) and database machine are different. So we have installed the "instantclient-basiclite-solaris6432-10.2.0.3-20070101.zip" to use OTT and OCCI on development machine. We are running purify in our application, Purify is reporting memory leaks on these OTT generated POObjects (type used is transient Objects), despite the fact that we are deleting these objects appropriately. .

    Since OTT generated code uses the STL data structures vector list etc.
    STL are not standard across platforms and hence you can ignore these warnings.

  • Teststand 3.5 Memory Leak Strategies

    I am experiencing a memory leak when running my test seqeunce using TestStand 3.5.  I have read several messages and Knowledgebase entries to try and collect intelligent memory leak strategies.  I have been running Perfmon on my Windows XP PXI controller card to collect data on the Private Bytes for the process SeqEdit.  This shows a memory increase with each test cycle of over 500 KBytes.  I am trying to reduce my huge test sequence file down to determine where the leaks are occuring, but have the following questions in order to more fully understand TestStand memory issues:
    1) I understand each individual step in a sequence can record results if not disabled.  So, if there are thousands of individual steps this could take up quite a lot of memory.  Does TestStand allocate new memory for these step results, or do the results get stored into memory already allocated for TestStand when it is invoked?  By the way, I debug the memory leak issues with reporting disabled.
    2) If the step results are stored in newly allocated memory, at what point does TestStand free up the additional memory it allocated for the step results?  Is it inside the process model?
    3) Is there a way in the sequence editor to turn off Record Results for multiple steps at once, or must they all be turned off individually (soooo time consuming!).
    4) If memory is newly allocated, is there a step I can execute to force memory to be freed up?
    Ideally, I should be able to start at a certain memory level, execute one test cycle (which has many memory allocations and de-allocations), and at the start of the second test cycle be at the same memory level that was present at the start of the first test cycle.  I actually focus my attention on the second test cycle vs. the third, fourth, ... since the first test cycle can load DLLs for the first time and will affect memory size.
    Any information on the above questions will be greatly appreciated.
    Ron

    Ron,
    What I meant by "default" was just when report generation is turned on and On-The-Fly Reporting is off. The memory used by the results array is released once the scope of the results is lost. In other words, when your sequence is done and ends, the memory is freed. When you use Test UUTs instead of Single Pass, the memory is not freed until the testing is "stopped" instead of choosing to test the next UUT. This does not mean that more and more memory is used for each pass. If you look at the process model for Test UUTs entry point, there are a few steps that clear the results container. That means the memory is still allocated, it just gets cleared and replaced with the new results.
    You keep referring to this as a "memory leak" when it actually is more along the lines of just getting more and more values to be stored into memory instead of a "leak." Something you might check to see is if you are storing numbers in huge arrays, which will also take large chunks of memory. You shouldn't be seeing a memory problem with just a couple thousand steps. I have seen sequence files with over 10,000 steps run before. One other thing you might consider is if you use On-The-Fly Reporting, you will see a slow of execution time.

  • Memory Leak in Report after upgrading from Crystal Reports 10.5 to 13.0.1/2

    I'm currently having an issue with crystal reports 13 (Visual Studio 2010), We have recently updated our CRM Solution to use the newer crystal reports runtime as we are now using Visual Studio 2010,
    We have a client who has a report which contains a sub report which basically contains a Image pulled from a MSSQL Database as a BLOB Image Field which is basically scanned images relating to the report, Previously the report worked fine before the Client Updated our CRM Solution to the latest version, Now for each individual page which has the scanned image the application is swallowing 100 MB of ram, as there are around 32 of these scanned images and our solution is a 32 bit application we are getting out of memory errors due to the whole 2GB addressable to a 32 bit process limitation,
    The images are around 4MP and stored in JPG format in the database so should not be consuming over 100mb of ram per image displayed by the report even if they are being stored uncompressed in RGBA Format,
    Likewise when viewing the pages of the report manually after a specific page (when the amount of memory addressable by a 32 bit application gets hit) the images just don't display and then any pages with the image are not being displayed and not giving an error / exception.
    I have tried re-saving the .rpt files to cause them to be in the newer crystal reports format and this is still happening, likewise I have tried un-installing the 13.0.1 and installing the 13.0.2 runtime.
    I am just about to check SQL which pulls the image for the sub report, although I am sure for each sub report it should only be pulling one row with one jpeg image in case the sub report is holding quite a few images but only displaying the first.
    Likewise If all else fails I will try re-creating the report as I have experienced issues with some other specific reports doing strange things after being updated from the 2008 runtime which I really am not liking the idea of due to how fiddly crystal reports can be, It is good and does the job but takes far longer than some other solutions to get what you are trying to achieve done.
    This report had been working fine for 2+ years before the client updated to the most recent version of our CRM Software.
    Has anyone else experienced simular issues with the latest runtime.

    I have just been reviewing the code for this and it appears that the sub report is pulling all of the images,
    It is strange that previously this was working fine seems like the newer runtime does not dispose of the data once it has been displayed on a sub report which would explain memory leak as it will call the select again pulling approx 60 images which are probably approx 8 - 900KB plus sub report + uncompressed image to display and then filtering.
    I am about to modify this report and will post if fix i put in place resolves the issue.

  • Memory leak in Crystal Reports 2008

    We are running CR runtime 2008 version 12.3.4 and it looks like there is a memory leak. This is what we see happen (see chart#1). So just between these 4 report runs memory usage as gone up 64mb. We loose 20mb of memory with each report that we call. We actually see memory keep going up until the application fails due to out of memory issues around 1100mb of memory usage. This has been an issue ever since crystal 2008 was released we did not see this issue with Crystal Reports 11 or 10.
    chart#1:
    memory using in MB after opening and closing a small CR
    Start 123
    open rpt 225
    close rpt 204
    open rpt 245
    close rpt 226
    open rpt 266
    close rpt 247
    open rpt 287
    close rpt 268
    When is SAP going to address this issue?  Our work around for the last 2 years has been to close the CR application and reopen it multiple times a day to free up this lost memory and to revent "Out of memory" errors.  We will be forced to move to Reporting Services if this issue is not addressed soon.
    Josh

    Hi Josh,
    There are no memory leaks in CR 10, 11, 2008 or 2010 or 2011.
    Make sure you are closing and disposing all of your report objects, database connections, Data Sets etc. And then calling GC.Collect.
    And if you want to pursue this I suggest you give more details than just saying there is a leak and show a bunch of numbers that mean nothing without the code to verify those numbers.
    Thank you
    Don

  • Crystal Reports 2008 - Report Load error - Memory Leak Error?

    Hello
    <br>
    We have a problem with Crystal Reports 2008 with .NET 2.0.
    <br>
    CrystalDecisions.CrystalReports.Engine, Version=12.0.2000.0, Culture=neutral, PublicKeyToken=692fbea5521e1304
    <br>
    The problem is that during high amount of report producing, errors in eventlog pops up and the production of reports using <br>
    Crystal Reports stops.
    <br>
    Below are examples of the three most common event logs.
    <br>
    We have tried to implement a cleanup method both as a destructor (with a global ReportDocument rdoc variable) and using direct call to cleanUpDoc() method when finished with loading doc:
    <br>
    ~IOServerClass()
    <br>
    <br>
                cleanupDoc();
    <br>
    <br>
    <br>
            private void cleanupDoc()
    <br>
    <br>
                try
    <br>
    <br>
                    if (rdoc != null)
    <br>
    <br>
                        rdoc.Close();
    <br>
                        rdoc.Dispose();
    <br>
                        rdoc = null;
    <br>
    <br>
                    this.CleanGlobalEvents();
    <br>
                    System.GC.Collect();
    <br>
    <br>
    <br>
    <br>
    The doc is loading using the "normal" method (in-process).
    <br>
    <br>
    try
    <br>
    <br>
                        rdoc = new ReportDocument();
    <br>
                        rdoc.Load(fullpathandreport); 
    <br>
    <br>
                   catch (Exception ex)
    <br>
    <br>
                    cleanupDoc();
    <br>
    <br>
    ...process doc....
    <br>
    cleanupDoc();
    <br>
    <br>
    Furthermore we have tried during Scalable tests of the system - but cannot produce the below errors ourselves. Only the customer can.
    <br>
    Please help with solving this problem.
    Is the above advisable to do?
    Should the document be loaded in another way?
    Is it a memory leak?
    <br>
    Regards
    Kristian
    <br>
    <br>
    event logs:
    <br>
    <br>
    #1
    <br>
    <br>
    Event Type:     Error
    Event Category:     None
    Event ID:     1102
    Date:          12-02-2010
    Time:          10:22:05
    User:          N/A
    Description:
    IO_ServerClass.IO_ServerPrepareReportBeforeExecute() Report load Error:
    Loading reportfile=C:\Inetpub\wwwroot\xxx\Reports\321.rpt
    Source=CrystalDecisions.CrystalReports.Engine
    Message=Load report failed.
    Stacktrace=   at
    CrystalDecisions.ReportAppServer.ReportClientDocumentWrapper.EnsureDocumentIsOpened()
       at CrystalDecisions.CrystalReports.Engine.ReportDocument.Load(String filename,
    OpenReportMethod openMethod, Int16 parentJob)
       at CrystalDecisions.CrystalReports.Engine.ReportDocument.Load(String filename)
       at xxx.IOServer2.IOServerClass.IO_ServerPrepareReportBeforeExecute(String
    WebRootRelPathNameRepName, String init, Hashtable ParmsVals, Int32 JobId, Int32 JobStep,
    Page webpage) in C:\Documents and Settings\xxx\My Documents\Visual Studio 2008\Projects\xxx.IOServer2\IOServerClassClassic.cs:line 290
    InnerSource:Analysis Server
    InnerMes:
    Error in File 321 {19463E3B-D404-45EB-88AE-5722A7FF9E90}.rpt:
    The request could not be submitted for background processing.
    InnerStack:
       at
    CrystalDecisions.ReportAppServer.ClientDoc.ReportClientDocumentClass.Open(Object&
    DocumentPath, Int32 Options)
       at CrystalDecisions.ReportAppServer.ReportClientDocumentWrapper.Open(Object&
    DocumentPath, Int32 Options)
       at
    CrystalDecisions.ReportAppServer.ReportClientDocumentWrapper.EnsureDocumentIsOpened()
    <br>
    <br>
    #2
    <br>
    <br>
    IO_ServerClass.IO_ServerPrepareReportBeforeExecute() Report load Error:
    Loading reportfile=C:\Inetpub\wwwroot\xxx\Reports\321.rpt
    Source=CrystalDecisions.CrystalReports.Engine
    Message=Creating an instance of the COM
    component with CLSID {D7F5D7C3-B06C-4CAC-BC47-A06E66D2EE9B} from the IClassFactory failed
    due to the following error: 8007000e.
    Stacktrace=   at
    CrystalDecisions.ReportAppServer.ReportClientDocumentWrapper.CreateRptDoc()
       at CrystalDecisions.ReportAppServer.ReportClientDocumentWrapper..ctor()
       at CrystalDecisions.CrystalReports.Engine.ReportDocument.Initialize()
       at CrystalDecisions.CrystalReports.Engine.ReportDocument..ctor()
       at Kimik.IOServer2.IOServerClass.IO_ServerPrepareReportBeforeExecute(String
    WebRootRelPathNameRepName, String init, Hashtable ParmsVals, Int32 JobId, Int32 JobStep, Page webpage) in C:\Documents and Settings\xxx\My Documents\Visual Studio 2008\Projects\xxx.IOServer2\IOServerClassClassic.cs:line 289
    <br>
    #3
    <br>
    <br>
    IO_ServerClass.IO_ServerPrepareReportBeforeExecute() Report load Error:
    Loading reportfile=C:\Inetpub\wwwroot\xxx\reports\340.rpt
    Source=CrystalDecisions.CrystalReports.Engine
    Message=Load report failed.
    Stacktrace=   at
    CrystalDecisions.ReportAppServer.ReportClientDocumentWrapper.EnsureDocumentIsOpened()
       at CrystalDecisions.CrystalReports.Engine.ReportDocument.Load(String filename,
    OpenReportMethod openMethod, Int16 parentJob)
       at CrystalDecisions.CrystalReports.Engine.ReportDocument.Load(String filename)
       at Kimik.IOServer2.IOServerClass.IO_ServerPrepareReportBeforeExecute(String
    WebRootRelPathNameRepName, String init, Hashtable ParmsVals, Int32 JobId, Int32 JobStep,
    Page webpage) in C:\Documents and Settings\xxx\My Documents\Visual Studio 2008
    \Projects\xxx.IOServer2\IOServerClassClassic.cs:line 290
    InnerSource:CrystalDecisions.ReportAppServer.ClientDoc
    InnerMes:
    Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
    InnerStack:
    at CrystalDecisions.ReportAppServer.ClientDoc.ReportClientDocumentClass.Open(Object&
    DocumentPath, Int32 Options)
       at CrystalDecisions.ReportAppServer.ReportClientDocumentWrapper.Open(Object&
    DocumentPath, Int32 Options)
       at
    CrystalDecisions.ReportAppServer.ReportClientDocumentWrapper.EnsureDocumentIsOpened()
    Edited by: kristians on Feb 16, 2010 2:57 PM

    Hi;
    First, ensure you have the latest service pack / hot fix for your version of Crystal Reports, and that the client has the same updates as well. Fix Pack 2.4 is the current latest, and can be downloaded from our downloads section.
    One of the errors is the Background Processing error, so have a look at the following article:
    http://www.sdn.sap.com/irj/boc/index?rid=/library/uuid/50a6f5e8-8164-2b10-7ca4-b5089df76b33&overridelayout=true
    Regards,
    Jonathan
    Follow us on Twitter u2013 http://twitter.com/SAPCRNetSup

  • Memory Leak in Crystal Report XI

    We are using Crystal Reports XI Licensed Developer version for web based application. The generated reports are getting accessed by multiple users from web interface. After continuos access of reports, at some point it reaches the maximum limit of Application pool and it stops the application.
    From number of web forms, we found that crystal reports are not releasing systems memory and it keeps adding extra load on memory after a single report generation or there is memory leak. Below are the code snippets to initialize and dispose of report object.
    a. Initializing a new report obj
    protected ReportDocument _selectedRpt = new ReportDocument();
    b. Disposing obj in page_unload event
    /// <summary>
    /// Page_Unload Event handler.
    /// </summary>
    /// <param name="sender">Sending control or event.</param>
    /// <param name="e">Generic event arguments.</param>
    protected void Page_Unload(object sender, EventArgs e)
         _selectedRpt.Close();
         _selectedRpt.Dispose();
    Temporary Solution:  For its temporary resolution, we are recycling application pool twice a day for smooth processing of reports, but recycling also destroying application session.
    Please suggest a solution, which can help to run crystal reports correctly without any memory leak.

    Helena, CR XI R2 is not supported in .NET 2008. See [this|https://wiki.sdn.sap.com/wiki/display/BOBJ/WhichCrystalReportsassemblyversionsaresupportedinwhichversionsofVisualStudio+.NET] wiki for more details.
    Re. your unanswered post. Can you provide a link? I search for unanswered posts, but do not see one from you.
    Remember that this is a community forum only, not support as such. If this is an important issue and you wish to discuss it with technical support, you can create a phone case here:
    http://store.businessobjects.com/store/bobjamer/DisplayProductByTypePage&parentCategoryID=&categoryID=11522300
    Ludek

  • TestStand 2010 Memory Leak when calling sequence in New Thread or New Execution

    Version:  TestStand 4.5.0.310
    OS:  Windows XP
    Steps to reproduce:
    1) Unzip 2 attached sequences into this folder:  C:\New Thread Memory Leak
    2) Open "New Thread Memory Leak - Client" SEQ file in TestStand 2010
    3) Open Task Manager, click Processes tab, sort A-Z (important), and highlight the "SeqEdit.exe" process.  Note the memory useage.
    4) Be ready to click Terminate All in TestStand after you see the memory start jumping.
    5) Run the "New Thread Memory Leak - Client" sequence.
    6) After seeing the memory consumption increase rapidly in Task Manager, press Terminate All in TestStand.
    7) Right click the "While Loop - No Wait (New Thread)" step and set Run Mode » Skip
    8) Right click the "While Loop - No Wait (New Execution)" step and set Run Mode » Normal
    9) Repeat steps 3 through 6
    I've removed all steps from the While Loop to isolate the problem.  I've also tried the other methods you'll see in the ZIP file but all cause the memory leak (with the exception of the Message Popup).
    I have not installed the f1 patch, but none of the bug fixes listed appear to address this issue.  NI Applications Engineering has been able to reproduce the issue (with Windows 7) and is working on it in parallel.  That said, are we missing something??
    Any ideas?
    Certified LabVIEW Architect
    Wait for Flag / Set Flag
    Separate Views from Implementation for Strict Type Defs
    Solved!
    Go to Solution.
    Attachments:
    New Thread Memory Leak.zip ‏14 KB

    Good point Doug.  In this case parallel sequences are being launched at the beginning of the sequential process model, but I'll keep that in mind for later.  Take away:  be intentional about when to wait at the end of the sequence for threads to complete.
    Certified LabVIEW Architect
    Wait for Flag / Set Flag
    Separate Views from Implementation for Strict Type Defs

  • Crystal report XI makeas memory leaking

    Hi all:
    My application use vs2003/COM+ with independ crystal report XI and it has a serious memory leaking issue. After I generated the report, the memory grew twice and then soon the application is crashed after it is up to the maximum memory.Microsoft helped me to look at the dump user file and their concusion is that the Crystal report was build with Debug mode and not release mode. I never heard it before since I only add module to my deployment project and never know it has debug and release module version. So Can I please get help and how can I get the release crystal report module?
    copid from the Microsft reply email:
    Hello Helena,
    Your custom modules are built in Release mode as per the configuration settings in Visual Studio, however, all the dlls that are built in Debug mode are listed below:-
    crystaldecisions.reportappserver.commlayer.dll built debug
    crystaldecisions.reportappserver.clientdoc.dll built debug
    crystaldecisions.reportappserver.cubedefmodel.dll built debug
    crystaldecisions.reportappserver.controllers.dll built debug
    crystaldecisions.reportappserver.datadefmodel.dll built debug
    crystaldecisions.reportappserver.reportdefmodel.dll built debug
    crystaldecisions.keycode.dll built debug
    crdb_adoplus.dll built debug
    the crystaldecisions.crystalreports.engine.dll  version is 11.5.3300.0
    Thanks
    Helena

    You can not. The memory will never go down to zero - at least not as long as the app is running. There is a number of files, assemblies, etc. held in memory by the framework until the app is shut down. This behaviour is by design, and is actually quite important. First with an application more then one report can be loaded at one time, so the underlying dlls couldn't be unloaded until all reports for that application were closed. If we behaved this way, everytime a new report was opened we would need to load all our core dlls, search for optional dlls and read all the registry keys over again. This would be a performance hit in the speed of the report being viewed and on the entire system. By leaving our core engine open after the report is closed there is no longer this bottle neck, and really if we changed this we would get lots of complaints.
    Now in general this is not that big of an issue for Windows applications as it is usually one user on a system at a time and 40 MB for a user is not much. For web applications I can see this as a potential issue, however if you are having 100 users at a single time running reports from your web application I might suggest that Crystal Reports may not be the best solution for you. I suggest you look at Business Objects Enterprise where you can offload the report generation from your Web App server to the Enterprise server to see if this would benefit you.
    A memory leak would be if you see this number increasing for ever - unitl you run out of memory and the mchine become unresponsive.

  • Memory Leaks in CRPE32.dll of Crystal report 8.5

    Post Author: Pugalendran P
    CA Forum: Crystal Reports
    Hi,
    On calling the PEOpenPrintEngine() API function of the Crystal report 8.5, the CRPE32.dll leaks memory of 2-3 kb. After printing 10000 reports approximately on a Server, the memory of the server was fully consumed and throws an exception stating "Unable to get current formula '' contents, Not enough memory for operation.".
    There are also other errors stating like "not enough memory for operation".
    Is there any resolution / hotfix / patch available to resolve this problem?
    If resolution / hotfix / patch is not available in Crystal report 8.5, will upgrading to Crystal Reports XI resolve this problem?
    Thanks in Advance,

    Hi all, Memory leaks are not usually an issue with CR and any that were reported have been plugged in 8.5. Most, using third party tools, are linked to some core MS dll's, printer drivers etc.
    And more commonly due to not releasing the report object, database connections, Printer DEVMODE's structure and other memory allocations you may have created in your application and not cleaned up when the report object is closed and disposed of.
    As for the life cycle this has been posted on our support site for quite a few years now, with the new Support site this link is not currently available but Google does have a cached copy of this from this link:
    http://209.85.173.104/search?q=cache:DkU35JxW5HsJ:support.businessobjects.com/programs_and_lifecycle/lifecycle/product_eol_dates.aspbusinessobjectslifecycle;hl=en&ct=clnk&cd=2&gl=ca
    Thank you
    Don

  • Crystal Report Basic for VS 2008 Memory Leak

    Hi,
    I am having a problem with CR Basic for VS 2008.  I can display a report, which I have linked to an DataSet in C#, but when I close the window, I seem to have a memory leak, as verified by process explorer.
    I am doing the following when the report window is closing:
    myReportViewer.ReportSource = null;
    myReportViewer.Dispose();
    myReportObject.Close();
    myReportObject.Dispose();
    GC.Collect();
    Any ideas?  I have a significant report that is generated and the memory leak is quite significant.
    Thanks,
    Dave

    The memory management you are seeing is an artifact of how the framework manages memory allocations of managed dlls. These dlls are left in memory as it is expect that they may be used later on in your app and reloading these dlls would be a resource intensive process. It is difficult, if not impossible to unload managed dlls and there may not be a good solution.  However I suspect that once the managed dlls are loaded, you will see the memory moving in the 38,860 to 40,812 range. This memory will not be freed by the framework until the application is terminated.                                                                               
    Couple of ideas:                                                                               
    1) Trying to find resources on the possibility of unloading managed dlls. Apparently there is a way, but it is cumbersome. Couple of years ago, one of my coworkers spent some time on the issue and eventually gave upu2026 Looking around a bit, I have found the following links that may be of some use to you:                                                                               
    http://blogs.msdn.com/jasonz/archive/2004/05/31/145105.aspx                                                                         
    http://social.msdn.microsoft.com/Forums/en-US/csharpgeneral/thread/a2682b53-12ad-4719-b05c-df1476cb39c9                             
    http://msdn.microsoft.com/en-us/library/system.appdomain.aspx ;                                                                      
    http://www.discussweb.com/c-programming/2391-how-unload-both-managed-unmanaged-dll.html ;                                                                               
    2) Try to see how the latest version of Crystal Reports behaves in your environment. Initially, I would suggest a test on a clean system with an eval version of Crystal Reports 2008. In CR 2008 we manage the memory via the crheapalloc.dll. So the behavior may be different. You can even try to see how CR 2008 behaves without the dll by simply renaming the dll.                                                                               
    An eval download of CR 2008 is here:                                                                               
    http://www.sap.com/solutions/sapbusinessobjects/sme/freetrials/index.epx                                                                               
    Ludek

  • How do I report a major memory leak problem with Firefox 3.6.10 in WinXP?

    After I installed Firefox 3.6.9 on a WinXP desktop, I occasionally had minor memory leak problems, reflected by getting "out of virtual memory" messages. I upgraded to 3.6.10 when notified that it was available and that it supposedly fixed stability problems. Ever since then, whenever I use Firefox, it starts out quick as a flash, but very rapidly slows down to a crawl, and has twice brought my system to a halt. IE does not cause this, nor any other program I use, but the execution speed of all programs slows as badly as Firefox. If I knew where to get older versions, I would back up to 3.6.9 or earlier. The situation now prevents me from using Firefox much at all.

    Im running windows 7, Firefox 3.6.10 and before i updated to 3.6.10 my CPU never went above 10% with Firefox open. Now it can spike well above 50% and i have nothing different from when i had 3.6.9 to now when i have 3.6.10.
    There is no evidence for me to suggest one of the additions i have is causing it, its all pointing to Firefox itself and the last update.

  • Problem Report: Severe memory leak in Flash Player 9.0

    Summary
    Flash player 9.0 is prone to a severe memory leak when
    playing SWF files produced by Captivate 1 containing full-motion
    recordings.
    Versions affected
    The problem reproduces with Flash player 9.0 (Flash9.ocx,
    Version 9.0.16.0) hosted in either Internet Explorer 6.0 or Mozilla
    Firefox 1.5 on a Windows XP SP2 system.
    The problem does not reproduce with Flash player 8.0
    (Flash8.ocx, Version 8.0.22.0) in the same environment.
    Description
    After a few minutes playing a SWF file produced by Captivate
    1 containing a full-motion recording recorded with Captivate 1, the
    host browser ends up using more than a gigabyte of memory, and the
    playback of the movie slows down to a halt, together with
    responsiveness of the whole system.
    Impact
    Our organization develops E-learning content with Captivate 1
    for various customers, mostly Fortune 100 companies.
    This bug severely limits our ability to deliver content to
    our customers.
    Steps to reproduce
    1. Using Captivate 1.01.1418, create a “blank
    movie” with default settings.
    2. Use the “Record” button and begin recording a
    full-motion movie for about 2-4 minutes. For the purposes of this
    bug, it is enough to record a user typing random text in a Notepad
    window resized to fit in the default 800x600 window.
    3. After recording the full-motion movie, publish the
    Captivate movie as a “Flash (SWF)” movie, using default
    settings (making sure that the “export HTML” checkbox
    is selected).
    4. Open the published movie’s HTML file with a host
    browser, making sure that the browser is using the Flash 9.0
    player.
    5. While the movie is playing, watch the memory usage of the
    browser process using Windows Task Manager, and you will see that
    the values of the “Mem Usage” and “VM Size”
    counters keep increasing until the system becomes unusable.

    Also see:
    http://www.adobe.com/cfusion/webforums/forum/messageview.cfm?forumid=44&catid=184&threadid =1249396&enterthread=y
    Flash is generating around 300 page faults per second per
    flash animation
    Performance
    issues: page faulting
    Flash is also generating around 300 page faults per second.
    This can be observed by following the instructions in the link
    above for displaying page faults in the system task manager.

  • CVI dll to read XML file causes memory leak

    Hello,
    I am facing a memory leak issue when I execute a dll created using CVI to read a XML file.
    Each iteration of the step is taking around 200k of memory.
    Short description of the code:
    Basically I am using a function created in CVI to read from an XML file by tag which 2 attributes: command and the response;
    int GetCmdAndRsp(char XML_File[MAX_STR_SIZE], char tag[MAX_STR_SIZE], char Command[MAX_STR_SIZE], char Response[MAX_STR_SIZE], char ErrorDescription[MAX_STR_SIZE]) 
    inputs:  
    - XML_File_path;
    - tagToFind;
    ouputs:
    - Command;
    - Response;
    - Error;
    Example:
    XMLFile:
    <WriteParameter Command="0x9 %i %i %i %i %i" Response = "0x8 V %i %i %i %i"/>
    Execution:
    error = GetCmdAndRsp("c:\\temp\\ACS_Messages.xml" ,"WriteParameter", cmd, rsp, errStr) 
    output:
    error = 0
    cmd = "0x9 %i %i %i %i %i"
    rsp = "0x8 V %i %i %i %i"
    errStr = "Unkown Error"
    Everything is working correctly but I have this memory leak issue. Why am I having such memory consumption?? Is it a TestStand or CVI issue??
    Each iteration I am loading the file, reading the file and discarding the file.
    Attached you can find the CVI project, a TestStand sequence to test (ReadXML_test2.seq) and an example of a XML file I am using.
    Please help me here.
    Thaks in advance.
    Regards,
    Pedro Moreira
    Attachments:
    ReadXML_Prj.zip ‏1826 KB

    Pedro,
    When a TestStand step executes, its result will be stored by TestStand which will be later used for generating reports or logging data into database.
    You are looking at the memory (private bytes) when the sequence file has not finished execution. So, the memory you are looking at, includes the memory used by TestStand to store result of the step. The memory used for storing results will be de-allocated after finishing the sequence file execution.
    Hence, we dont know if there is actual memory leak or not. You should look at the memory, before and after executing sequence file instead of looking in between execution.
    Also, here are some pointers that will be helpful for checking memory leak in an application:
    1. TestStand is based on COM and uses BSTR in many function. BSTR caches the memory and because of the behavior, sometime you might get false notion of having memory leak. Hence, you need to use SetOaNoCache function OR set the OANOCACHE=1 environment variable to disable caching.
    2. Execute the sequence file atleast once before doing the actual memory leak test. The dry run will make sure all static variables are initialized before doing memory leak test.
    3. Make sure that the state of system or application is same when considering the Private bytes. Ex: Lets say ReportViewControl is not visible before you start executing sequence file. Then you note down the private bytes and then execute the sequence file. After finishing execution, make sure you close the ReportViewControl and then note down the private bytes once again to check if memory is leaked or not.
    4. If there exists memory leak as you specified, it is possible that the leak is either in TestStand, or in your code. Make sure that your code doesn't leak by creating a small standalone application (probably a console application) which calls your code.
    Detecting memory leaks in CVI is better explained in
    http://www.ni.com/white-paper/10785/en/
    http://www.ni.com/white-paper/7959/en/
    - Shashidhar

Maybe you are looking for