Community
Participate
Working Groups
When opening a new experiment, the time range is initialized to [BigBang,BigCrunch] and then updated as the trace events are parsed. The timestamp comparisons are done using TmfTimestamp.compareTo() which uses then normalizes the timestamps using private method synchronize(). And synchronize() throws an ArithmeticException when the scales are ridiculously apart, as is the case when opening an experiment... The fix is to have compareTo() make an early (and obvious) decision when either timestamps is BigBang or BigCrunch.
Created attachment 168431 [details] Arithmetic exception fix
Patch committed.
Released in a past delivery.
Released in a previous delivery.