Hi laszloj,
The upstream bug #5055 mentions "This change has several overlapping
parts. Unfortunately, merging individual parts is both difficult and
likely to cause crashes." Indeed, it looks like several upstream
commits would need backported, involving a non-trivial amount of code
changes. Due to that, it is especially important to define a
reproduction case; otherwise it's hard to know for certain that the
patches are actually fixing the problem, and it will then be challenging
to get this approved for SRU to jammy.
However, we may be able to proceed if you can define the bounds on the
random crashes. How often do the crashes happen? E.g. daily? Every
1000 connection requests? Would you be able to script a workload that
attempts a bunch of connections that triggers the crash on your
hardware?
** Changed in: squid (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1975399
Title:
FATAL FwdState::noteDestinationsEnd exception: opening()
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/squid/+bug/1975399/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
