We will also be using 2500 APCDC later tonight and splitting it into inputs of 1 APCDC and performing secondary testing if results of users testing deems it necessary.
Regardless we should have answers by morning
UPDATE / NEWS
Ok so user allowed us to watch via live stream and performed quite a few tests before we called it a night..
We only used around 1300 inputs from the user since we had most of our answers before the first send was even initiated.
User has NO coins currently staking and all transactions in log are cleared.
First send (NO INPUTS SELECTED)
After user hits send button client hangs for around 30 seconds and pops transaction error
Second send (NO INPUTS SELECTED)
User attempts to send 400+ inputs. Transaction hangs for around 30 seconds and pops transaction error
Third send (INPUTS SELECTED)
After user hits send button client again hangs for around 30 seconds and pops transaction error
We have user open input screen and although the user had NO selected inputs
the wallet was registering 1 input selected. Overview shows coins staking.
What has happened is that during the lag of creating the transaction for the huge input send inputs continue to stake. The transaction of course cannot occur because the input is no longer available to send. Because the input was set aside for sending but staked during the creation of the transaction the transaction fails. The input is now stuck in memory limbo both registering to the wallet as usable input and staking input and old input is always selected to be in the transaction but no longer exists. This stays persistent until the wallet is restarted.
While this seems like an extremely bad thing it is actually not as bad as one would think. This problem only occurs when you are farming inputs. Most users will never exceed 2 - 300 inputs. Mostly only large bag holders will experience this as there wallet will stake more often than the average user as wallet stake weight is a combination of ALL stakeable inputs.
User restarts wallet
User goes to console (help/debug/console)
reservebalance true ##### (wallet amount, or amount always ready to send)
User sends 400+ inputs
Client hangs for around 30 seconds. Transaction complete
User sends 2x more 400+ input sends
Client hangs for around 30 seconds. Transaction complete
user returns to help/debug/console
reservebalance false
Client hanging to creation of gigantic input transactions will always hang. It does not matter what wallet. The problem is the creation of a stake block while a transaction is occurring.
We will be releasing a fix for this down the road but for now we will just have to ask users to perform proper staking etiquette. While this is currently inconvenient for the input farmers we do not see it affecting the average holder.
While inconvenient setting a reservebalance so coins do not stake & creating smaller transactions is how to get around this problem.
But again this problem only occurs for large input farmers.
This information will be added to the OP.
APCDC will be moved to a new thread SOON.