Sites log button isn't showing the true last 10 lines of log file

RESOLVED INCOMPLETE

Status

()

Firefox
Untriaged
--
minor
RESOLVED INCOMPLETE
2 years ago
2 years ago

People

(Reporter: Martin Grossman, Unassigned)

Tracking

({regression, regressionwindow-wanted, testcase-wanted})

49 Branch
x86
Windows 7
regression, regressionwindow-wanted, testcase-wanted
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

2 years ago
User Agent: Mozilla/5.0 (Windows NT 6.1; rv:49.0) Gecko/20100101 Firefox/49.0
Build ID: 20160922113459

Steps to reproduce:

On a website a button marked LOG is displayed which should show the last 10 lines of my log file.  I have tried a lot other browsers (including IE) and they all work as expected.  Only my true love "Firefox" truncates the sent file prematurely and then displays the last 10 lines.   This causes the last 10 lines to be 20-30 minutes old.
Below I'll show what Firefox displays, and what IE displays done within second of each other.   Sorry I can't let you reproduce it without giving my login/password.
PS I have used Wireshark and noticed that the data received by my system is the same in each case.  Its as if Firefox's receive buffer is full and the last 20-30 minutes are lost and then the last 10 lines are displayed.

In IE what is displayed is the last 10 lines, and if I select from the last line upto the first line (using the scroll bar), paste into notepad and save it the file is 12301 bytes long.  If I do the exact same thing in Firefox (ie select the whole buffer, save to a file) the file size varies from 9080 to 9449 bytes long.  The site always sends exactly the last 12.5K of data.



Actual results:

