Sieve Client Thread

[Nuri]

The same happens here. That's strange, because the client works for higher p values. So, it's not something to do with a boundary etc.

For some reason, it stucks between 666000078456017 and 666000078456023.

I dunno why it happens, but it will run again if you set pmin to 666000078456024.


PS: Death, I also checked the range with one of our older clients (SoBsieve 1.10). There's no factor at that specific point.