OOM when using media tracker on a low spec device

[fpitterstv2]

Describe the bug
We are getting OOM reports after playing for very long >6 hours on device model that is ~
The stacktrace is as follow

 Fatal Exception: java.lang.OutOfMemoryError
Failed to allocate a 33554444 byte allocation with 4194152 free bytes and 28MB until OOM
java.util.HashMap.resize (HashMap.java:511)
java.util.HashSet.add (HashSet.java:217)
com.snowplowanalytics.core.media.controller.MediaSessionTrackingStats.updateDurationStats (MediaSessionTrackingStats.java:106) 

To Reproduce
Enable media tracking updating position every second and play some content for several hours

Device informatoin (please complete the following information):
Mostly seeing on a STB with 1GB of RAM running Android 7, but it's showing up on other devices more sporadically

**Other
The set (HashSet) is trying to allocate ~35MB of memory, that doesn't feel like much, but it's probably holding another array of ~30MB for the copy.
We are wondering if we can come up with a different approach to account for the played seconds instead of using a ever growing set?

[mscwilson]

Hi! What version of the tracker is this?

[fpitterstv2]

Thanks for following up, we are using 6.0.1

[fpitterstv2]

We are wondering if there is any chance for this issue to be reviewed?

[mscwilson]

Hi, sorry for not getting back to you earlier. As it stands, it doesn't look like we'll be able to address this issue this quarter, sorry.

If you are a Snowplow customer, consider raising a Support ticket and mention this Issue - that would help us prioritise it in our roadmap.

Alternatively, PRs are very welcome!