This is displayed by Firefox
[2016-10-16 07:23 EDT] 18719 msgs recv'd from dump1090-fa (89 in last 5m); 18719 msgs sent to FlightAware
[2016-10-16 07:28 EDT] mlat-client(754): Receiver status: connected
[2016-10-16 07:28 EDT] mlat-client(754): Server status: synchronized with 55 nearby receivers
[2016-10-16 07:28 EDT] mlat-client(754): Receiver: 18.4 msg/s received 5.9 msg/s processed (32%)
[2016-10-16 07:28 EDT] mlat-client(754): Server: 0.1 kB/s from server 0.0kB/s TCP to server 0.1kB/s UDP to server
[2016-10-16 07:28 EDT] mlat-client(754): Results: 43.4 positions/minute
[2016-10-16 07:28 EDT] mlat-client(754): Aircraft: 0 of 0 Mode S, 3 of 3 ADS-B used
[2016-10-16 07:28 EDT] 18803 msgs recv'd from dump1090-fa (84 in last 5m); 18803 msgs sent to FlightAware
[2016-10-16 07:33 EDT] 18909 msgs recv'd from dump1090-fa (106 in last 5m); 18909 msgs sent to FlightAware
[2016-10-16 07:38 EDT] 19020 msgs recv'd from dump1090-fa (111 in last 5m); 19020 msgs sent to FlightAware
[2016-10-16 07:43 EDT] mlat-client(754): Receiver status: connected
[2016-10-16 07:43 EDT] mlat-client(754): Server status: synchronized with 61 nearby receivers
[2016-10-16 07:43 EDT] mlat-client(754): Receiver: 24.9 msg/s received 8.1 msg/s processed (32%)
[2016-10-16 07:43 EDT] mlat-client(754): Server: 0.1 kB/s from server 0.0kB/s TCP to server 0.1kB/s UDP to server
[2016-10-16 07:43 EDT] mlat-client(754): Results: 44.3 positions/minute
[2016-10-16 07:43 EDT] mlat-client(754): Aircraft: 3 of 9 Mode S, 3 of 3 ADS-B used
[2016-10-16 07:43 EDT] 19177 msgs recv'd from dump1090-fa (157 in last 5m); 19177 msgs sent to FlightAware
[2016-10-16 07:48 EDT] 19409 msgs recv'd from dump1090-fa (232 in last 5m); 19409 msgs sent to FlightAware
[2016-10-16 07:53 EDT] 19599 msgs recv'd from dump1090-fa (190 in last 5m); 19599 msgs sent to FlightAware
[2016-10-16 07:58 EDT] 19788 msgs recv'd from dump1090-fa (189 in last 5m); 19788 msgs sent to FlightAware
[2016-10-16 07:58 EDT] mlat-client(754): Receiver status: connected
[2016-10-16 07:58 EDT] mlat-client(754): Server status: synchronized with 75 nearby receivers
[2016-10-16 07:58 EDT] mlat-client(754): Receiver: 56.3 msg/s received 15.1 msg/s processed (27%)
[2016-10-16 07:58 EDT] mlat-client(754): Server: 0.3 kB/s from server 0.0kB/s TCP to server 0.2kB/s UDP to server
[2016-10-16 07:58 EDT] mlat-client(754): Results: 143.0 positions/minute
[2016-10-16 07:58 EDT] mlat-client(754): Aircraft: 3 of 4 Mode S, 4 of 4 ADS-B used
[2016-10-16 08:03 EDT] 19883 msgs recv'd from dump1090-fa (95 in last 5m); 19883 msgs sent to FlightAware
[2016-10-16 08:08 EDT] 19954 msgs recv'd from dump1090-fa (71 in last 5m); 19954 msgs sent to FlightAware
[2016-10-16 08:13 EDT] 20115 msgs recv'd from dump1090-fa (161 in last 5m); 20115 msgs sent to FlightAware
[2016-10-16 08:13 EDT] mlat-client(754): Receiver status: connected
[2016-10-16 08:13 EDT] mlat-client(754): Server status: synchronized with 58 nearby receivers
[2016-10-16 08:13 EDT] mlat-client(754): Receiver: 22.5 msg/s received 6.4 msg/s processed (29%)
[2016-10-16 08:13 EDT] mlat-client(754): Server: 0.1 kB/s from server 0.0kB/s TCP to server 0.1kB/s UDP to server
[2016-10-16 08:13 EDT] mlat-client(754): Results: 38.7 positions/minute
[2016-10-16 08:13 EDT] mlat-client(754): Aircraft: 2 of 5 Mode S, 3 of 3 ADS-B used
[2016-10-16 08:18 EDT] 20251 msgs recv'd from dump1090-fa (136 in last 5m); 20251 msgs sent to FlightAware
[2016-10-16 08:23 EDT] 20442 msgs recv'd from dump1090-fa (191 in last 5m); 20442 msgs sent to FlightAware
[2016-10-16 08:28 EDT] 20611 msgs recv'd from dump1090-fa (169 in last 5m); 20611 msgs sent to FlightAware
[2016-10-16 08:28 EDT] mlat-client(754): Receiver status: connected
[2016-10-16 08:28 EDT] mlat-client(754): Server status: synchronized with 71 nearby receivers
[2016-10-16 08:28 EDT] mlat-client(754): Receiver: 38.5 msg/s received 12.4 msg/s processed (32%)
[2016-10-16 08:28 EDT] mlat-client(754): Server: 0.2 kB/s from server 0.0kB/s TCP to server 0.2kB/s UDP to server
[2016-10-16 08:28 EDT] mlat-client(754): Results: 77.6 positions/minute
[2016-10-16 08:28 EDT] mlat-client(754): Aircraft: 3 of 8 Mode S, 3 of 3 ADS-B used
[2016-10-16 08:33 EDT] 20781 msgs recv'd from dump1090-fa (170 in last 5m); 20781 msgs sent to FlightAware
[2016-10-16 08:38 EDT] 20998 msgs recv'd from dump1090-fa (217 in last 5m); 20998 msgs sent to FlightAware
[2016-10-16 08:43 EDT] 21115 msgs recv'd from dump1090-fa (117 in last 5m); 21115 msgs sent to FlightAware
[2016-10-16 08:43 EDT] mlat-client(754): Receiver status: connected
[2016-10-16 08:43 EDT] mlat-client(754): Server status: not synchronized with any nearby receivers
[2016-10-16 08:43 EDT] mlat-client(754): Receiver: 34.5 msg/s received 9.2 msg/s processed (27%)
[2016-10-16 08:43 EDT] mlat-client(754): Server: 0.3 kB/s from server 0.0kB/s TCP to server 0.1kB/s UDP to server
[2016-10-16 08:43 EDT] mlat-client(754): Results: 126.1 positions/minute
[2016-10-16 08:43 EDT] mlat-client(754): Aircraft: 2 of 8 Mode S, 1 of 1 ADS-B used
[2016-10-16 08:48 EDT] 21200 msgs recv'd from dump1090-fa (85 in last 5m); 21200 msgs sent to FlightAware
[2016-10-16 08:53 EDT] 21306 msgs recv'd from dump1090-fa (106 in last 5m); 21306 msgs sent to FlightAware
[2016-10-16 08:58 EDT] 21488 msgs recv'd from dump1090-fa (182 in last 5m); 21488 msgs sent to FlightAware
[2016-10-16 08:58 EDT] mlat-client(754): Receiver status: connected
[2016-10-16 08:58 EDT] mlat-client(754): Server status: synchronized with 69 nearby receivers
[2016-10-16 08:58 EDT] mlat-client(754): Receiver: 24.4 msg/s received 7.5 msg/s processed (31%)
[2016-10-16 08:58 EDT] mlat-client(754): Server: 0.2 kB/s from server 0.0kB/s TCP to server 0.1kB/s UDP to server
[2016-10-16 08:58 EDT] mlat-client(754): Results: 70.5 positions/minute
[2016-10-16 08:58 EDT] mlat-client(754): Aircraft: 2 of 4 Mode S, 4 of 4 ADS-B used
[2016-10-16 09:03 EDT] 21655 msgs recv'd from dump1090-fa (167 in last 5m); 21655 msgs sent to FlightAware
[2016-10-16 09:08 EDT] 21850 msgs recv'd from dump1090-fa (195 in last 5m); 21850 msgs sent to FlightAware
[2016-10-16 09:13 EDT] 21967 msgs recv'd from dump1090-fa (117 in last 5m); 21967 msgs sent to FlightAware
[2016-10-16 09:13 EDT] mlat-client(754): Receiver status: connected
[2016-10-16 09:13 EDT] mlat-client(754): Server status: synchronized with 32 nearby receivers
[2016-10-16 09:13 EDT] mlat-client(754): Receiver: 30.3 msg/s received 10.0 msg/s processed (33%)
[2016-10-16 09:13 EDT] mlat-client(754): Server: 0.1 kB/s from server 0.0kB/s TCP to server 0.2kB/s UDP to server
[2016-10-16 09:13 EDT] mlat-client(754): Results: 43.7 positions/minute
[2016-10-16 09:13 EDT] mlat-client(754): Aircraft: 2 of 6 Mode S, 2 of 2 ADS-B used
[2016-10-16 09:18 EDT] 22064 msgs recv'd from dump1090-fa (97 in last 5m); 22064 msgs sent to FlightAware
[2016-10-16 09:23 EDT] 22306 msgs recv'd from dump1090-fa (242 in last 5m); 22306 msgs sent to FlightAware
[2016-10-16 09:28 EDT] 22440 msgs recv'd from dump1090-fa (134 in last 5m); 22440 msgs sent to FlightAware
[2016-10-16 09:28 EDT] mlat-client(754): Receiver status: connected
[2016-10-16 09:28 EDT] mlat-client(754): Server status: synchronized with 53 nearby receivers
[2016-10-16 09:28 EDT] mlat-client(754): Receiver: 29.9 msg/s received 9.1 msg/s processed (30%)
[2016-10-16 09:28 EDT] mlat-client(754): Server: 0.2 kB/s from server 0.0kB/s TCP to server 0.1kB/s UDP to server
[2016-10-16 09:28 EDT] mlat-client(754): Results: 68.1 positions/minute
[2016-10-16 09:28 EDT] mlat-client(754): Aircraft: 1 of 6 Mode S, 1 of 1 ADS-B used
[2016-10-16 09:33 EDT] 22575 msgs recv'd from dump1090-fa (135 in last 5m); 22575 msgs sent to FlightAware
[2016-10-16 09:38 EDT] 22777 msgs recv'd from dump1090-fa (202 in last 5m); 22777 msgs sent to FlightAware
[2016-10-16 09:43 EDT] 23038 msgs recv'd from dump1090-fa (261 in last 5m); 23038 msgs sent to FlightAware
[2016-10-16 09:43 EDT] mlat-client(754): Receiver status: connected
[2016-10-16 09:43 EDT] mlat-client(754): Server status: synchronized with 51 nearby receivers
[2016-10-16 09:43 EDT] mlat-client(754): Receiver: 39.9 msg/s received 10.7 msg/s processed (27%)
[2016-10-16 09:43 EDT] mlat-client(754): Server: 0.2 kB/s from server 0.0kB/s TCP to server 0.2kB/s UDP to server
[2016-10-16 09:43 EDT] mlat-client(754): Results: 93.3 positions/minute
[2016-10-16 09:43 EDT] mlat-client(754): Aircraft: 2 of 15 Mode S, 3 of 3 ADS-B used
[2016-10-16 09:48 EDT] 23220 msgs recv'd from dump1090-fa (182 in last 5m); 23220 msgs sent to FlightAware
[2016-10-16 09:53 EDT] 23336 msgs recv'd from dump1090-fa (116 in last 5m); 23336 msgs sent to FlightAware
[2016-10-16 09:58 EDT] 23437 msgs recv'd from dump1090-fa (101 in last 5m); 23437 msgs sent to FlightAware
[2016-10-16 09:58 EDT] mlat-client(754): Receiver status: connected
[2016-10-16 09:58 EDT] mlat-client(754): Server status: synchronized with 7 nearby receivers
[2016-10-16 09:58 EDT] mlat-client(754): Receiver: 35.1 msg/s received 10.7 msg/s processed (30%)



