No leaks detected
In one of the rare cases where Plumbr cannot discover the leak, you can turn to our guaranteed offering where our core team jumps in and finds the leak manually. But to make sure it is really the case, let us check a few things:
- First and foremost – as rare as it can seem, there are actually applications out there which are not leaking memory. If this is the case, congratulations for a job well done!
- Are you running Plumbr in a real application or in a small synthetic test case? When using the latter, bear in mind that Plumbr needs data from both leaking and non-leaking objects in order to build the statistics necessary for deciding whether a particular behaviour is suspicious in your particular application or not. If you are just creating leaking objects Plumbr stands no chance of comparing it to “normal” behaviour.
- Is your application actually being used? Plumbr monitors the application during runtime to detect anomalies during object creation and destruction. If nobody is using the application Plumbr has nothing to monitor nor detect. So either generate the load or let the end users do the job in production deployments.
- And as a last resort, we have to admit we find only nine out of ten leaks out there. So some of the leaks might be left unnoticed. In this case, contact us and our engineering will find the leak manually.