Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enabled profiler triggers Xdebug on chrome-extension calls #458

Open
Defimas opened this issue Dec 11, 2020 · 2 comments
Open

Enabled profiler triggers Xdebug on chrome-extension calls #458

Defimas opened this issue Dec 11, 2020 · 2 comments

Comments

@Defimas
Copy link

Defimas commented Dec 11, 2020

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
Copy link
Owner

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
Copy link
Author

Defimas commented Dec 21, 2020

Trigger is present.

FYI: I'm using the Laravel integration.

cl

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants