Jump to content

Search the Community

Showing results for tags 'MemoryLeak'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • uniGUI Public
    • Announcements
    • General
    • Feature Requests
    • Installation
    • Deployment
    • Other Platforms
  • Licensing
    • Licensing
    • Ordering uniGUI
  • Bug Reports
    • Active Reports
    • Closed Reports
    • Old Bug Reports
  • uniGUI Development
    • General Development
    • uniGUI Releases & Roadmaps
    • Utilities
  • Mobile Platform
    • uniGUI Mobile
    • Mobile Browsers
  • Users Area
    • Sample Projects
    • Components and Code Samples
    • Third Party Components
  • Non-English
    • Non-English
  • Miscellaneous
    • Hosting
    • Server Security
    • Jobs

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 1 result

  1. Good afternoon to everyone in the community, I'm writing from Brazil. My Unigui version is "uni-1.0.0.1410". I need to scan my system, I need to find all the places where there is a memory leak. To do this, I thought about using EurekaLog. I ran the test using the UNIGUI demo, located at: ..uniGUI \ Utils \ EurekaLog \ Demos \ Standalone \ test.dproj To configure EurekaLog, I used the recommended settings at: "..uniGUI \ Utils \ EurekaLog \ uniGUI.eof" My doubt is: - Is EurekaLog able to find 'MemoryLeak' in an application made in UNIGUI? So far the conclusion I got was: EurekaLog is able to write 'Acess Violation' log, but not 'MemoryLeak'. Has anyone used EurekaLog + UNIGUI to detect "MemoryLeak"? I got in touch with EurekaLog support, and got the following response: "Is EurekaLog capable of capturing 'MemoryLeak' in systems made in Framework Unigui? Isn't that a Web Services framework like IntraWeb? In such an application it is difficult to measure leaks. This is because web service applications are never shut down. This makes it difficult to tell if a memory allocation is legitimate or if it is an unfreed leak. In a normal EXE we store information about each heap allocation in a database located in RAM. As blocks of heap memory are freed, they are removed from the database. At shutdown we simply make a list of each un-freed memory allocations and the stack trace that produced each one. You will not see a leaks report if there were no actual leaks or the leaks were known ones in the RTL or other places." I thank the attention. att Lucas
×
×
  • Create New...