V0.10.2.1-abe client crashes on Win7 x64

[mfread]

I've downloaded all 3 current qt clients from Google Drive and they (piggybank.exe) all produce an "APPCRASH" report.

• V0.10.1.0-tempfix.zip
• V0.10.2.0-abe.zip
• V0.10.2.1-abe.zip

Am I doing something wrong? Are there any further releases? I have CENT with cryptsy.com, which by all accounts has shut down the CENT wallet, and so I want to move my CENT coins out to a local wallet.

[CatmanIX]

Can't really help unless you post at least the last fifty lines from your debug log, but likeliness is that your old chain is corrupt and you need to wipe it before launching a new wallet.

Just delete everything in %appdata%\pennies except for wallet.dat (that's where your pennies are).

Also, fair warning, as far as i know Cryptsy's still on an old wallet with a broken chain, so you likely won't receive anything you send from them. (I think that's why they're shutting down the market, 'cause their wallets all fucked up, but they haven't responded to any of my inquiries so i honestly know fuck all.)

[mfread]

Thanks CatmanIX.

This was a brand new install - I have never had any of these wallets on my PC before.

The first one I downloaded was 10.2.1-abe.zip as it was the most recent release. When unzipped and the piggybank.exe was executed

, it created the following appdata roaming folder (see screenshot), and produced the following crash report (see screen shot).

[CatmanIX]

hmm. did you try to interact with the program in any way while it was trying to start loading the blockchain? That can cause the wallet to crash (though i've only ever seen it happen after it's already got a blockchain from a previous session).

Also, what are the contents of db.log?

[mfread]

No, I didn't interact with the app (as there is no time/opportunity to do
so). From Windows Explorer I double-clicked on the piggybank.exe file, it
opens with the splash screen/logo of a pig, then within 2 seconds it
displays the "piggybank.exe has stopped working" dialog (with the crash
report).

As you can see from one of the 3 screenshots I provided you with, db.log is
0 bytes in size.

On Sun, Mar 2, 2014 at 9:37 AM, Jack Fenderson notifications@github.comwrote:

hmm. did you try to interact with the program in any way while it was
trying to start loading the blockchain? That can cause the wallet to crash
(though i've only ever seen it happen after it's already got a blockchain
from a previous session).

Also, what are the contents of db.log?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/7#issuecomment-36439121
.

[mfread]

I also copied the entire app from F:\Crypto-Coins\Coins\Scrypt\Pennies
(CENT)\wallets\Pennies-v0.10.2.1-abe to F:\Pennies (just in case the app
doesn't like long pathnames etc). Before launching piggybank.exe I deleted the entire appdata/roaming/pennies folder to be sure.

After running piggybank.exe I still get the same result (crash dialog window).

On Sun, Mar 2, 2014 at 9:45 AM, Mark Read mfread@gmail.com wrote:

No, I didn't interact with the app (as there is no time/opportunity to do
so). From Windows Explorer I double-clicked on the piggybank.exe file, it
opens with the splash screen/logo of a pig, then within 2 seconds it
displays the "piggybank.exe has stopped working" dialog (with the crash
report).

As you can see from one of the 3 screenshots I provided you with, db.log
is 0 bytes in size.

On Sun, Mar 2, 2014 at 9:37 AM, Jack Fenderson notifications@github.comwrote:

hmm. did you try to interact with the program in any way while it was
trying to start loading the blockchain? That can cause the wallet to crash
(though i've only ever seen it happen after it's already got a blockchain
from a previous session).

Also, what are the contents of db.log?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/7#issuecomment-36439121
.

[mfread]

here's another screenshot ...

On Sun, Mar 2, 2014 at 9:48 AM, Mark Read mfread@gmail.com wrote:

I also copied the entire app from F:\Crypto-Coins\Coins\Scrypt\Pennies
(CENT)\wallets\Pennies-v0.10.2.1-abe to F:\Pennies (just in case the app
doesn't like long pathnames etc).

I still get the same result (crash dialog window).

On Sun, Mar 2, 2014 at 9:45 AM, Mark Read mfread@gmail.com wrote:

No, I didn't interact with the app (as there is no time/opportunity to do
so). From Windows Explorer I double-clicked on the piggybank.exe file, it
opens with the splash screen/logo of a pig, then within 2 seconds it
displays the "piggybank.exe has stopped working" dialog (with the crash
report).

