Why logcat messages drain
It depends on what you mean by "leak". If the problem is that the messages are scrolling too fast and you need to stop auto-scrolling at the bottom, you can pause this function in the IDE (or DDMS / Monitor). How you do this depends on your IDE, in IntelliJ you can just click somewhere in the log output to place the cursor, and in Eclipse there is a button above the logcat window to pause the output scrolling (don't forget to bring it back or you don't see new messages).
However, if your problem is that so much data is being logged that you cannot scroll up to see what you need, even if the pause is paused, you need to log less. This is because the Android logcat driver is a 64KB ring buffer. So if you log enough data, it will start overwriting the old log entries and they will disappear before you have a chance to read them.
source to share
Why don't you filter out the logarithm, so it shows what interests you the most.
You can only display the tags you are interested in using the following syntax (using the adb tool from the command line, also available in the logcat view in Eclipse):
adb logcat TAGTOSHOW:* TAGTOSHOW2:* *:s
You can enable as many TAG combinations as you like. Don't forget * .s, which outshines everyone else.
source to share