Skip to content
This repository has been archived by the owner on Feb 23, 2020. It is now read-only.

Invalid solution spam #3

Open
dmarcuse opened this issue Jan 20, 2016 · 2 comments
Open

Invalid solution spam #3

dmarcuse opened this issue Jan 20, 2016 · 2 comments
Assignees
Milestone

Comments

@dmarcuse
Copy link
Owner

Seeing as this bug has persisted from the original version of the Java portion of the code, I'd imagine it's a bug with the OpenCL mining kernel.

@dmarcuse dmarcuse self-assigned this Jan 20, 2016
dmarcuse added a commit that referenced this issue Jan 20, 2016
@dmarcuse
Copy link
Owner Author

Not completely fixed as of 452ca4a, but mitigated.

@dmarcuse dmarcuse reopened this Jan 20, 2016
@dmarcuse dmarcuse added this to the First Release milestone Jan 27, 2016
@empirebuilder1
Copy link

empirebuilder1 commented Oct 6, 2016

It seems to me that the miner kernel isn't clearing it's solution cache after finding a valid solution. When it rolls over to the next block, it for some reason submits all the solutions it was previously working on. This varies greatly, but seems to get worse the longer an easy block is worked on. Example: This block was worked on for about 5 minutes by my GPU at work level 98711. It spams a bunch of rejected solutions before eventually continuing on as normal.

I don't know much about how it's coded (nor do I really understand enough to read it), but maybe memory needs to be cleaned up when a valid solution is found before continuing to the next block. I'm not even sure this is relevant to the original issue here, and if it's not I'll start a different thread.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants