1410103 - cannot submit crash report

Status: RESOLVED WONTFIX

(Toolkit :: Crash Reporting, defect)

Description

[Lu Wei]

User Agent: Mozilla/5.0 (Windows NT 5.1; rv:52.0) Gecko/20100101 Firefox/52.0
Build ID: 20170921064520

Steps to reproduce:

Firefox crashed, and submitting crash report dialogue appeared


Actual results:

I clicked submit, and after sometime it said something like "failed". Re-openning Firefox, in trouble shooting information the failed to submit reports are there, and clicking them one by one makes them submitted.


Expected results:

They should be submitted in the first place.

Comment 1

[Lu Wei]

submit.log:
[09/09/16 09:41:43] Crash report submitted successfully
[09/18/16 16:45:24] Crash report submitted successfully
[Tue Apr 25 09:08:03 2017] Crash report submission failed: An error occurred in the secure channel support
[Tue Apr 25 21:42:47 2017] Crash report submission failed: An error occurred in the secure channel support
[Sun Apr 30 09:46:31 2017] Crash report submission failed: The server name or address could not be resolved
[Wed May 10 15:34:26 2017] Crash report submission failed: An error occurred in the secure channel support
[Fri May 19 09:21:38 2017] Crash report submission failed: The server name or address could not be resolved
[Fri Jun 16 09:26:35 2017] Crash report submission failed: An error occurred in the secure channel support
[Fri Jul  7 18:39:41 2017] Crash report submission failed: An error occurred in the secure channel support
[Thu Jul 27 14:33:11 2017] Crash report submission failed: The server name or address could not be resolved
[Tue Sep  5 16:38:15 2017] Crash report submission failed: An error occurred in the secure channel support
[Thu Sep 21 10:05:55 2017] Crash report submission failed: An error occurred in the secure channel support
[Wed Oct  4 21:24:13 2017] Crash report submission failed: An error occurred in the secure channel support
[Tue Oct 10 13:15:25 2017] Crash report submission failed: The connection with the server was reset
[Thu Oct 19 22:13:15 2017] Crash report submission failed: An error occurred in the secure channel support

So the bug appears since 2017

Comment 2

[Lu Wei]

Attachment: 1.pcapng

Following Wayne Mery's suggestion I downloaded Nightly tester tools and made test crash. Then I caught the network flow. 
First was caught in a company proxy environment:

CONNECT crash-reports.mozilla.com:443 HTTP/1.0
User-Agent: Breakpad/1.0 (Windows)
Host: crash-reports.mozilla.com:443
Content-Length: 0
Proxy-Connection: Keep-Alive
Pragma: no-cache

HTTP/1.0 200 OK
Server: FreeProxy/4.50
Date: Thu, 26 Oct 2017 08:04:45 GMT
Content-Type: application/octet-stream

....H...D..Y..1Gv...:.q....bO]..z..jF'...U
........
...d.b.........c...............(

CONNECT crash-reports.mozilla.com:443 HTTP/1.0
User-Agent: Breakpad/1.0 (Windows)
Host: crash-reports.mozilla.com:443
Content-Length: 0
Proxy-Connection: Keep-Alive
Pragma: no-cache

HTTP/1.0 200 OK
Server: FreeProxy/4.50
Date: Thu, 26 Oct 2017 08:04:46 GMT
Content-Type: application/octet-stream

....C...?..Y..1&....p..n..P..F`.=JI.y.%............
...d.b.........c..........(

CONNECT crash-reports.mozilla.com:443 HTTP/1.0
User-Agent: Breakpad/1.0 (Windows)
Host: crash-reports.mozilla.com:443
Content-Length: 0
Proxy-Connection: Keep-Alive
Pragma: no-cache

HTTP/1.0 200 OK
Server: FreeProxy/4.50
Date: Thu, 26 Oct 2017 08:04:47 GMT
Content-Type: application/octet-stream

Second was caught at home no proxy environment. Wireshark file is saved as attachment uploaded.

And I find that crash reporting component uses IE proxy setting, not the one in Firefox. Should this be another bug?

Comment 3

[Wayne Mery (:wsmwk)]

Is the exact text "There was a problem submitting your report" ?

Comment 4

[Lu Wei]

(In reply to Wayne Mery (:wsmwk) from comment #3)

Is the exact text "There was a problem submitting your report" ?

Yes.

For the bug, based on improved knowledge these years, I think the problem just lies in "crash reporting component uses IE proxy setting, not the one in Firefox", because it implies that crash reporting is independent of Firefox and uses OS network component to connect (which is preferred), so that in the record 1.pcapng, it connects to bug server with TLS 1.0, which is characteristic of WinXp without post-SP3 POSReady patches (KB4019276 specifically), then refused by bug server that may raised the security level above TLS 1.0 at some time before April 2017. And since Firefox supports TLS 1.2 natively then the bug reports could be submitted within Firefox.

Although my winxp machine had been patched to support TLS 1.2, so I believe that bug should not occur to me now, yet with bug server raise security level above TLS 1.2 someday it will occur again. Since winxp is not supported anyway, making crash report meaningless, and I have switched to more updated Fx52 variant -- Serpent 52 browser (I suggest everyone on windows xp port to it) , this bug could be resolved to wontfix.