Enabled profiler triggers Xdebug on chrome-extension calls

[Defimas]

Enabling profiler within the chrome-extension forces Xdebug to trigger profiling (xdebug.start_with_request=trigger) by the extensions own "__clockwork" calls. Througth its polling behavior cachegrinds start to pile up, which i dont think is intended?

[itsgoingd]

Hey, this is definitively not intended. We explicitly remove the trigger cookie when doing metadata requests, can you inspect one of the profiles to make sure it's caused by Clockwork?

[Defimas]

Trigger is present.

FYI: I'm using the Laravel integration.