Logcat is "spammed", which results in "too much result to process",

Whenever I connect my Samsung Galaxy S5 (running Android 4.4.2) to my computer, Logcat in Android Studio starts spamming the same message several times ~ 1600 times per second , resulting in the message "Too many results for processing "that appears in the yellow box in Logcat. This happens when there is no filtering and no debugging process has been selected.

Logcat message:

D/tms_audio_hw/AudioTmsIpc AudioTmsClientListen accept Done gAudioClientAcceptSockFd -1 gAudioClientLocalSockFd 24

Googling it shows surprisingly little. Nothing really. I'm not sure, but it seems to affect logging from my application, because when I select my application as a debugging process, I don’t get all the Logcat output from my application - sometimes I get some, sometimes I get others, sometimes i don't get it.

In addition, because of this, my computer begins to use the processor, like crazy, only to process these messages, which leads to extreme processor use and fans with a full take-off!

What the hell is this?

EDIT

, , 1600 , . , " ", .

+4
4

. , "", .. , .

Logcat " ". , , , ( ) .

, , . Logcat , , .

+3

, " " Android, " " , " " , Logcat.

Android Monitor. enter image description here

+10

; Android. , , , , .

- , -, , .

0

, , " " > "" > " OpenGl", "", .

0

All Articles