1191802 - Break on add-on

Status: NEW

(DevTools :: Debugger, enhancement, P5)

Description

[David Teller [:Yoric] - still alive but not very active]

I'd like to be able to add a breakpoint that's triggered once any code from that add-on is executed. This would help me (and probably add-on developers) find out why some add-on is flagged as slow.

Comment 1

[Andreas Wagner [:TheOne] [use NI]]

Can you tell us why chrome debugging does not fulfill this use-case?

Comment 2

[David Teller [:Yoric] - still alive but not very active]

I may be missing something, but I don't think there is a way to ask chrome debugging to break on _any_ use of an add-on, is there? Again, that's for add-ons which are somehow triggered by Firefox, but assuming that I don't know the entry point.

Comment 3

[Andreas Wagner [:TheOne] [use NI]]

Ah, I understand now, thank you for the clarification. Being familiar with add-ons (and therefore biased) I'm asking myself what the cases are where you have not the slightest clue about where to start debugging.

I don't know about the "slow" flag for add-ons, but we should have docs about what code it triggers, and if not, we should write some :)

Lmk, if this is going too far for this bug and we can continue this somewhere else.

Comment 4

[David Teller [:Yoric] - still alive but not very active]

Actually, my current example is an add-on that's just ~100 loc, which shouldn't be triggered by Firefox but apparently is. I suspect a bug in or around Jetpack.

As for the "slow" flag for add-ons, I'm the one currently developing it :)