android studio app keeps stopping in emulator

I kept scrolling up and down in the log and several minutes after I'd restarted, I FINALLY got a stacktrace for my app. Then I got a stacktrace but it was nothing to do with my app. Then I got some red lines that were not stacktraces. White lines started getting written but nothing red.

I was in normal Run mode, not debug.) I immediately clicked on Logcat and it was completely empty I'd never seen that before! (I realize now that it was because I had a short search string in the search box and none of the existing log records containing that string.) I found the icon to restart Logcat and clicked it (with the setting at Verbose). (Again, I was testing on my phone but initiated the test from Android Studio with the phone connected via USB. Okay, I'm back to testing and the same thing happened: the app crashed. I prefer to run the app without debug first to see which parts of the major functionality are working and which parts have bugs, then I can zoom in on the parts with bugs via debug. Usually I find that if I just run the app again (sometimes two or three times), it eventually starts and finally shows a stacktrace but why should that be necessary? It's just a waste of time. Is this working correctly as I've described it? If it is, how is it possible to figure out my problem without a stacktrace? Are there other logs or places to check for diagnostics? I'm new with Android so there's a lot I don't know yet. I check to see if there are other threads and I just happen to be on the wrong one but usually there is just the one even if there is another, clicking on it, doesn't change what I see: it's the exact same information for both threads. Sometimes the LogCat hasn't had anything written to it for a few minutes. I go to LogCat and look through it carefully - and find NOTHING. I'll run my app and then get a message that the app has crashed it advises me to click on the message and it will restart. I've experienced this several times now and it's getting really annoying. I've seen the claim that all crashes of apps cause a stacktrace to be written to LogCat but I'm here to tell you that this is NOT always true. How do you figure out why your app crashed if no stacktrace was written to LogCat?

Android studio app keeps stopping in emulator