Intercom, Sentry, and Turbolinks don't play nicely together about intercom-rails HOT 5 OPEN

I had a conversation with support confirming this issue 10 weeks again. Any way I can help move this forward?

from intercom-rails.

Checking in here again. @sduquej Any insight into this or ways that I can help clarify?

from intercom-rails.

Hey @jhubert, really appreciate the detail you've provided here and the repo with repro steps.
I won't have the bandwidth to look into this soon but I'm raising it with the team.

We had seen this error in our own setup (we also use Sentry) about a year ago but we made changes to it and there hasn't been an instance of it in 90+ days. Do you have many users still using IE11?

I know this isn't great but if you haven't already I'd suggest configuring Sentry to ignore this error so that it doesn't eat up your quota :-/ As far as I can tell, there's no detrimental UX other than the annoying error in the IE console. Does this match what you're seeing?

from intercom-rails.

@sduquej Thanks for the follow up. Somehow I missed the notification.

We ignored it in Sentry a while ago. It still comes up as an issue when doing anything in browserstack due to memory overloads. Those listeners stack on top of each other without getting cleared because of Turbolinks. A few pages in and the site can get really slow on older computers. Disabling Intercom fixes it.

The majority of our desktop users are on IE11 because we sell an enterprise product to retailers who are generally not on the latest technologies.

We had seen this error in our own setup (we also use Sentry) about a year ago but we made changes to it and there hasn't been an instance of it in 90+ days

What changes did you make?

from intercom-rails.

@sduquej Any follow up on this? I'd love to get some resolution. I have full control over sentry and turbolinks, but the intercom listeners seem to be the problem and I'm limited to what I can change there.

from intercom-rails.