When PM alerted me about the availability of 15.2.1, I told it to go ahead and update itself. However, the download of the update package (which is a whopping 18 MB) was extremely slow, so I decided to download the installer (which is only 14 MB, very strange) manually via BitTorrent, then exited PM and ran the installer to update. When PM was started again, I checked the About dialog for version info, which was OK, but then I saw that PM has resumed downloading the 15.2.1 update package, despite being updated already.
Obviously, PM should re-check its current version before resuming the download of update package. Additionally, I'd like to have a button to manually cancel the download at any time for any reason.
And why is the update package larger than the installer?
PM resumes downloading of update after manual update
Moderator: trava90
Forum rules
This board is for technical/general usage questions and troubleshooting for the Pale Moon browser only. The main focus here is on Pale Moon on Windows. Please direct your questions that are specific for Linux and Mac to the dedicated boards for those operating systems.
Technical issues and questions not related to the Pale Moon browser should be posted in other boards!
Please keep off-topic and general discussion out of this board, thank you!
This board is for technical/general usage questions and troubleshooting for the Pale Moon browser only. The main focus here is on Pale Moon on Windows. Please direct your questions that are specific for Linux and Mac to the dedicated boards for those operating systems.
Technical issues and questions not related to the Pale Moon browser should be posted in other boards!
Please keep off-topic and general discussion out of this board, thank you!
Re: PM resumes downloading of update after manual update
Normally, you'd let the updater do its job - it will continue to work in the background once started, and you can continue browsing as normal. It was probably slow because a lot of people will be notified these days about their browser update, and the server hosting the update packages is not limitless 
The updater, as-designed by the Firefox team, built in the "background resume" even across browser restarts, but it doesn't include a check for a current version change, as normally people would not install a version in the interim. You can manually remove the pending update, of course, by following these instructions.
The size of the update package is larger than the installer because the update archive format uses a less efficient compression method (bzip) than the installer (7-zip). I will look into making the update packages smaller by providing a "delta" instead, at least for minor releases like this .1 - I've not done this so far as there is a larger risk that the update fails with a partial archive, leaving you with a nonfunctional application.
The updater, as-designed by the Firefox team, built in the "background resume" even across browser restarts, but it doesn't include a check for a current version change, as normally people would not install a version in the interim. You can manually remove the pending update, of course, by following these instructions.
The size of the update package is larger than the installer because the update archive format uses a less efficient compression method (bzip) than the installer (7-zip). I will look into making the update packages smaller by providing a "delta" instead, at least for minor releases like this .1 - I've not done this so far as there is a larger risk that the update fails with a partial archive, leaving you with a nonfunctional application.
"Son, in life you do not fight battles because you expect to win, you fight them merely because they need to be fought." -- Snagglepuss