Expected results:

This is whats displayed by IE
[2016-10-16 09:58 EDT] mlat-client(754): Aircraft: 2 of 7 Mode S, 1 of 1 ADS-B used
[2016-10-16 10:03 EDT] 23554 msgs recv'd from dump1090-fa (117 in last 5m); 23554 msgs sent to FlightAware
[2016-10-16 10:08 EDT] 23723 msgs recv'd from dump1090-fa (169 in last 5m); 23723 msgs sent to FlightAware
[2016-10-16 10:13 EDT] 23853 msgs recv'd from dump1090-fa (130 in last 5m); 23853 msgs sent to FlightAware
[2016-10-16 10:13 EDT] mlat-client(754): Receiver status: connected
[2016-10-16 10:13 EDT] mlat-client(754): Server status: not synchronized with any nearby receivers
[2016-10-16 10:13 EDT] mlat-client(754): Receiver: 24.3 msg/s received 6.0 msg/s processed (25%)
[2016-10-16 10:13 EDT] mlat-client(754): Server: 0.2 kB/s from server 0.0kB/s TCP to server 0.1kB/s UDP to server
[2016-10-16 10:13 EDT] mlat-client(754): Results: 70.3 positions/minute
[2016-10-16 10:13 EDT] mlat-client(754): Aircraft: 3 of 4 Mode S, 1 of 2 ADS-B used
[2016-10-16 10:18 EDT] 23957 msgs recv'd from dump1090-fa (104 in last 5m); 23957 msgs sent to FlightAware
(Reporter)

