Fix non-linear incrementing of session index

• lasts for as long as sessionCookieTimeout
• doesn’t respect heartbeatDelay (multiple page pings per second despite an heartbeat of 5s)
• possible leads:
  • configHeartBeatTimer might somehow be null here which would cause the callback to happen relentlessly
  • multiple setInterval are set, that could be solved by clearInterval if we mean to have only one at any time

Session indices look like the following when ordered by dvce_created_tstamp:

which would suggest some kind of mad callback.

Tracker initialization looked like the following when the bug occurred:

window._tracker("newTracker", "js", "", {
    appId: "",
    platform: "web",
    post: !0,
    cookieLifetime: 31536e4,
    contexts: {
        webPage: !0,
        performanceTiming: !0
    }
}), 
window._tracker("enableLinkClickTracking", null, !0, !0), 
window._tracker("refreshLinkClickTracking"), 
window._tracker("enableActivityTracking", 5, 5), 
window._tracker("trackPageView"),

[alexanderdean]

Hey @BenFradet - configHeartBeatTimer - why don’t we create a new ticket that puts a guard on the value of this, rather than just && configHeartBeatTimer? I tried a setInterval with “” as the interval and yes it just triggered relentlessly…

[paulboocock]

This has altered considerably since this issue was created, including the addition of guarding to prevent relentless callbacks. Likely no longer an issue.