Logcat crashes with error: unexpected EOF

AndroidAndroid Logcat

Android Problem Overview

I’m running some lengthy calculations and something goes wrong quite late. I tried using breakpoints, but with no success so far. So I put into the loop a Log.d to monitor...

But quite soon, Logcat crashes with:

02-08 16:35:42.820 2936-3402/com.nohkumado.geneticsolving.full D/BaseC: 
    norm:BC sq:49.0 dis:0.0 con:50.0/BC sq:56.0 dis:4.0 con:94.0=1.4069148936170213

    read: unexpected EOF!

    --------- beginning of crash

and I need to restart the studio to get Logcat running again.

I looked if I could find some setting for the buffer size for Logcat, but so far I’ve found nothing. What can be done?

Android Solutions

Solution 1 - Android

Fuller answer

The accepted answer didn't work for me. Rather than turning the logger buffer off, I increased it to the max size.

  1. Enable developer options in your emulator or device (not Android Studio) if it hasn't been enabled already: In your emulator or device go to Settings > System > About (emulated device) and click on Build number 7 times.
  2. Go to Settings > System > Developer options > Logger buffer sizes and choose a higher value.

enter image description here

  1. I also had to restart the emulator.

So the original problem apparently happens because the devices log buffer gets filled up for lengthy logging. Increasing the buffer size allows you to log more in a single logging session.

Solution 2 - Android

Try setting Logger buffer sizes to off under Settings->Developer options, on your device/emulator. This might be happening because Logger buffer is configured to display limited KB of logs only at a particular time. Next set of logs would only be displayed once previous buffer is cleared.

Solution 3 - Android

In Developer options you can set Logger buffer size to maximum 16M.
(Setting > System > Developer options > Logger buffer sizes)

If you need more you can set it using adb. For example you can set it to 100M:

adb logcat -G 100M

Solution 4 - Android

This log you posted is stating the app crashing (although not in the usual way with a stacktrace but it's crashing), not the logcat. Do you have the app selected and filter set to "Show selected application" in the logcat? If so just set the filter to "No Filter" and you'll see all the logs of your app.

Also in case you need to restart the logcat for any reason, rather than restarting Android Studio you could run the following commands which will restart adb and eventually restart your logcat as well:

adb kill-server
adb start-server

Solution 5 - Android

use the following command:

adb logcat -G 20M

Solution 6 - Android

  1. remove all log.d and restart android studio and Just go to File -> Invalidate Caches / Restart.
  2. your device Settings->Developer options
  3. Change Log Buffer size

Solution 7 - Android

If you are running from a real phone - disconnect & connect the phone from the usb worked for me (the buffer gets empty- like @Suragch suggested).

Solution 8 - Android

The recommendations did not work for me. I finally changed this preference setting:

Menu "Run", Menu Entry "Edit Configurations", then on the left side "Android App/app" and on the right side the tab "Miscellaneous", and finally activate "Logcat: Clear log before launch".

Of course this has side effects, but at least I can see the log output again.

Solution 9 - Android

Changing the buffer size did not work for me. What did was changing my USB connection to a USB 3.0 port.

Solution 10 - Android

Restart your device! I have no idea why it works for me after restarting my mobile phone.

Solution 11 - Android

> adb logcat -G 1m

Enter this on Terminal, it worked for me

Solution 12 - Android

Unfortunately this seems to be still an issue, i could not find a satisfying solution beside of installing a plugin(File -> Setting -> Plugins -> Marketplace) called "Log Viewer". Works better than the built-in logcat viewer of Android Studio.

Solution 13 - Android

I had the same problem as a result of reading a texting file in a while loop. I had two log.d statement in the while loop and the file size was ~220 MB. I removed the log.d statement in the while loop because it was making so many outputs in logcat. I increased the logcat size to the maximum possible. That worked for me although the processing time was long before I got the desired result.

Solution 14 - Android

Just go to File -> Invalidate Caches / Restart will let android studio do the job

Categories
Recommended Android Solutions

Previous Solution:

How can I implement ISerializable in .NET 4+ without violating inheritance security rules?

C#.NetSerializationAppdomainCode Access-Security

Next Solution:

What is the difference between persistent volume (PV) and persistent volume claim (PVC) in simple terms?

KubernetesOpenshiftStoragePersistent VolumesPersistent Volume-Claims

Attributions

All content for this solution is sourced from the original question on Stackoverflow.

The content on this page is licensed under the Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.

Content TypeOriginal AuthorOriginal Content on Stackoverflow
QuestionNoh KumadoView Question on Stackoverflow
Solution 1 - AndroidSuragchView Answer on Stackoverflow
Solution 2 - AndroidRishabhView Answer on Stackoverflow
Solution 3 - AndroidLukk17sView Answer on Stackoverflow
Solution 4 - AndroidahasbiniView Answer on Stackoverflow
Solution 5 - AndroidShubham TalekarView Answer on Stackoverflow
Solution 6 - AndroidLucky AgarwalView Answer on Stackoverflow
Solution 7 - AndroidALUFTWView Answer on Stackoverflow
Solution 8 - AndroidAndreas K. aus M.View Answer on Stackoverflow
Solution 9 - AndroidProfView Answer on Stackoverflow
Solution 10 - AndroidEnderView Answer on Stackoverflow
Solution 11 - AndroidSabin AcharyaView Answer on Stackoverflow
Solution 12 - AndroidkayaView Answer on Stackoverflow
Solution 13 - AndroidOthelloView Answer on Stackoverflow
Solution 14 - AndroidAnonymous-EView Answer on Stackoverflow