As you can see from one of the 3 screenshots I provided you with, db.log
is 0 bytes in size.

On Sun, Mar 2, 2014 at 9:37 AM, Jack Fenderson notifications@github.comwrote:

hmm. did you try to interact with the program in any way while it was
trying to start loading the blockchain? That can cause the wallet to crash
(though i've only ever seen it happen after it's already got a blockchain
from a previous session).

Also, what are the contents of db.log?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/7#issuecomment-36439121
.

[mfread]

Did you mention that Cryptsy have the old (corrupted) blockchain and
therefore any coins I have in it are probably lost? A friend transfered his
CENT coins out of Cryptsy and into swisscex - does swisscex therefore have
the old (corrupted) blockchain too?

Will Cryptsy (and others) ever be able to repair their blockchain (or move
coins out of it and into the 'new' block chain)?

I do not understand the process sorry. How do block chains become corrupt?
I thought it was impossible. It has never happened to BTC, LTC etc (as far
as I know - it would of been all over the press if it did).

So how did the Pennies blockchain become corrupt? And once corrupted, does
everyone loose their Pennies and have to start mining afresh (using a new
wallet the the new blockchain)?

Thanks Jack.

On Sun, Mar 2, 2014 at 9:56 AM, Mark Read mfread@gmail.com wrote:

here's another screenshot ...
[image: Inline image 1]

On Sun, Mar 2, 2014 at 9:48 AM, Mark Read mfread@gmail.com wrote:

I also copied the entire app from F:\Crypto-Coins\Coins\Scrypt\Pennies
(CENT)\wallets\Pennies-v0.10.2.1-abe to F:\Pennies (just in case the app
doesn't like long pathnames etc).

I still get the same result (crash dialog window).

On Sun, Mar 2, 2014 at 9:45 AM, Mark Read mfread@gmail.com wrote:

No, I didn't interact with the app (as there is no time/opportunity to
do so). From Windows Explorer I double-clicked on the piggybank.exe file,
it opens with the splash screen/logo of a pig, then within 2 seconds it
displays the "piggybank.exe has stopped working" dialog (with the crash
report).

As you can see from one of the 3 screenshots I provided you with, db.log
is 0 bytes in size.

On Sun, Mar 2, 2014 at 9:37 AM, Jack Fenderson <notifications@github.com

wrote:

hmm. did you try to interact with the program in any way while it was
trying to start loading the blockchain? That can cause the wallet to crash
(though i've only ever seen it happen after it's already got a blockchain
from a previous session).

Also, what are the contents of db.log?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/7#issuecomment-36439121
.

[CatmanIX]

like i said, i have no idea what's going on with cryptsy, they won't respond to any of my inquiries. The last thing i heard (through unofficial channels) was that they were still running the 10.0.0 version of the wallet, which didn't have proper checks in place to ensure the validity of old blocks so the whole chain got forked to hell. As a result, some old coins were still able to be transferred in and out, but anything generated since the stake fix weren't recognized on cryptsy's side. whether or not they ever actually got their wallet up to date i have no idea, they aren't telling me anything. It shouldn't have been a major issue for them.

The main chain is perfectly healthy as far as I know, it's just that the 10.0.0 version of the wallet can't validate it. same thing would happen if you were running Bitcoin v1, chain parameters have been changed and old clients don't know what to do with it.

