blocks|key|1958842|text|关闭方法断点。您可以通过Run+000-View断点查看所有断点(Ctrl+-F8+)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1958843|​|1958844|📷|atomic|offset|length|1958845|1958846|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/8edf068e6c7dcc3c9f56c36affd9d944.png|imageAlt^0|0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|U|8|@]|9|@$G|V|H|W|1|X]]|A|$]]|$1|I|3|C|5|6|7|Y|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q|R|-4]]]]

Turn off the method breakpoints. You can see all your breakpoints through Run | View Breakpoints (Ctrl - Shift -F8 )
<a href="https://i.stack.imgur.com/3aEkg.png" rel="noreferrer"><img src="https://i.stack.imgur.com/3aEkg.png" alt="enter image description here" /></a>

blocks|key|1440356|text|在IDEA+2017.1中引入了模拟的方法断点：断点，它们允许使用方法断点，而不需要性能损失。默认启用。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1440357|entityMap|0|LINK|mutability|MUTABLE|url|https://www.jetbrains.com/help/idea/using-breakpoints.html#method_breakpoint^0|O|2|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

In IDEA 2017.1 Emulated Method Breakpoints were introduced: <a href="https://www.jetbrains.com/help/idea/using-breakpoints.html#method_breakpoint" rel="noreferrer">https://www.jetbrains.com/help/idea/using-breakpoints.html#method_breakpoint</a>
They allow using method breakpoints without the performance penalty.
Enabled by default.

blocks|key|144136|text|来自JetBrains团队：“由于JVM的设计，方法断点会大大降低调试器的速度，评估它们的代价很高。删除方法断点并考虑使用常规的行断点。”见更多。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|144137|长话短说，根本的问题似乎是方法断点是使用JPDA的方法入口&方法退出特性实现的。这种实现要求JVM每次任何线程进入anyE+210方法时，以及当E+111任何E+212线程退出E+113任何E+214方法时，都会触发一个事件。|style|BOLD|CODE|144138|entityMap|0|LINK|mutability|MUTABLE|url|https://intellij-support.jetbrains.com/hc/en-us/articles/206544799-Java-slow-performance-or-hangups-when-starting-debugger-and-stepping^0|1Y|2|0|0|K|4|P|4|U|4|1F|2|1L|1K|1O|5|20|5|27|5|2G|5|2N|5|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@$A|R|B|S|1|T]]|C|$]]|$1|D|3|E|5|6|7|U|8|@$A|V|B|W|F|G]|$A|X|B|Y|F|G]|$A|Z|B|10|F|G]|$A|11|B|12|F|G]|$A|13|B|14|F|G]|$A|15|B|16|F|H]|$A|17|B|18|F|H]|$A|19|B|1A|F|H]|$A|1B|B|1C|F|H]|$A|1D|B|1E|F|H]]|9|@]|C|$]]|$1|I|3|-4|5|6|7|1F|8|@]|9|@]|C|$]]]|J|$K|$5|L|M|N|C|$O|P]]]]

From the JetBrains Team: "Method breakpoints will slow down debugger a lot because of the JVM design, they are expensive to evaluate. Remove method breakpoints and consider using the regular line breakpoints.". See <a href="https://intellij-support.jetbrains.com/hc/en-us/articles/206544799-Java-slow-performance-or-hangups-when-starting-debugger-and-stepping" rel="noreferrer">more</a>.

To make the long story short, it seems that the root issue is that Method Breakpoints are implemented by using JPDA's Method Entry &amp; Method Exit feature. This implementation requires the JVM to fire an event each time any thread enters any method and when any thread exits any method.

blocks|key|1440401|text|我遵循的实用建议是:+1.在应用程序出现时静音所有断点；2.仅在调试该流程时启用断点。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1440402|当然，如果您尝试调试在应用程序启动过程中发生的事情，这将于事无补。|1440403|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Practical advice that I follow:
1. mute all the breakpoints while the app is coming up
2. enable breakpoints only while debugging that flow.

Of course, it won't help if you are trying to debug something which happens during app startup.

