FastNoSQL.exe shuts down immediately

fastogt / fastonosql

FastoNoSQL is a crossplatform Redis, Memcached, SSDB, LevelDB, RocksDB, UnQLite, LMDB, ForestDB, Pika, Dynomite, KeyDB GUI management tool.

https://fastonosql.com

GNU General Public License v3.0

1.18k stars 97 forks source link

FastNoSQL.exe shuts down immediately #23

Closed Trolldemorted closed 7 years ago

Trolldemorted commented 7 years ago

fastonosql.exe is running for ~1s and silently shuts down on my W10 Pro N 64bit machine.

Happens with both the installed and the portable version.

Could not find any output or logs, unfortunately.

topilski commented 7 years ago

Hi @Trolldemorted , please check folder C:\Users\${NAME}\ , you can find fastonosql.log

Trolldemorted commented 7 years ago

nope, file does not exist

topilski commented 7 years ago

For which database you want to use FastoNoSql? if for redis you can try FastoRedis, may be FastoRedis will work.

Trolldemorted commented 7 years ago

a chrome app's leveldb, unfortunately i have not yet found a working editor on windows.

topilski commented 7 years ago

Yes, for leveldb worked only FastoNoSQL, i will try to reproduce and fix this issue, also you can login to fastonosql.com site and try to build own installer, please select only leveldb in options. Select Windows 10 and press build.

Trolldemorted commented 7 years ago

The fresh built installer "worked" as in the UI starts up now.

However, opening the db does not do much:

stuck

log says:

14:05:41.235 FastoNoSQL [ERROR] Fail connect to server: Invalid argument: idb_cmp1 does not match existing comparator : leveldb.BytewiseComparator!

I am new to leveldb, i should just open the folder with the *.ldb files, shouldn't i? Note that the db is rather big (~700 MB), can that cause issues?

topilski commented 7 years ago

Please select folder where placed leveldb files, i never worked with so big leveldb instances.

unforgettableid commented 7 years ago

@Trolldemorted: Thanks for your report!

FastoNoSQL is probably crashing silently. So you're probably experiencing two bugs.

It crashed silently when it should have shown you a Windows Error Reporting dialog box. This is bug #28.
It crashed, even though it shouldn't crash at all. This is the bug you reported.

Please do this:

Press Win+R to open the "Run" dialog.
Type: %LOCALAPPDATA%\CrashDumps
Click OK.

A) Are there still any FastoNoSQL crash dump files there, even though they were created so many weeks ago? If so, could you please visit https://github.com/fastogt/fastonosql/issues/23 and then drag and drop them into a comment?

B) If there are no FastoNoSQL crash dump files there, please check in the "View all problem reports" control panel and tell us whether or not there are any FastoNoSQL problem reports there.

unforgettableid commented 7 years ago

@Trolldemorted:

C) Please run msinfo32.exe. What processor (CPU) do you have?

unforgettableid commented 7 years ago

@Trolldemorted: If you have a Pentium or Celeron CPU, you might be experiencing bug #29, and if so, we don't need any crash dump files.

Trolldemorted commented 7 years ago

there is no CrashDumps folder in %LOCALAPPDATA% on my system.

The db in question does not exist any more, but the processor was a phenom II X4 940.

unforgettableid commented 7 years ago

The Phenom II X4 940 is a 64-bit CPU, but it doesn't have any AVX support. (Source.) If you were running the 64-bit version of FastoNoSQL, you probably experienced bug #29. The workaround is to use the 32-bit version instead.

It would be good if you could please do the following:

A) Open up the "View all problem reports" control panel and tell us whether or not there are any FastoNoSQL problem reports there. B) If there are, please right-click on a few of them, one at a time. C) For each one, choose "View technical details". Are an exception code and an exception offset shown? What are the code and the offset?

Trolldemorted commented 7 years ago

There are a lot, here is one:

Quelle
fastonosql

Zusammenfassung
Nicht mehr funktionsfähig

Datum
‎02.‎03.‎2017 11:50

Status
Der Bericht wurde gesendet.

Beschreibung
Pfad der fehlerhaften Anwendung:    C:\Program Files\FastoNoSQL\FastoNoSQL.exe

Problemsignatur
Problemereignisame: APPCRASH
Anwendungsname: FastoNoSQL.exe
Anwendungsversion:  1.5.0.0
Anwendungszeitstempel:  01410158
Fehlermodulname:    FastoNoSQL.exe
Fehlermodulversion: 1.5.0.0
Fehlermodulzeitstempel: 01410158
Ausnahmecode:   c000001d
Ausnahmeoffset: 0000000000a57bad
Betriebsystemversion:   10.0.14393.2.0.0.256.49
Gebietsschema-ID:   1031
Zusatzinformation 1:    d986
Zusatzinformation 2:    d98638711348b9469ee746f75705b0e9
Zusatzinformation 3:    52e2
Zusatzinformation 4:    52e23fa37fc61a0b55b905945af9d71e

Weitere Informationen über das Problem
Bucket-ID:  c5df9074b36e56cd12e30831bc15b7b7 (120695870482)

Unfortunately, no exception or stacktrace. I have indeed used the 64bit version, but unfortunately i cannot test the 32bit one because the database in question is gone.

unforgettableid commented 7 years ago

Thanks for all your replies!

I looked at the website of Error Toolkit, Inc.; they (correctly) report that exception code c000001d means STATUS_ILLEGAL_INSTRUCTION.

Offset 0000000000a57bad means FastoNoSQL!unqlite_util_random_num+5f8a4d.

So it's confirmed now:

Bug #29 caused FastoNoSQL to crash at startup for you.
But no crash dialog ever appeared on your screen, because of bug #28.

@topilski: I think we can close this issue now. :)