The only thing you can try and do is send your entire balance to yourself (so it's combined into 1 input). It will hang for a LONG LONG time, i had 50k some inputs that took hours sitting frozen. If your mining at a pool I would suggest raising your payout threshold. Or at least enabling coin control & combining small inputs occasionally.(DONT use coin control right now, youll freeze for hours just to freeze again when you start selecting from your inputs)  if your on linux you could always compile the daemon and issue the sendtoaddress command to the daemon through command line, may help on resources and not take so long to send...

Depending on your system combining/sending a huge amount of inputs could take days. You got popcorn and some good cable tv its gonna take a while

sorry i couldnt help :p

do you see anything in your debug.log taht might shed any light ??
should be in your data directory with your wallet etc.

no idea if this will help.
increasing your maxconnections
.
either edit the QubitCoins.conf (i dont know the correct file name la capital letters)

maxconnections=1000

or open the qt using a terminal window and add arguments
(can drag/drop qt onto terminal window to get file location)
open terminal (applications/utilities)
>open /file/location/qubitcoin-qt.app --args -maxconnections=1000

..

try not to let your computer be doing anything else
seems like it needs full attention

another possible is using ulimit.
it sets system limits on processes, so you'd raise the limit, then open qt

i'm not that familiar with it, but on OSX 10.8

terminal window
> sudo ulimit -n 10000
password : [enter your user password here]
> open /file/location/qubitcoin-qt.app --args -maxconnections=1000


note: this only effects processes done within this session (terminal window), so you need to open qt within the window, and when you close window that setting will disappear (except for the qt that might still be running - until you close that too).


..
in case you're wondering why maxconnections might help, when maxconnections seems related to how many network connections it has,
maxconnections is tied to file descriptors, which seem to be related to number of processes that can be handled.
https://github.com/qubitcoin/QubitCoin/blob/1c616605f0f63e69983754a114d21eebddbb8710/src/init.cpp#L541

can you do anything?
maybe sending smaller amounts? this would reduce yr number of inputs.

could be painful though painstakingly repeat transactions,

a daemon is handy cos you can set up an auto transaction using crontab, and it would do it in the background ..
(actually you can apparently do that to a qt, but i'm not sure how. something I've always wanted to do so i'm currently syncing, but will look at it later)

..
how many addresses are the coins on, more than one?
do you have the privkeys?

if you have more than one address, you could import them one by one into a new wallet which would reduce # of tx.
if you do not have the privkeys there are tools to extract them from yr wallet.dat

or,
you could delete yr blockchain, so the wallet would have zero transactions when you run it, then you should be able to export yr privkeys easily enough.

to run client with different empty data directory,
from command line
open /location/Qubitcoin-Qt.app --args -datadir=/location/alternativedirectory

*(you can drag drop locations onto command line)*

I don't know what might be the culprit, i know it works on lot of Macs and El Capitan particularly. I'm no Mac user so i can't help more. Anyway, there's a webwallet, it's browser based.

Where did you get the download? I just want to be sure that it's not out of date, or no longer in use.
Did you get it from here? https://onlinegames.credit/downloads/paperwallet/
Hope I can help sort out the problem! Our webwallet is also available here: https://wallet.gamecredits.org/

El Capitan 10.11.5
How do I re-index?, I guess it's quicker than redownloading the blockchain

I tried sending on OSX 10.11 and it worked on my setup. Which version of OSX are you using? Does it always happen? Maybe try reindex or redownloading the blockchain.

Can somebody make pool for this?

Here's a Mac build I created from the 0.11.2.1 source. Give it a try:

https://github.com/willowrose/QubitCoin/releases/download/v0.11.2.1/q2c-0.11.2.1-osx.dmg

The different block chains is due to the new 0.11 clients starting to enforce the soft-forks from Bitcoin (BIP34, BIP65, etc).

These are enforced if a certain number of blocks are mined on the new wallet.

Since the majority seems to be on the new wallet, I suggest everyone upgrade to the new version to remain compatible.

To get the fork info on the new wallet you can type:

getblockchaininfo


{
"chain" : "main",
"blocks" : 2010486,
"headers" : 2010486,
"bestblockhash" : "00000006a0f46da556779ea27b0ae43054ab294500ea1bfbe5a97871a8c35eed",
"difficulty" : 0.13478134,
"verificationprogress" : 1.00000026,
"chainwork" : "000000000000000000000000000000000000000000000000001dc91cf4f3258c",
"pruned" : false,
"softforks" : [
{
"id" : "bip34",
"version" : 2,
"enforce" : {
"status" : true,
"found" : 8000,
"required" : 750,
"window" : 8000
},
"reject" : {
"status" : true,
"found" : 8000,
"required" : 950,
"window" : 8000
}
},
{
"id" : "bip66",
"version" : 3,
"enforce" : {
"status" : true,
"found" : 8000,
"required" : 750,
"window" : 8000
},
"reject" : {
"status" : true,
"found" : 8000,
"required" : 950,
"window" : 8000
}
},
{
"id" : "bip65",
"version" : 4,
"enforce" : {
"status" : true,
"found" : 8000,
"required" : 750,
"window" : 8000
},
"reject" : {
"status" : true,
"found" : 8000,
"required" : 950,
"window" : 8000
}
}
]
}