Comment 1

2 years ago
Sorry,  In the above section "Actual results:"  I pasted the whole buffer when it
should have been just the last 10 lines (ie without scrolling"
Severity: normal → minor
OS: Unspecified → Windows 7
Hardware: Unspecified → x86

Comment 2

2 years ago
(In reply to Martin Grossman from comment #0)
> On a website a button marked LOG is displayed which should show the last 10
> lines of my log file.  I have tried a lot other browsers (including IE) and
> they all work as expected.  Only my true love "Firefox" truncates the sent
> file prematurely and then displays the last 10 lines.   This causes the last
> 10 lines to be 20-30 minutes old.

Can you please provide a minimal self-contained test case that allows others to reproduce the problem? Thanks in advance!

Updated

2 years ago
Flags: needinfo?(mardor)
Keywords: testcase-wanted
(Reporter)

Comment 3

2 years ago
Sorry, I have no idea how to write a minimal self-contained test case.
Do you have any secure way I could send you my login/password so you could
see whats broken?
In a nutshell, the web site always sends the last 12.5K of a log file.
In all browsers the whole 12.5K is displayed in a small window containing
the last 10 lines and scroll bars to see the rest of the data.  In Firefox
its truncating the data between 9K and 10K and then displaying the last 10
lines and a scroll bar to see the previous data.
I have verified with Wireshark that in each case all 12K is being sent from
server to browser.

PS I have tried Firefox version 47 and upgraded yesterday to version 49.
Flags: needinfo?(mardor)

Comment 4

2 years ago
You can create a guest/testing account and send it by email (just right click on name to get the email address).
(Reporter)

Comment 5

2 years ago
If I create a guest/test account and that account does not start sending ADS-B data then there will be no Log button available :-(

Here is (I think) the relevant html code for the Log button.
PS I have no idea what window.loadlogs does :-(

<fieldset>
    <legend data-default-visible="false" data-refresh-logs="true">
      <button type="button" class="collapseIndicator"><i class="fa fa-caret-right"></i></button>
      Log
    </legend>
  <div style="display:block; width:100%; text-align:right; margin-bottom: 5px;">
  <em style="color:#B2B2B2">Note: this log pane refreshes itself automatically every 15 seconds</em>
  &nbsp;&nbsp;
  <button class="blue button" onclick="window.loadLogs();return false;">
   Refresh log contents &rarr</button>
  </div>

  <div class="log_container" data-facility="fAT-b827eb95218b" data-nearby-airport="KBED">Loading...
  </div>
</fieldset>
Hi Martin, on what website does this issue occur? Thanks.
Flags: needinfo?(mardor)
(Reporter)

Comment 7

2 years ago
Here is the website...
https://flightaware.com/adsb/stats/user/MartinGrossman#1997

BUT you will not see the LOG button unless you are logged in with
a valid account AND have their Raspberry PI program "Piaware" running.
Flags: needinfo?(mardor)
Component: Untriaged → Networking
Product: Firefox → Core
Hi Martin,

Can you try performing a mozregression on this issue? Without having login details available, it's difficult to figure out where to put this bug or where it could be at fault, but I think this would be a good start to figure out the problem.
Flags: needinfo?(mardor)
Keywords: regression, regressionwindow-wanted
According to comment 3, all data crosses the wire. No real evidence this is a networking bug so far (could be many things, networking only one of them). Popping back to untriaged.
Component: Networking → Untriaged
Product: Core → Firefox

Comment 10

2 years ago
Martin, any update about the search for a regression range in Firefox with the tool mozrgression?
Closing due to lack of response. If you feel this issue is still pertinent, please provide the info requested in Comment 10. Thanks!
Status: UNCONFIRMED → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → INCOMPLETE
(Reporter)

Comment 12

2 years ago
I cannot do any reqression testing since I have no idea if this ever worked correctly.
I have submitted textual data showing that it works in all other browsers except firefox.
Status: RESOLVED → UNCONFIRMED
Flags: needinfo?(mardor)
Resolution: INCOMPLETE → ---
Unfortunately, there's not much we can do with the information we're provided. There's no way we can confirm this issue and there's no way to tell if this issue can ever be resolved.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 2 years ago2 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.