blocks|key|1440412|text|查找代码中的红色菱形图标(不是红色圆圈)，这些图标表示方法断点。很可能是在Kotlin中的get()/set()方法中设置它们。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1440413|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Look for the red diamond icons (not red circles) in your code, those represent the method breakpoints. Most probably you set them at get()/set() methods in Kotlin.

blocks|key|144211|text|​|type|unstyled|depth|inlineStyleRanges|entityRanges|data|144212|📷|atomic|offset|length|144213|144214|从调试面板中关闭方法断点。这是截图。|144215|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/4838e6ce6f412e9eb4612e53179931f5.png|imageAlt^0|0|0|1|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@$E|U|F|V|1|W]]|A|$]]|$1|G|3|4|5|6|7|X|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|Y|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q|R|-4]]]]

<a href="https://i.stack.imgur.com/CmAkn.png" rel="noreferrer"><img src="https://i.stack.imgur.com/CmAkn.png" alt="enter image description here" /></a>
Turn off the method breakpoint from the debug panel.
Here is a screenshot.

blocks|key|144278|text|在我的例子中，我使用了Android，当我在method+name+line+(称为Java+Method+Break-Point)上设置断点时，Android向我展示了这个警告和调试非常慢.|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|144279|我的问题被removing+this+Break-Point解决了..。|144280|​|144281|📷|atomic|144282|144283|144284|144285|144286|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/48a25b08a5ea1a8d75e1c14ad5b750d1.png|imageAlt|1|https://developer.qcloudimg.com/http-save/yehe-900000/b96bd81169103ce98967d151bf24db2c.png^0|M|G|16|N|0|5|P|0|0|0|1|0|0|0|0|0|1|1|0|0^^$0|@$1|2|3|4|5|6|7|11|8|@$9|12|A|13|B|C]|$9|14|A|15|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|16|8|@$9|17|A|18|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|19|8|@]|D|@]|E|$]]|$1|J|3|K|5|L|7|1A|8|@]|D|@$9|1B|A|1C|1|1D]]|E|$]]|$1|M|3|I|5|6|7|1E|8|@]|D|@]|E|$]]|$1|N|3|I|5|6|7|1F|8|@]|D|@]|E|$]]|$1|O|3|K|5|L|7|1G|8|@]|D|@$9|1H|A|1I|1|1J]]|E|$]]|$1|P|3|I|5|6|7|1K|8|@]|D|@]|E|$]]|$1|Q|3|-4|5|6|7|1L|8|@]|D|@]|E|$]]]|R|$S|$5|T|U|V|E|$W|X|Y|-4]]|Z|$5|T|U|V|E|$W|10|Y|-4]]]]

In my case, I used Android Studio, When I set Break-Point on a <code>method name line</code> (called <code>Java Method Break-Point</code>), The Android Studio show me the this warning and debugging was so slow...
By <code>removing this Break-Point</code> my problem solved...
<a href="https://i.stack.imgur.com/S18eL.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/S18eL.png" alt="enter image description here" /></a>
<a href="https://i.stack.imgur.com/5orR1.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/5orR1.png" alt="enter image description here" /></a>

blocks|key|144294|text|视图断点-+(Ctrl+-F8+)删除所有方法断点。在调试模式下重新运行应用程序。其工作f|type|unstyled|depth|inlineStyleRanges|entityRanges|data|144295|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

View Breakpoints - (Ctrl - Shift -F8 )
Remove all method Breakpoints.
rerun the application in debugging mode .
its working f

When I start intellij debugger, it comes the the hint you can see in the screenshot.
the debugger takes a lot of time to start. How to solve this problem?<img src="https://i.stack.imgur.com/pHwTd.png" alt="enter image description here">

Intellij Debugger slow: Method breakpoints may dramatically slow down debugging

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

当我启动intellij调试器时，您可以在屏幕截图中看到提示。调试器需要很长时间才能启动。如何解决这个问题？​

问Intellij调试器慢速:方法断点可能大大减慢调试速度
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Intellij调试器慢速:方法断点可能大大减慢调试速度EN