Jon.
Has anyone else used the trick of adding a few strategically-placed `new Array(1000000)`s to check for memory leaks?
-
-
-
Fail faster.
End of conversation
New conversation -
-
-
scala.util.Random.alphanumeric.mkString *running*
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
If all you see in profilers is byte[] then different type arrays will surely help... But JFR nowadays gives you a stack trace so not sure I'd use this. I am of course clueless about your setup... etc.
-
JFR for java fligh messages?
End of conversation
New conversation -
-
-
the `println("this worked")` of memory leaking debugging. tbh I never thought of this :D, thanks Jon, you keep giving and giving.
-
Glad it helped! I had never tried it before today, but I'm writing a
@scala_zone lesson on streaming with LazyLists, and I wanted a good way to demonstrate that you need to be careful about holding references to the stream... - Show replies
New conversation -
-
-
Could someone pls explain how allocating a bunch of memory could help detecting leaks?
-
I suppose if you want to check if a small object is leaking or not. You weight it in this way, an see if your app crash faster.
End of conversation
New conversation -
-
-
I... Yes.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.