Why does chrome debugging always go to the breakpoint of its own file? how can it be set to get rid of this?

as shown in figure

in debugging embedded iframe pages, iframe.js is not its own file (probably some security check files for chrome), and then always jumps to this breakpoint, even if I haven"t hit the breakpoint, the breakpoint will be removed or entered.

sometimes enter a file called lookup.js. I guess it may be because of chrome security. Is there any way to get rid of these settings to make debugging a little smoother?

how do you solve the problems you encounter?
ps: firefox does not have such a problem.

Javascript chrome-devtools chrome front-end

Feb.28,2021

encounter this problem, I will try to uninstall and reinstall the updated version of chrome,

try to disable all plug-ins, if there is no problem, try to drive back one by one?

generally speaking, either the script implemented by the browser itself or the script, Chrome devtool of the plug-in allows you to blackbox the block of certain scripts. At this time, debugging will not go in

or first find out where the js file comes from

@ front end small slag positive solution.
take a screenshot:

Previous: Electron pack vue?

Next: Why is there no WXMiniProgramObject? in ios Wechat sdk?