Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Crash with MacOs Mojave #994

Closed
Promethee83 opened this issue Sep 5, 2019 · 9 comments

Comments

@Promethee83
Copy link

commented Sep 5, 2019

Describe the issue

Crash when I open the app after few seconds

Can you reliably reproduce the issue?

Always

If so, please list the steps to reproduce below:

  1. Open app
  2. Wait
  3. Crash

Expected behavior

The 3.3.0 version is fully operational

Actual behavior

The app crashed

Screenshots.

Process: PIVX-Qt [72825]
Path: /Applications/PIVX-Qt.app/Contents/MacOS/PIVX-Qt
Identifier: PIVX-Qt
Version: 3.4.0 (3.4.0)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: PIVX-Qt [72825]
User ID: 501

Date/Time: 2019-09-05 14:04:48.386 +0200
OS Version: Mac OS X 10.15 (19A546d)
Report Version: 12
Bridge OS Version: 3.0 (14Y905)
Anonymous UUID: 978ADC1C-29AC-12E9-81DF-D05594649B5C

Time Awake Since Boot: 240000 seconds

System Integrity Protection: enabled

Crashed Thread: 4 QThread

Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY

Application Specific Information:
Assertion failed: (hashPrevBlock == view.GetBestBlock()), function ConnectBlock, file main.cpp, line 3168.

What version of PIVX Core are you using?

3.4.0

Machine specs:

  • OS: MacOs Mojave
  • CPU:
  • RAM:
  • Disk size:
  • Disk Type (HD/SDD):

Any extra information that might be useful in the debugging process.

@fdknunes

This comment has been minimized.

Copy link

commented Sep 18, 2019

Hi ANy updates on This?Were you able to find a workaround?
I 'M HAVING THE EXACT SAME PROBLEM

@akshaynexus

This comment has been minimized.

Copy link

commented Sep 18, 2019

Try starting it with -reindex.that should solve the issue

@Warrows

This comment has been minimized.

Copy link
Collaborator

commented Sep 29, 2019

Did you try the above suggested solution? Is it any better?

@Promethee83

This comment has been minimized.

Copy link
Author

commented Sep 30, 2019

@Fuzzbawls

This comment has been minimized.

Copy link
Collaborator

commented Sep 30, 2019

3.3.0 isn't a valid version anymore. The error indicates blockchain data corruption. you can follow the steps on https://snapshots.pivx.org to get 3.4.0 up and running again.

@Promethee83

This comment has been minimized.

Copy link
Author

commented Oct 1, 2019

@random-zebra

This comment has been minimized.

Copy link
Collaborator

commented Oct 1, 2019

That's because, not upgrading in time, you ended up on a forked chain. Those coins are not "lost".
They are simply part of a chain that the rest of the network considers invalid.

@fdknunes

This comment has been minimized.

Copy link

commented Oct 2, 2019

@fdknunes

This comment has been minimized.

Copy link

commented Oct 2, 2019

@Warrows Warrows closed this Oct 2, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
6 participants
You can’t perform that action at this time.