LLL.Player sometimes records events resulting in a 'negative' session length

[ShinNoNoir]

Cause: Unknown

Example of a player's .eventlog:

[
    [1410601854.8559999, 'PLAYING', 0.0, 0.0],
    [1410601879.102, 'TICK', 1.54, 1.54],
    [1410601879.2579999, 'PLAYING', 1374.8900000000001, 1.54],
    [1410601879.3640001, 'PAUSED', 1.54, 1.54],
    [1410601879.6059999, 'PLAYING', 1374.8900000000001, 1374.8900000000001],
    [1410601884.2720001, 'TICK', 1374.8900000000001, 1374.8900000000001],
    [1410601884.493, 'PLAYING', 3415.7399999999998, 1374.8900000000001],
    [1410601888.0669999, 'TICK', 3415.7399999999998, 3415.7399999999998],
    [1410601888.109, 'PLAYING', 5134.3500000000004, 3415.7399999999998],
    [1410601889.7119999, 'TICK', 5134.3500000000004, 5134.3500000000004],
    [1410601889.75, 'PLAYING', 9130.6100000000006, 5134.3500000000004],
    [1410601894.457, 'TICK', 9130.6100000000006, 9130.6100000000006],
    [1410601894.6229999, 'PLAYING', 14608.67, 9130.6100000000006],
    [1410601904.112, 'TICK', 14608.67, 14608.67]
 ]

Hypothesis 1: Bug in event log simplification code (

commonhit/lllight.js

Line 163 in 0a058e5

if (this.eventlog.length >= 2) {

).

Hypothesis 2: Bug in YouTube player API reporting incorrect playback position?

[ShinNoNoir]

Idea to further investigate: Keep track of the non-simplified event log and echo this to a debug field as soon as a negative playback segment is being constructed.