[setup topic/libsolv] Crash after incomplete download
Thu Nov 2 19:25:00 GMT 2017
On 11/2/2017 1:22 PM, Jon Turney wrote:
> On 01/11/2017 20:38, Ken Brown wrote:
>> If there is a download failure and the user clicks Yes in response to
>> "Download Incomplete.Â Try again?", then setup will crash.Â The crash
>> occurs at PickView.cc:447 because i->source() is NULL.
> Thanks for finding all these problems!
>> I haven't yet analyzed this in further detail, but the crux of the
>> issue seems to be that we call do_ini_thread a second time without
>> having cleaned out the package database and the libsolv pool.
>> This is probably a symptom of a more general problem, which is that we
>> haven't thought carefully (or at least I haven't) about what happens
>> when we visit certain pages for a second time, after the libsolv pool
>> has been created.
> The fact that this isn't considered at all at the moment makes me wonder
> if it's working correctly in this situation currently.Â But, yeah, I
> agree that packagedb state should be cleared in this case.
> I tried with the attached, but it still segfaults at the same place.
> This seems to be because all the packagedb prep (including
> fixup_source_package_ids) is in OnInit() (which is only called once per
> page, but lazily), rather than OnActivate(), so probably some more
> restructuring is needed there :(
I guess we could move all that prep to OnActivate() but make sure it's
only run when we've gotten to the chooser page from the site page (and
not because the user pressed Back on the prereq page). What about
adding a 'prepped' data member to packagedb and using this to decide
whether to run the prep code?
>> Before I work further on this, I have a UI question.Â Is it really
>> reasonable that we go back to the mirror selection page after
>> "Download incomplete"?Â I understand the rationale, which is that the
>> user might want to try a different mirror after a download failure.
>> But I personally have always found this annoying.Â I would rather just
>> retry the download, which is what the message ("Download Incomplete.
>> Try again?") suggests is going to happen.
> This makes perfect sense to me.
> The path that an unattended install takes out of there is particularly
> convoluted, as well.
> I suspect there's other terribleness in this area, like if you choose
> "No", the incomplete package download is left in the local package cache
> to fail it's checksum check on the next run...
> +packagedb::init ()
> + installeddbread = 0;
> + installeddbver = 0;
> + packages.clear();
> + sourcePackages.clear();
> + categories.clear();
> + solver.clear();
> + basepkg = packageversion();
> + dependencyOrderedPackages.clear();
I think you also need solution.clear(), where the latter does
essentially what SolverSolution::~SolverSolution() does. (Or is it
enough to just set solv = NULL?) Otherwise, solv will be an invalid
pointer when update is next called.
More information about the Cygwin-apps