[http trace] the http trace view will cause browser memory raise

is about http trace problem, in /instances/219a2939eb94/httptrace view, the browser memory usage will raise and page dead in seconds.

chartData is too big…

so i have make some log output on this loop from traces-chart.vue,

let i = 0;
for (let time = Math.floor(oldest.valueOf() / interval) * interval; time < now; time += interval) {
          i++;
          console.log('loop', i);
          console.log('loop --- time', time);
          console.log('loop --- now', now);
       //...
}

i found it is because the timestamp unit of now and time is different so the loop will run many times till the page dead.

the time is come from server’s httptrace response, something like this…, timestamp unit is second

[hirohe]

i try debug step by step… find out httptrace.timestamp is serialized in com.fasterxml.jackson.datatype.jsr310.ser.InstantSerializerBase#serialize

if (useTimestamp(provider)) { // pass when serialization.write-dates-as-timestamps is true
    if (useNanoseconds(provider)) { // pass by default,
        // have to set serialization.write-date-timestamps-as-nanoseconds to false,
        // to prevent timestamp format in seconds unit
        generator.writeNumber(DecimalUtils.toBigDecimal(
                getEpochSeconds.applyAsLong(value), getNanoseconds.applyAsInt(value)
        ));
        return;
    }
    generator.writeNumber(getEpochMillis.applyAsLong(value));
    return;
}

• without any spring.jackson.serialization config. httptrace.timestamp is ISO format

• with spring.jackson.serialization.write-dates-as-timestamps: true, httptrace.timestamp is timestamp of second unit

• with spring.jackson.serialization.write-dates-as-timestamps: true and spring.jackson.serialization.write-date-timestamps-as-nanoseconds: false httptrace.timestamp is timestamp of miliisecond unit

three different format will happen🤔

[dazer007]

Thank you, I have encountered such a problem…