On Tue, Sep 14, 2021 at 10:19:41AM +0100, Stuart Henderson wrote:
> Maybe relevant: https://github.com/arvidn/libtorrent/issues/6405
I tried updating libtorrent-rasterbar to 1.2.14 and bumping
TORRENT_{READ,WRITE}_HANDLER_MAX_SIZE by 16 bytes to match what was
discussed in that thread for libtorrent 2.0.x. I still get the same
abort (also the bogus pointer (double free?) seen in the backtrace
suggests that the problem is a different one.
>
> Users of other software that uses boost: please test snapshots ASAP and
> report back if there are recent problems.
>
> --
> Sent from a phone, apologies for poor formatting.
>
> On 14 September 2021 03:24:53 "Elias M. Mariani" <marianiel...@gmail.com>
> wrote:
> > Thanks for the links Theo, I didn't know about those mirrors with the
> > previous builds.
> > Yep, the problem seems to lie with the boost update from 1.76 to 1.77.
> > Using 1.76 works OK.
> >
> > On Mon, Sep 13, 2021 at 6:28 PM Theo Buehler <t...@theobuehler.org> wrote:
> > On Mon, Sep 13, 2021 at 05:55:51PM -0300, Elias M. Mariani wrote:
> > > I should add some more info:
> > > - I tested this on amd64, qbittorrent 4.3.8 was working OK a week or so
> > > ago. I just tested deluge because it uses the same libraries.
> > > - Reproduce: pkg_add qbittorrent on -current, run qbittorrent. The same
> > > applies for deluge.
> > > I tested both in a vanilla -current machine just to be sure that nothing
> > > was on the way...
> >
> > There was a similar report on bugs (Sep 9):
> > https://marc.info/?l=openbsd-bugs&m=163120864431955&w=2
> >
> > The timeframe of "one week or so" and the trace make it likely that it
> > is the boost 1.77 update.
> >
> > This is the last snapshot with boost-1.76p0:
> > https://ftp.hostserver.de/archive/2021-09-05-0105/snapshots/
> > If that works and the next snapshot with boost-1.77 is broken...
> > https://ftp.hostserver.de/archive/2021-09-06-0105/snapshots/
>
