lol VB6. It's called Qt and it's from Nokia: http://qt.nokia.com/
And that's why it sucks
Topic: Version 0.6.2 available - page 2. (Read 8331 times)
lol VB6. It's called Qt and it's from Nokia: http://qt.nokia.com/
If you really have 11,000 transactions, why are you even using the GUI?
And if you know how to program in wx, you are welcome to maintain the old version. Luke-Jr will even help you set it up.
If you really have 11,000 transactions, why are you even using the GUI?
And if you know how to program in wx, you are welcome to maintain the old version. Luke-Jr will even help you set it up.
bitcoin-qt has a flaw when you have thousands of transactions It starts to be a CPU and memory hog. Plus it looks like it was done in VB6. The GUI is crap, please go back to one of the beta designs as it was far superior.
I'm running this on windows, setting the priory to low, and setting the affinity to only using 2 CPU's on bitcoin-qt.exe. No real change, still a hog.
The client started to become a more of a resource whore around the ~1000 transactions mark... not sure 100% tho. I'm a little over 11k transactions.. and doing more and more everyday.
I've tried multibit, and Electrum.. both sux imho... May give multibit another try, but hate running java.. *sigh*
I know of a few other users with the same issue... From my conclusion it seems that the bitcoin client does not like to have thousands and thousands of transactions
Any suggestions?
I'm running this on windows, setting the priory to low, and setting the affinity to only using 2 CPU's on bitcoin-qt.exe. No real change, still a hog.
The client started to become a more of a resource whore around the ~1000 transactions mark... not sure 100% tho. I'm a little over 11k transactions.. and doing more and more everyday.
I've tried multibit, and Electrum.. both sux imho... May give multibit another try, but hate running java.. *sigh*
I know of a few other users with the same issue... From my conclusion it seems that the bitcoin client does not like to have thousands and thousands of transactions
Any suggestions?
When sending coins from one of your addresses to another one of your addresses, the client only displays an entry saying "transaction to yourself" without listing the amount or the from/to address.
While this isn't a bug, it makes keeping track of your coins difficult. Blockchain.info for example lists the transaction just like every other one; I suggest that the client should do the same.
While this isn't a bug, it makes keeping track of your coins difficult. Blockchain.info for example lists the transaction just like every other one; I suggest that the client should do the same.
Hey, I didn't have time to check the thread if this already has been reported, but after installing, running it for the first time I get a "Runaway exception" error. It says "EXCEPTION: NSt8ios_base7failurE" and "CDataStream:
)read : end of data" on the last line it says "C:\Program Files\Bitcoin\Bitcoin-qt.exe in runaway exception"
I'm running windows 7 and 0.6 worked fine. I already uninstalled 0.6 before installing 0.6.2 but still the same error.
)read : end of data" on the last line it says "C:\Program Files\Bitcoin\Bitcoin-qt.exe in runaway exception"I'm running windows 7 and 0.6 worked fine. I already uninstalled 0.6 before installing 0.6.2 but still the same error.
I see that too on W7 x64, and additionally another display anomaly: Clicking the icon once pops the window into the foreground, and clicking again puts it back down in the tray. This isn't a bad thing, but it is different from how it used to work. It used to require a double click to open, and X it out to minimize to tray.
I see it on my Win 7 x64 machine. Wasn't like that on version 0.6.1.
I was wrong. Tried version 0.6.0, 0.6.1 and 0.6.2 now.0.6.0 = OK
0.6.1 = icon remains in system tray
0.6.2 = icon remains in system tray
Anyone else seeing the same behavior?
I see it on my Win 7 x64 machine. Wasn't like that on version 0.6.1.Yup. I think I see it on my XP laptop as well.
Anyone else seeing the same behavior?
I see it on my Win 7 x64 machine. Wasn't like that on version 0.6.1. 
I'm running into a minor annoyance that is happening on two separate Windows 7 x64 machines. After exiting bitcoin-qt, the icon remains in the system tray until you move the mouse over it. I'm not sure if it is a Windows issue or something specific to my display settings, but I don't recall it happening with earlier versions. Anyone else seeing the same behavior?
We ♥ Gavin.
Needs to be mate into a t-shirt..and sold for Bitcoin.
@Toffoo - Yes seeing some inappropriate switching to foreground behavior too. Running 3 different Windows 0.6.xx versions here, no change in that which I've noticed. Was trying to figure out how to document that just yesterday, somewhat hard to describe.
Just wanted to add...
Gavin's recommended upgrade path went smoothly, no problems to report there, although while reviewing which files had changed, was surprised to find that in windows explorer, under the Program Files/bitcoin subdirectory as well as the bitcoin/src (plus subs) & bitcoin/daemon folders, all the files date/time stamps remain the same, stuck on 1/29/2011. Both the date modified and the date created fields, odd that I can't look at those quickly and be able to tell which files have been modified recently. Mostly it would be nice to at least see the bitcoin-qt.exe file has a newer time stamp on it, before running....
My initial install was back one April 2nd 2012, can clearly see that as the folders dates modified & created are working fine, it's just the files themselves which aren't changing....
GR
Just wanted to add...
Gavin's recommended upgrade path went smoothly, no problems to report there, although while reviewing which files had changed, was surprised to find that in windows explorer, under the Program Files/bitcoin subdirectory as well as the bitcoin/src (plus subs) & bitcoin/daemon folders, all the files date/time stamps remain the same, stuck on 1/29/2011. Both the date modified and the date created fields, odd that I can't look at those quickly and be able to tell which files have been modified recently. Mostly it would be nice to at least see the bitcoin-qt.exe file has a newer time stamp on it, before running....
My initial install was back one April 2nd 2012, can clearly see that as the folders dates modified & created are working fine, it's just the files themselves which aren't changing....
GR
Pieter fixed the "100% usage on OSX bug" and I created and uploaded a fixed version 0.6.2.2 especially for the Mac.
Thanks guys, I can confirm the v0.6.2.2 Mac version fixed the CPU bug. However, the "switch to foreground" issue I mentioned looks like it's still there for the next version to fix.
Could someone explain the differences with a portable and non-portable blkindex.dat?
Portable means you can move/copy it to another data directory.
If changes have been made to a .dat file (except blk0001.dat, which isn't really a database), an "lsn_reset pass" is necessary before the file can be used in another data directory (or the same, if its logfiles are deleted). Versions prior to 0.6.1 would always perform this pass at shutdown - which could take up to a minute on some systems. Since 0.6.1, this process is made optional for addr.dat and blkindex.dat. Wallets are always made portable at shutdown.
Could someone explain the differences with a portable and non-portable blkindex.dat?
I know the new version is "faster" to shut down, but how much faster should I expect it to be? I haven't really timed it, but the old version seemed to take between 30 sec and 1 min to shut down completely.
It depends on what caused the slowdown. While not syncing the chain, with no caches to write at shutdown, I often get shutdowns close to a second or less now. During chain download, it can be significantly more.
I know the new version is "faster" to shut down, but how much faster should I expect it to be? I haven't really timed it, but the old version seemed to take between 30 sec and 1 min to shut down completely.
It depends on what caused the slowdown. While not syncing the chain, with no caches to write at shutdown, I often get shutdowns close to a second or less now. During chain download, it can be significantly more.
Pieter fixed the "100% usage on OSX bug" and I created and uploaded a fixed version 0.6.2.2 especially for the Mac.
RE: upgrading: the best upgrade practice is to:
1) Backup your wallet someplace safe (if you're running an 0.6 release then use the Backup Wallet menu item).
2) Shutdown. Make sure Bitcoin isn't still in your system tray-- don't just close the window, shut it down.
3) Wait a minute or two (it can take older versions a minute or two to completely shut down)
4) Install and run the new version.
I know the new version is "faster" to shut down, but how much faster should I expect it to be? I haven't really timed it, but the old version seemed to take between 30 sec and 1 min to shut down completely. RE: upgrading: the best upgrade practice is to:
1) Backup your wallet someplace safe (if you're running an 0.6 release then use the Backup Wallet menu item).
2) Shutdown. Make sure Bitcoin isn't still in your system tray-- don't just close the window, shut it down.
3) Wait a minute or two (it can take older versions a minute or two to completely shut down)
4) Install and run the new version.
Pieter fixed the "100% usage on OSX bug" and I created and uploaded a fixed version 0.6.2.2 especially for the Mac.
RE: upgrading: the best upgrade practice is to:
1) Backup your wallet someplace safe (if you're running an 0.6 release then use the Backup Wallet menu item).
2) Shutdown. Make sure Bitcoin isn't still in your system tray-- don't just close the window, shut it down.
3) Wait a minute or two (it can take older versions a minute or two to completely shut down)
4) Install and run the new version.
RE: upgrading: the best upgrade practice is to:
1) Backup your wallet someplace safe (if you're running an 0.6 release then use the Backup Wallet menu item).
2) Shutdown. Make sure Bitcoin isn't still in your system tray-- don't just close the window, shut it down.
3) Wait a minute or two (it can take older versions a minute or two to completely shut down)
4) Install and run the new version.
Working fine here.
Jump to: