search

agusantoso / harviewer

Automatically exported from code.google.com/p/harviewer
0 stars 0 forks source link

harviewer throws "Sum of request timings doesn't correspond to the total value" errors #76

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1.Use attached HAR file

What is the expected output? What do you see instead?
Analysis results are not shown. Instead screen is filled with red text, saying 
"HAR Validation Sum of request timings doesn't correspond to the total value: 
http://google.com/ (request.time: 309 vs. sum: 89), request#: 0, parent page: 
page_1"

I guess that happens because Google Chrome (that generated the file by simply 
visiting google.com in anonymous session) does not care about sum of timings to 
match. Probably they just throw off the fractional part that causes sum to be 
less than total time.

If I manually go over the file and replace 'sum' with 'expected sum' then 
harviewer works OK (the only exception is when I had to fix 309 into 89 which 
seems a bit too much to count as a fraction error).

What version of the product are you using? On what operating system?
2.0.15 running on Google Chrome 19 on Ubuntu 10.04 64bit.

www.google.ch.har is original file produced by Google Chrome
www.google.ch-fixed.har is manually fixed file.

Original issue reported on code.google.com by alex...@google.com on 23 Apr 2012 at 3:49

Attachments:

GoogleCodeExporter commented 9 years ago 
Well, yes the sum is obviously wrong in the original HAR file. But shouldn't 
you rather file a bug for Chrome tool?

I don't know what do you want me to fix in HAR Viewer...?

Note that a workaround for you might be switching off the validation by setting 
a "validate" cookie to false, see:
http://code.google.com/p/harviewer/wiki/Customization

Honza

Original comment by odva...@gmail.com on 26 May 2012 at 5:31

GoogleCodeExporter commented 9 years ago 
Sorry, I actually didn't notice that you have the 'validate' checkbox that is 
checked by default. If I uncheck it - it works fine (though, I suppose it 
displays somewhat skewed results, but that's not your fault).

So this bug is a red herring, it's fine to close it with 'working as intended'.

Thank you.

Original comment by alex...@google.com on 31 May 2012 at 8:47

GoogleCodeExporter commented 9 years ago 
Thanks for the update!
Honza

Original comment by odva...@gmail.com on 31 May 2012 at 10:09