Search Results for "fix memory leaks"

OSS-Fuzz is a large-scale fuzz testing platform developed by Google to improve the security and reliability of widely used open source software. Fuzz testing is a proven method for uncovering programming errors such as buffer overflows and memory leaks, which can lead to severe security vulnerabilities. By leveraging guided in-process fuzzing, Google has already identified thousands of issues in projects like Chrome, and this initiative extends the same capabilities to the broader open source community. OSS-Fuzz integrates modern fuzzing engines with sanitizers and runs them at scale in a distributed environment, providing automated testing and continuous monitoring. ...

...We understand the pain of unnecessary and sometimes rarely used mods/features being shipped with custom roms nowadays which may end up causing battery drains and/or memory leaks. This is being strictly avoided on our side keeping everything to a bare minimum, delivering the stable performance all the time without destroying the AOSP interface. With users getting more used to tweaks and features, we added just the right stuff that will be actually USEFUL at the end of the day.

Includes: Java JDK 13 or Java JDK 14 or Java JDK 16 or Java JDK 18 or Java JDK 19 OpenSource JDK. Dev/Run-time Visual VM JConsole MissionControl the JET's in JETPack.

...Element-Size and chronological order. Use malloc{slower-but-easy} or fix (static) memory. - OAList01: Object-Kind of a predefined pre-reserved List with X Elements (with constant user-data size), with secur modify functions and option to use locks (POSIX: mutex). Supporting a BusyList and a IdleList for easy build of e.g. a FIFO without need of much time for mem-allocation. - Release-Notes see uws-Lnkdlst-readme.txt in the tar.gz file(s) and in „Files“.

This library allows one to automatically complete sequences based on a second lifecycle stream. This capability is useful in Android, where incomplete subscriptions can cause memory leaks. You must start with an Observable<T> representing a lifecycle stream. Then you use RxLifecycle to bind a sequence to that lifecycle. It assumes you want to end the sequence in the opposing lifecycle event - e.g., if subscribing during start, it will terminate on stop. If you subscribe after pause, it will terminate at the next destruction event (e.g., pasue will terminate in stop). ...

...OYSTER (Open sYSTem Entity Resolution) is an entity resolution system that supports probabilistic direct matching, transitive linking, and asserted linking. To facilitate prospecting for match candidates (blocking), the system builds and maintains an in-memory index of attribute values to identities. Because OYSTER has an identity management system, it also supports persistent identity identifiers. OYSTER is unique among other ER systems in that it is built to incorporate Entity Identity Information Management (EIIM). OYSTER supports EIIM by providing methods that enforce identifiers to be unique among identities, maintain persistent IDs over the life of an identity, and allowing the ability to fix false-positive and false-negative resolutions, which cannot be done with matching rules, through the use of assertion, traceability, and other features.

...Because it relies on annotation processing, there’s no reflection at runtime, keeping startup paths lean and predictable. The generated bind/unbind lifecycle helps avoid memory leaks by clearing references when views are destroyed. Butter Knife made UI code more readable and maintainable for years, especially in large codebases with complex layouts and many event hooks. While newer Android APIs now offer official view binding alternatives, the project remains a landmark example of how code generation can simplify everyday Android development.

...Unlike simple observer patterns, AndroidEventBus typically integrates with Android lifecycles so that subscribers are automatically registered, paused, or cleaned up based on activity/fragment state — reducing memory leaks and errant behavior during configuration changes. The library aims to simplify common inter-component messaging tasks (like posting a login success event or notifying multiple listeners of state changes) while preserving type safety and performance.

Madmap is a tool to help analyze java heap dumps. New in v1.1 it supports hprof ascii and now binary dumps collected with jmap. It helps find memory leaks by showing the live set and automatically calculating which objects retain the most heap size.

Importer library to import assets from different common 3D file formats such as Collada, Blend, Obj, X, 3DS, LWO, MD5, MD2, MD3, MDL, MS3D and a lot of other formats. The data is stored in an own in-memory data-format, which can be easily processed. www.open3mod.com/ is a 3D model viewer and exporter based on Assimp that is also Open Source.

...When combined with the Super Mario World (SMW) engine you can create awesome 2D platform games like Super Mario World. This language evolved from a "clone" of TI-BASIC which I began developing when I was having memory (segmentation fault) bugs with C. C-Lesh lacks memory allocation and destruction. There is no need to use pointers and you can never get memory leaks or program crashes caused by memory leaks. As C-Lesh is somewhat primitive you may like it if you are into C. I'd say its a step up from C for 2D games. Everything is set - all you need is a sprite sheet and some programming knowledge.

Objectreferenceanalyser (ORA) helps finding memory leaks, design weaknesses and bugs. The ORA-Framework visualizes objects, their content and relations during runtime of any Java application and is able to persist these findings for subsequent analyze.

A modular java library which addresses the most common classloader memory leaks in common java application servers and libraries.

Realy simple and useful Java music player Features: * Low Processor/Memory usage * Search music easily by "Locate music" * Simple ID3 tag editor * Indentify and offer to fix problems with ID3 tags (like unknown artist) * "Delete the current music

Open Office Server Daemon based on older daemon written in python (oood). Open Office is unstable as a server (memory leaks, not multithreaded, ...), this daemon makes it working in long-term without having to change anything in your code.

AIXmem is a tool to detect memory leaks in a IBM AIX C-development environment. AIX 'User Defined Malloc Replacement' is used to trace the memory allocation and freeing. --> Unfortunately i don't have time to make something useful out of this. :( <--

JHeap provides the toolset to help Java developers discover and fix the root cause of memory issues in their applications. JHeap integrates easily with your application server and has been designed to be used in production environments with low overhead.

AdaptiveCells J2EE generates test-beds for benchmarking J2EE performance. They consists of highly customizable EJB cells that can emulate CPU load, memory usage, memory leaks and exceptions. The behaviour of the cells is coordinated from a web front-end.