Android Studio, logcat clears after closing the application

Question

I have a problem with my logcat since the 1.2 Beta update for Android Studio. When I launch my application, it records everything as usual, and I got to the point where my application crashes with the application, saying: unfortunately, the game is stopped.

After a few seconds, the android closes this message. When this happens, my logarithm is also completely cleared, which means that I barely have time to read the error. I found some information about the buffer, but it seems Android Studio has no way to increase this, except that I doubt it is a problem.

Something that may be useful is that after clearing it and changing the process in Android.process.core and the message that I get in my logarithmic mode is:

04-13 10:28:13.394 12259-12265/android.process.acore D/dalvikvm﹕ Debugger has detached; object registry had 1 entries 

Edit: I read about breakpoints, so I turned off the focus application on breakpoints in the settings-build, execute, deploy-debugger, but this had no effect.

Answer 1

I had the same problem, but more like a function than an error:

In AndroidStudio, the default value for the Logcat window looks like "Show only the selected application" (upper right corner of the Logcat window) ... which looks at the log of the selected process (your current launch by default). Therefore, when your application crashes during testing, this process has disappeared, so the filter clears the log.

Instead, select "Edit Filter Configuration ..." and configure the filter for your application , for example:

• Filter Name: MyApp
• PackageName: com.example.myapp (<<replace with your application package name)

... and then select this filter for future runs. This should contain a log for you, even after the application crashes.

Answer 2

Switch "Show only selected application" to "No filters". This way you can see the logcat output from the process, even if that process is not running.

The disadvantage is that your logarithm will be filled with a lot of spam from other processes.

Answer 3

My application crashed and rebooted. I also had some problems reading logcat to know what was going on. Then I noticed that in the drop-down menu next to the “Device” drop-down list there was something like “com.mypackage.myapp (“ some number ”), and when my application hung, there was another option called“ com.mypackage .myapp ('some number') [DEAD] " . If you select the "Dead" option, it will show you the logcat of the previous instance.

Answer 4

In the event of a failure, see Run " Run " at the bottom of the IDE.

You can see the reason for the failure in this part (even in the pure case of logcat).

Note. If the trick described above does not work, try to crash and immediately disconnect the mobile cable (if you are using a real device for the test). You can see the error before clearing it.

Answer 5

I ran into the same problem and this solution: -

1- Tools → Android → Enable ADB Integration.

and now you can see the logarithm and alarms as usual

Answer 6

The filter clears the log after the application crashes. Therefore, select "Edit Filter Configuration" and create your own filter with the name of the filter. This will keep a log of information even when the application is hacked.

Answer 7

This is the year 2018, and it can still happen. Close Android Studio and open again.

Answer 8

This error seems to be fixed with the new version of Android Studio version 1.2.2

Answer 9

I ran into the same problem and none of the answers helped me until I realized that my application was raising an OutOfMemoryException. This is a probable reason.

Answer 10

In Android Studio 2+

1. Click Run

2. Click Edit Configurations

3. In the Run/Debug Configurations window, select the Miscellaneous tab

4. Make sure the Clear log before launch check box is not selected.