CODEWITHSUNDEEP
androidandroid-studioandroid-logcat
mehdok
mehdok

Reputation: 1608

Stop memory monitor in Android Studio 1.2.1.1

In Android Studio version 1.0 there was a close button beside the memory monitor panel that stops it from reporting memory changes; but in Android Studio version 1.2.1.1 the close button isn't there anymore.

The annoying thing is that logcat will flood the monitoring log and I can't see my log anymore.

05-27 16:21:24.431 32121-32127/com.exampleapp D/jdwp﹕ handlePacket : cmd=0x1, cmdSet=0xC7, len=0x14, id=0x40001396, flags=0x0, dataLen=0x9
05-27 16:21:24.431 32121-32127/com.exampleapp D/jdwp﹕ sendBufferedRequest : len=0x34     
05-27 16:21:24.932 32121-32127/com.exampleapp D/jdwp﹕ processIncoming

So how can i stop memory monitor and its annoying logs?

UPDATE 1:

enter image description here

Upvotes: 0

Views: 1573

Answers (4)

mehdok
mehdok

Reputation: 1608

creating a filter like the picture will solve the problem, but it is not a real answer also :)

enter image description here

Here is the filter: 

^(?!(jdwp))

Upvotes: 4

Lennon Spirlandelli
Lennon Spirlandelli

Reputation: 3193

You can stop monitoring at anytime by disable the ADB Integration. Click on Tools in the top, go to Android and then click on Enable ADB Integration to deselect it. Like the following image:

enter image description here

To Enable Enable ADB Integration again you must do the same thing.

After that, you can change the logcat option to specify what kinda monitoring you want. In the next image shows that I wanted to monitor only logs from my app:

enter image description here

Upvotes: 0

Denys Kniazhev-Support Ukraine
Denys Kniazhev-Support Ukraine

Reputation: 9102

I believe that logs that you have listed have nothing to do with memory monitor window.

There is not much you can do about such logs. They are of "Debug" level so first thing you can do is to select a more severe log level ("Info", "Warn", "Error" or "Alert"). You can do this in the Log Level dropdown:

enter image description here

If you need to watch debug logs from your app then you can do

Log.wtf("===", "message");

and select Log Level "Assert". This way you'll only see your custom logs. Or you can use a more sophisticated logging tool, like Jake Wharton's Hugo

Upvotes: 3

aga
aga

Reputation: 29416

The annoying thing is that logcat will flood the monitoring log and I can't see my log anymore.

If I understand your issue correctly than here comes the easier solution. You can filter the log messages by the package name like so: enter image description here

Upvotes: 0

Related Questions