blocks|key|1214914|text|如果可能，在您的问题中打印完整日志，或参阅下面的文档：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1214915|1214916|+读取堆栈跟踪|blockquote|offset|length|style|BOLD|1214917|1214918|修复崩溃的第一步是确定崩溃发生的地方。如果您使用的是Play+Console或logcat工具的输出，则可以使用报告详细信息中提供的堆栈跟踪。如果你没有可用的堆栈跟踪，你应该在本地重现崩溃，要么手动测试应用程序，要么联系受影响的用户，并在使用logcat时重现它。|1214919|以下跟踪显示了一个示例应用程序上的崩溃示例：|1214920|-开始崩溃AndroidRuntime:致命异常:主进程:+com.android.developer.crashsample，PID:+3686+java.lang.NullPointerException:在android.view.View.performClick(View.java:6134)+at+android.view.View$PerformClick.run(View.java:23965)+at+android.os.Handler.handleCallback(Handler.java:751)+at+android.os.Handler.dispatchMessage(Handler.java:95)+at+android.os.Looper.loop(Looper.java:156)+at+android.app.ActivityThread.main(ActivityThread.java:6440)的com.android.developer.crashsample.MainActivity$1.onClick(MainActivity.java:27)的崩溃样本在com.android.internal.os.ZygoteInit.main(ZygoteInit.java:746)的com.android.internal.os.Zygote$MethodAndArgsCaller.run(Zygote.java:240)的java.lang.reflect.Method.invoke(本机方法)-系统的开始|1214921|1214922|full+doc+here|1214923|entityMap|0|LINK|mutability|MUTABLE|url|https://developer.android.com/topic/performance/vitals/crash^0|0|0|1|6|0|0|0|0|0|0|0|D|0|0^^$0|@$1|2|3|4|5|6|7|11|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|12|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|13|8|@$F|14|G|15|H|I]]|9|@]|A|$]]|$1|J|3|-4|5|6|7|16|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|17|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|18|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|19|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|1A|8|@]|9|@]|A|$]]|$1|R|3|S|5|6|7|1B|8|@]|9|@$F|1C|G|1D|1|1E]]|A|$]]|$1|T|3|-4|5|6|7|1F|8|@]|9|@]|A|$]]]|U|$V|$5|W|X|Y|A|$Z|10]]]]

If possible print full log in your question or see doc below:

<blockquote>
 Reading a stack trace
 
 The first step to fix a crash is to identify the place where it happens. You can use the stack trace available in the report details if you are using Play Console or the output of the logcat tool. If you don’t have a stack trace available, you should locally reproduce the crash, either by manually testing the app or by reaching out to affected users, and reproduce it while using logcat.
 
 The following trace shows an example of a crash on a sample app:

<pre><code> --------- beginning of crash
AndroidRuntime: FATAL EXCEPTION: main
Process: com.android.developer.crashsample, PID: 3686
java.lang.NullPointerException: crash sample
at com.android.developer.crashsample.MainActivity$1.onClick(MainActivity.java:27)
at android.view.View.performClick(View.java:6134)
at android.view.View$PerformClick.run(View.java:23965)
at android.os.Handler.handleCallback(Handler.java:751)
at android.os.Handler.dispatchMessage(Handler.java:95)
at android.os.Looper.loop(Looper.java:156)
at android.app.ActivityThread.main(ActivityThread.java:6440)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.Zygote$MethodAndArgsCaller.run(Zygote.java:240)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:746)
--------- beginning of system
</code></pre>
</blockquote>

<a href="https://developer.android.com/topic/performance/vitals/crash" rel="nofollow noreferrer">full doc here</a>

blocks|key|1384399|text|此问题是由firebase性能引起的。你可以在这里找到详细的信息：https://firebase.google.com/docs/perf-mon/get-started-android|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1384400|我的日志记录如下：|1384401|---------+beginning+of+system
---------+beginning+of+main
---------+beginning+of+crash
12-25+17:53:40.583+25281+25581+D+FirebasePerformance:+Creating+a+new+Non+Verbose+Session:+34bf424qwe12312318ac831ad5459a
12-25+17:53:40.584+25081+25081+D+FirebasePerformance:+Creating+a+new+Non+Verbose+Session:+642b3efweqwsafqweqa5a73e1befasadcb2e
12-25+17:53:50.872+25181+25881+D+FirebasePerformance:+onResume():+com.example.app.ui.splash.SplashScreen:+10309636+microseconds
12-25+17:54:27.026+25381+25501+I+FirebasePerformance:+Did+not+receive+a+HTTP+Response+Code
12-25+17:54:27.026+25081+25201+W+FirebasePerformance:+Unable+to+process+the+PerfMetric+due+to+missing+or+invalid+values.+See+earlier+log+statements+for+additional+information+on+the+specific+missing/invalid+values.|code-block|syntax|javascript|1384402|你的错误和我的一样|1384403|entityMap|0|LINK|mutability|MUTABLE|url|https://firebase.google.com/docs/perf-mon/get-started-android^0|X|1P|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@$A|V|B|W|1|X]]|C|$]]|$1|D|3|E|5|6|7|Y|8|@]|9|@]|C|$]]|$1|F|3|G|5|H|7|Z|8|@]|9|@]|C|$I|J]]|$1|K|3|L|5|6|7|10|8|@]|9|@]|C|$]]|$1|M|3|-4|5|6|7|11|8|@]|9|@]|C|$]]]|N|$O|$5|P|Q|R|C|$S|T]]]]

this issue is caused by firebase performance. You can find detailed information here: <a href="https://firebase.google.com/docs/perf-mon/get-started-android" rel="nofollow noreferrer">https://firebase.google.com/docs/perf-mon/get-started-android</a>

my log record is as follows:

<pre><code>--------- beginning of system
--------- beginning of main
--------- beginning of crash
12-25 17:53:40.583 25281 25581 D FirebasePerformance: Creating a new Non Verbose Session: 34bf424qwe12312318ac831ad5459a
12-25 17:53:40.584 25081 25081 D FirebasePerformance: Creating a new Non Verbose Session: 642b3efweqwsafqweqa5a73e1befasadcb2e
12-25 17:53:50.872 25181 25881 D FirebasePerformance: onResume(): com.example.app.ui.splash.SplashScreen: 10309636 microseconds
12-25 17:54:27.026 25381 25501 I FirebasePerformance: Did not receive a HTTP Response Code
12-25 17:54:27.026 25081 25201 W FirebasePerformance: Unable to process the PerfMetric due to missing or invalid values. See earlier log statements for additional information on the specific missing/invalid values.
</code></pre>

your mistake is like mine

I am troubleshooting a strange bug, and I'm seeing this in logcat right when the bad behavior occurs.

<pre><code> --------- beginning of system
</code></pre>

What does this mean? I haven't found any native crash logs, or any exceptions, nothing. Just this "beginning of system" line right at the exact time my app is bugging out.

Logcat --------- beginning of system

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我正在排除一个奇怪的bug，当错误行为发生时，我在logcat中看到了这一点。    --------- beginning of system这是什么意思？我没有发现任何本机崩溃日志，或者任何异常，什么都没有。这行“系统的开始”恰好是在我的应用程序出错的时候。

问Logcat -系统开始
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Logcat -系统开始EN