Geoffrey McRae

Sorry, I forgot to come back and update this. Yes, I determined the same, the code is correct here. @easyteacher is this on the station or the ap? Disabling it...

so the workaround is to limit the throughput... not really an option either.

Not sure how issue #576 relates to this one, there is no kernel oops generated by either the repeat of old frames or the eventual device failure at high throughputs.

Again, I am NOT looking for a hacky workaround, but a fix. Please stop polluting this issue with junk.

Why are you guys still posting to this issue? I have an EXACT error reported of duplicated frames! Not just some random dropout under high loads. Unless you're seeing the...

I believe this issue is fixed in bleeding edge, can you please update and test?

> You are talking about stratum server bans, right? Yes > With the current code, only 127.0.0.1 is whitelisted, so you can run xmrig-proxy and p2pool on the same host...

All this change does is move the `x[FRAME_SIZE];` from a local on the stack to static memory allowing the state to be retained between calls, there is no change to...

It can still be done exactly the same, what you are asking for can still be achieved with it, the difference is that we can have a ring buffer that...

> Since your changes introduce an internal buffer No it does not, read the source! This buffer already exists except it's scoped `LOCALLY` on the `STACK`, there is NO additional...