Sua aplicação fica lenta com o passar do tempo? Recebe exceções por falta de memória? Pode ser "Vazamento de Memória". Aperte o play e confira!
Participantes
Marcio Frayze David
marcio@segunda.tech
https://twitter.com/marciofrayze
https://segunda.tech
https://masto.donte.com.br/web/accounts/138458
https://linkedin.com/in/marcio-frayze
Julianno Martins Silva
juliannoms@gmail.com
https://twitter.com/juliannoms
https://linkedin.com/in/juliannoms
Links:
Analisador on-line de logs do GC (identifica possíveis vazamentos):
https://gceasy.io/
Visual VM:
https://visualvm.github.io/
Try with resources do Java:
https://docs.oracle.com/javase/tutorial/essential/exceptions/tryResourceClose.html
Git lab memory leads issues:
https://duckduckgo.com/?t=ffab&q=gitlab+memory+leak&atb=v223-1&ia=web
Memory Leak no Rust:
https://doc.rust-lang.org/book/ch15-06-reference-cycles.html#reference-cycles-can-leak-memory
Microsoft 70% dos bugs de segurança:
https://www.zdnet.com/article/microsoft-70-percent-of-all-security-bugs-are-memory-safety-issues
Podcast do Marcio sobre Livros:
Outros artigos:
https://martinfowler.com/articles/qa-in-production.html
https://deepsource.io/blog/exponential-cost-of-fixing-bugs
https://developers.redhat.com/blog/2014/08/14/find-fix-memory-leaks-java-application
https://www.toptal.com/java/hunting-memory-leaks-in-java
https://www.baeldung.com/java-heap-dump-capture
https://www.dynatrace.com/news/blog/the-top-java-memory-problems-part-1/