Author [EN] [ZH] [ES] [PT] [IT] [DE] [FR] [NL] [TR] [SR] [AR] [RU] [EN] [ZH] [ES] [PT] [IT] [DE] [FR] [NL] [TR] [SR] [AR] [RU] [EN] [ZH] [ES] [PT] [IT] [DE] [FR] [NL] [TR] [SR] [AR] [RU] Topic: Critical Error: An instance of Bitshares is already running! Wallet 4.27.1 Please Advise.  (Read 1005 times)

0 Members and 1 Guest are viewing this topic.

Offline Average Guy on Street

  • Jr. Member
  • **
  • Posts: 47
    • View Profile

Anyone get this critical error? And know how to fix it?

"Critical Error: An instance of Bitshares is already running"
I am running Wallet 4.27.1

Please advise.
Thanks


Sent from my iPad using Tapatalk

julian1

  • Guest
What platform? Try to check the process list, and see if there's another instance running.

Offline btswildpig

  • Hero Member
  • *****
  • Posts: 1423
    • View Profile
Anyone get this critical error? And know how to fix it?

"Critical Error: An instance of Bitshares is already running"
I am running Wallet 4.27.1

Please advise.
Thanks


Sent from my iPad using Tapatalk
backup the wallet ,  exit the wallet , go to the data file folder where the blockchains and wallet are stored , then delete everything except "wallet" folder , the restart the wallet and wait ... ...
这个是私人账号,表达的一切言论均不代表任何团队和任何人。This is my personal account , anything I said with this account will be my opinion alone and has nothing to do with any group.

Offline merlin0113

  • Sr. Member
  • ****
  • Posts: 286
    • View Profile
I came to this exact error today too. I think it's a bug.

Offline Average Guy on Street

  • Jr. Member
  • **
  • Posts: 47
    • View Profile
I'm running windows 7


Sent from my iPad using Tapatalk

Offline Riverhead

Look in the %AppData%/Bitshares tree for a file called, "LOCK" and delete it.

Sent from my Timex Sinclair


Offline fran2k

  • Full Member
  • ***
  • Posts: 126
    • View Profile
  • BTS: fran2k
Anyone get this critical error? And know how to fix it?

"Critical Error: An instance of Bitshares is already running"
I am running Wallet 4.27.1

Please advise.
Thanks


Sent from my iPad using Tapatalk
backup the wallet ,  exit the wallet , go to the data file folder where the blockchains and wallet are stored , then delete everything except "wallet" folder , the restart the wallet and wait ... ...

I'm having this same error after power loss in the computer while running the QT with 4.27.1 in Windows 7.
Witness: rmglab /// Buenos Aires BTS Meetup http://www.meetup.com/es-ES/BitSharesBA/ /// [old BTS 1.0 chain] Delegate bitshares-argentina (ex argentina-marketing-matt608) Thread https://bitsharestalk.org/index.php/topic,15781.0.html

Offline vikram

We're not sure why this is happening to some people. Another thread: https://bitsharestalk.org/index.php?topic=10727.msg170452#msg170452


Offline mint chocolate chip

Right click and close the Bitshares icon that is in the running programs box in the bottom right corner of your desktop. X-ing out of the client does not stop it from running on your computer.

Offline Riverhead

I got the error on a fresh boot into Windows. No BitShares process is running. I'll see if I can resolve. Could be a lock file somewhere.

It may be related to multithreading the indexing on 32bit Windows (that's what I'm running on this MacBook Pro). It starts the indexing and then closes with that error.
« Last Edit: January 09, 2015, 01:49:35 AM by Riverhead »


Offline vikram

Nathan's comment here: https://github.com/BitShares/qt_wallet/issues/82#issuecomment-68959403 made me realize that this is a misleading error message that our team has put there.

The message does not necessarily mean that another instance is running, rather it will show up when one of the LevelDB databases fails to open for some reason.

I've seen the underlying database error occur when the OS isn't happy about our process opening so many file handles. There are likely multiple other reasons this could happen as well, as we've been seeing reports of database opening failures for a long time.

Is everyone that has this problem running Windows? 64-bit or 32-bit?

Offline testz

Is everyone that has this problem running Windows? 64-bit or 32-bit?

Never seen this problem (Windows 64-bit).


 

Google+