[tor-bugs] #28195 [Applications/Tor Browser]: TB fails to restart updating 8.5a3
Tor Bug Tracker & Wiki
blackhole at torproject.org
Thu Oct 25 23:30:58 UTC 2018
#28195: TB fails to restart updating 8.5a3
--------------------------------------+-----------------------------------
Reporter: traumschule | Owner: tbb-team
Type: defect | Status: needs_information
Priority: Medium | Milestone:
Component: Applications/Tor Browser | Version:
Severity: Normal | Resolution:
Keywords: tbb-regression | Actual Points:
Parent ID: | Points:
Reviewer: | Sponsor:
--------------------------------------+-----------------------------------
Comment (by traumschule):
All updates are ok, restarting fails. When TB crashes the update is not
invoked and no last-update.log or app.update.log are created. Every
{{{last-update.log}}} file i found ends with
> succeeded
> calling QuitProgressUI
The different errors on exit do not only happen on updates, for example
below with 8.0.3.
My computer is slow, maybe it can be fixed by raising some timeout?
Also folder name seems to have an effect (#28199).
Updating 8.5a3
{{{
AUS:SVC Downloader:onStopRequest - setting state to: pending
AUS:SVC getCanStageUpdates - staging updates is disabled by preference
app.update.staging.enabled
AUS:SVC showUpdateDownloaded - Notifying observers that an update was
downloaded. topic: update-downloaded, status: pending
Discarding onCreatedNavigationTarget for 27: received source tab data
without any created tab data available
[10-25 21:26:31] Torbutton DBUG: Got timer update, but no cookie change.
Discarding onCreatedNavigationTarget for 27: received source tab data
without any created tab data available
[10-25 21:27:31] Torbutton DBUG: Got timer update, but no cookie change.
[10-25 21:27:46] Torbutton INFO: controlPort >> 650 STREAM 51 CLOSED 6
<scrubbed>:443 REASON=DONE
[10-25 21:27:53] Torbutton INFO: controlPort >> 650 STREAM 8 CLOSED 6
<scrubbed>:443 REASON=DONE
[10-25 21:28:31] Torbutton DBUG: Got timer update, but no cookie change.
AUS:SVC getCanApplyUpdates - testing write access
/media/user/tbb/tor/manual/tor-browser_en-
US/Browser/TorBrowser/UpdateInfo/update.test
AUS:SVC getCanApplyUpdates - able to apply updates
AUS:SVC getCanStageUpdates - staging updates is disabled by preference
app.update.staging.enabled
AUS:SVC readStatusFile - status: pending, path: /media/user/tbb/tor/manual
/tor-browser_en-US/Browser/TorBrowser/UpdateInfo/updates/0/update.status
[10-25 21:29:31] Torbutton DBUG: Got timer update, but no cookie change.
<Restart>
Oct 25 21:32:14.000 [notice] Owning controller connection has closed --
exiting now.
Oct 25 21:32:14.000 [notice] Catching signal TERM, exiting cleanly.
Crash Annotation GraphicsCriticalError: |[C0][GFX1-]: Receive IPC close
with reason=AbnormalShutdown (t=473.767) [GFX1-]: Receive IPC close with
reason=AbnormalShutdown
[Child 15153, Chrome_ChildThread] WARNING: pipe error (3): Connection
reset by peer: file /var/tmp/build/firefox-
0c004047822a/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 353
}}}
Exitin 8.0.3 without (visible) update
> FATAL ERROR: AsyncShutdown timeout in profile-before-change Conditions:
[{"name":"Crash Reporter: blocking on
minidumpgeneration.","state":"(none)","filename":"/var/tmp/build/firefox-
858720263bed/ipc/glue/CrashReporterHost.cpp","lineNumber":189,"stack":"Minidump
generation"}] At least one completion condition failed to complete within
a reasonable amount of time. Causing a crash to ensure that we do not
leave the user with an unresponsive process draining resources.
> WARNING: No crash reporter available
> [Parent 6862, Main Thread] ###!!! ABORT: file /var/tmp/build/firefox-
858720263bed/ipc/glue/CrashReporterHost.cpp, line 189
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/28195#comment:8>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
More information about the tor-bugs
mailing list