Download JAR files tagged by leak with all dependencies

A memory leak tracking library for Android and Java

A simple Gradle plugin that auto-patches the memory leak in Kotlin Gradle Plugin 1.5.0.

A simple Gradle plugin that auto-patches the memory leak in Kotlin Gradle Plugin 1.5.0.

Current limiting tool based on leak bucket algorithm and token bucket algorithm.

Fix package conflicts after confusion

Test framework to confirm suspected classloader leak, and create heap dumps to track the leaks

MrChecker Database Module: - based on JPA interfaces, - structure build on ORM methodology, - supports all database engines with JDBC drivers. In case of driver leak at mvn repositories, please insert drivers file into 'lib/dbdrivers' directory. Examples build on Hibernate as a JPA provider. IMPORTANT: For easy of use Lombok library was used. In case of compilation issues please apply newest Lombok plugin for your IDE.

This is the Max5 Limbus Engine implementation that currently provides the following features: - Hot-Deploy features: - Deploy from filesystem - Deploy via Limbus API - Deploy via filesystem observer - Deploy from Maven Repositorx - Undeploy via Limbus API - Plugin lifecycle support - Classloader hierarchy - Isolation of deployed classpaths - Shared classloader for centralized libraries - Maintenance console with linux terminal suppot - Safety shutdown sequence - Classloading leak prevention - Thread stopping and cleaning

This module groups all different output writers. Different output writers have different dependencies. To ensure that those dependencies do not leak to other output writer, or that we can limit to number of dependencies at runtime, output writers are split into separate modules based on the dependencies they use. For example, the CloudWatch output writers depends on the AWS SDK, which is quite large and not used by any other output writer. If you only want to send metrics to Graphite, there should be no need to have the AWS SDK in your classpath at runtime. Some dependencies are also problematic. They can introduce incompatibilities. For example, a few writers are based directly on log4j or logback. This direct dependence breaks the use of SLF4J. By isolating those output writers to a specific module, we can ensure this has minimal impact.