Thanks for submitting this issue @issacgerges
Can you please provide more information about the "unresponsive" events?
How often do they occur? What browsers/platforms? Under what conditions?
If this is a statistically rare event, we want to prioritize it differently from a major issue

unresponsive is a Chromium concept and happens when the following occurs:

A UI event (like a button click) is sent from the main thread to the renderer thread, which isn't acknowledged (or handled) for 15s.

It's most often caused by synchronous javascript running for that long. In Google Chrome it bubbles to the user in a message that looks something like this, other Chromium embedders handle it in different ways

A very recent browser api, currently in Origin Trial, adds the ability to collect callstacks when this error happens. So after 15s of an unacknowledged input event, the stack is sampled.

We're trialing this API and it's pointing to the following culprit

Too early to say what percentage of users this is, but I can say this is the highest culprit we've detected. A few things to keep in mind

• We recalculate fingerprints on a 5m interval, because our app is often used across multiple tabs, if the fingerprint updates in one, we don't want older tabs sending older fingerprints.
• Browsers are complicated, especially when it comes to scheduling, so its difficult to say that 100% of these are real and this would be true for all apps out there

You likely could improve this by adding a yield back to the browser, but that said, we do not use this part of the fingerprint, and this represents a sizable amount of work for the layout engine. I'd really rather not collect it (an other unused parts) at all.

Thanks!
Please feel free to exclude this source from collection temporarily by patching the collection code, forking the library or any other mechanism that works for you.
I'll mark this as "help_wanted", but cannot provide an ETA about when we'll be to look into this issue.
A reproducible example would greatly accelerate the time to resolution though.

Perfect, do you agree this is a safe place to add these items?

Alternatively could import sources and simply delete items off of it

delete source.fonts

@issacgerges can you please link to this Crash Reporting API? I'm not sure if what I'm finding is what you're using, thanks.

Of course!

https://developer.chrome.com/origintrials/#/view_trial/1049901663130746881
https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/CrashReporting/AddStackToCrashReports.md
https://wicg.github.io/crash-reporting/

Thanks, we've added this to our internal roadmap tracking tool

The 3rd argument here is the list of entropy sources to exclude. You can modify the FingerprintJS source code to add a source name there, or you can create a load() option provide a value for that argument and create a PR.