Anyway, as for your wallet, i have no idea why it crashes every time you launch it. unfortunately, i don't have my workstation functional at the moment so i can't do any significant testing to work on it. Only other thing i can think of is to delete all your files, redownload 10.2.1-abe (don't even bother with the older versions, i should probably just remove those), extract and try again. It could be as simple as your original download being corrupt. Also try running from C:\Pennies and seeing if that makes a difference (maybe somethings funky with F:?).

[mfread]

Thanks Jack.

Still no-go.

Downloaded 10.2.1-abe. Extracted into C:\pennies. Deleted
appdata\roaming\pennies. Executed piggybank.exe - exact same problem
occured. No db.log.

I think I have Win7 32bit somewhere in a virtual machine - I'll try 10.2.1
there (perhaps it's Win7 64bit that is the issue).

=Mark

On Sun, Mar 2, 2014 at 11:28 AM, Jack Fenderson notifications@github.comwrote:

like i said, i have no idea what's going on with cryptsy, they won't
respond to any of my inquiries. The last thing i heard (through
unofficial channels) was that they were still running the 10.0.0 version of
the wallet, which didn't have proper checks in place to ensure the validity
of old blocks so the whole chain got forked to hell. As a result, some old
coins were still able to be transferred in and out, but anything generated
since the stake fix weren't recognized on cryptsy's side. whether or not
they ever actually got their wallet up to date i have no idea, they
aren't telling me anything. It shouldn't have been a major issue for them.

The main chain is perfectly healthy as far as I know, it's just that the
10.0.0 version of the wallet can't validate it. same thing would happen if
you were running Bitcoin v1, chain parameters have been changed and old
clients don't know what to do with it.

Anyway, as for your wallet, i have no idea why it crashes every time you
launch it. unfortunately, i don't have my workstation functional at the
moment so i can't do any significant testing to work on it. Only other
thing i can think of is to delete all your files, redownload 10.2.1-abe
(don't even bother with the older versions, i should probably just remove
those), extract and try again. It could be as simple as your original
download being corrupt. Also try running from C:\Pennies and seeing if that
makes a difference (maybe somethings funky with F:?).

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/7#issuecomment-36441714
.

[CatmanIX]

It shouldn't be win7x64, that's my build OS and it launched fine in that. Try setting up a new win7x64 VM and see how it runs in that, there must be something on your system interfering with the wallet for some reason.

Actually, what do you have for antivirus? Some of them pick up the built-in miner as malware and can interfere with it without telling you.

[mfread]

This is a new Win7 x64 install (just 1 wk old). The only anti virus/malware
installed is the default Windows Defender. I have disabled it (and the
Windows Firewall) to ensure this wasn't the cause.

As mentioned prior, I have several other Windows qt wallets installed that
run just fine.

How do I tell piggybank.exe to use a local folder instead of
.../appdata/roaming/pennies? I want to eliminate this aspect for the
equation.

On Sun, Mar 2, 2014 at 2:53 PM, Jack Fenderson notifications@github.comwrote:

It shouldn't be win7x64, that's my build OS and it launched fine in that.
Try setting up a new win7x64 VM and see how it runs in that, there must be
something on your system interfering with the wallet for some reason.

Actually, what do you have for antivirus? Some of them pick up the
built-in miner as malware and can interfere with it without telling you.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/7#issuecomment-36445303
.

[CatmanIX]

I'm not sure if that's even an option, but if it's actually creating files there in the first place it shouldn't be the issue...

Have you tried finding someone who can send you a copy of their blockchain and try to launch with that? I'd send you mine but I won't have access to it for another week or so.

[mfread]

Thanks Jack. Good idea. I can wait a week :)

On Mon, Mar 3, 2014 at 6:54 AM, Jack Fenderson notifications@github.comwrote:

I'm not sure if that's even an option, but if it's actually creating files
there in the first place it shouldn't be the issue...

Have you tried finding someone who can send you a copy of their blockchain
and try to launch with that? I'd send you mine but I won't have access to
it for another week or so.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/7#issuecomment-36464462
.

[mfread]

Hi Jack. Any update on the zip file?

Also, is the src in this repo the 10.2.1 version? If yes, do you know where I can find instructions to compile it under Win7? If I can get that far then perhaps I might be able to debug why it is crashing.

Cheers,
Mark

[CatmanIX]

Still waiting on a cooler from the BTCStore to get my workstation back up so i can access my files, sorry.

There's some basic build instructions in doc/build-msw.txt, that should give you a start. The repo is up to date.