60 days is an absurd timeout, and I would complain loudly about that...
... If it weren't for the fact that I came back to this bug report to
say that it seems to have very recently been solved. Had to have been in
version 93 or 94, probably 94.
At least, for my own purposes, it seems completely
@Olivier Tilloy, ironically, I'm now seeing the same behavior in version
90. I don't remember if the performance behaved the same way in 89 or
not, but maybe? At any rate, performance of Ubuntu's builds has vastly
improved, even if it's still not quite on the same level as Chrome. I
haven't re-test
@osomon, I don't think this is due to the toolchain version used. I
semi-recently (I don't know how long it's been going on.. Somewhere in the span
of the last 6 months to the last 2 years? Probably more like the past year and
a half, but it feels in some ways longer, in some ways shorter?) foun
Nowhere in either the parent post, nor in the comments, is 'bang for the
buck' even talked about. The entire thing seems to be about choosing a
higher quality default sampling method due to the availability of faster
CPUs. In fact, libsamplerate is never mentioned by name, and src-sinc-.*
are only
Christopher, it is unlikely that any automated tool is ever going to
capture this bug any more than it already has. It is much more
beneficial to find out why it might NOT happen, than why it DOES happen.
What's more, is that it seems that this bug is in the proprietary driver
upstream... So the mo
I'm on 14.10 using an AMD Radeon R9 290X, and having the same issue. The
fact that we're supposed to make new bug reports every time someone's
hardware is slightly different or a new version of Ubuntu comes out is
mildly infuriating, because it makes it seem as if there are fewer
people with this i
6 matches
Mail list logo
