You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
db browser for sqlite.exe has stopped working #774
@elyorm Thanks for reporting it, we will need more info though so we can investigate. 😄
As well as what @revolter mentions (it's important), info about when/where it crashed would help. For example, did it crash as soon as you opened it, or did it crash in the middle of doing something, (or something else)?
Are you ok to help us out with that info, so we can try figuring it out? 😄
Works fine for me. I can only assume (as is usual) Windows will try and open the last used location. If this is on media that no longer exists, DB4S might be getting confused? Is there a registry entry telling DB4S where to open, or does it just rely on Windows?
I assume double clicking a .db file opens the file correctly in DB4S. If you close DB4S, re-open it and then click 'Open Database', does that work? (ie, it has stored its last used location...)
I've set it to weird paths, wrong paths and even 'cannot access' paths. It'll default to the program directory if it can't. A 'cannot access' path correctly comes up with a warning.
I can't reproduce this, so this may not be the cause. 😢
Even deleted the whole registry leg for DB4S and it just recreated what it needed.
I'm currently logged on as an administrative user (so not Administrator, but I have admin privileges). so not sure if a 'normal' user would have a different experience. Will check.
Deleting the DB4S registry leg could also be an option. I can knock up a VB program to do that, as I was just creating a program to reset the file associations.
We might want to add some debugging info / error handling to the "Open Database" method, even in just a once-off temporary build, to try and understand why it's crashing.
I tried it a few days ago with a somewhat recent nightly (not exactly sure
of the date) and that failed the same way however the laptop is in the
field and I don't have current access to that.
John
My first guess is there's some kind of dll conflict. There are some tools around to show which dlls are being used by a program, so we should be able to compare what your system is using with a "known good" one.
But yeah, it'll need you to have the laptop in hand. Ping us when you're ok on your end and we can take a look at this. 😄
Can confirm this happens only in the Win64 version, I was having this frequently, reading this thread I installed the 32bit version, and it seems not to crash.
It just crashes ~3 seconds after the open file dialog opens.
@RangelReale Thanks, that's useful info. It does sound like there's some kind of conflict or mis-loading of 32 bit dll's for the Win64 version then. It'd be useful to know what's causing it, as although it seems pretty rare that doesn't exactly help the people it happens to.
Not really sure how to diagnose this further though. 😖
I hope someone must have found a solution by now.
It crashes every time I click "New Database" or "Open Database".
when I click either, the window to choose a location pops-up, and 2 seconds later, the software stops working
First I tried the portable version. This happened.
Then the x64 .exe file. Again it crashed.
Then I tried the same file for a previous version (3.9.0). Still it happens.
I was installing it in E drive, so for a change I tried to let it install in the default location given in the prompt (C:/ProgramFile/......). But the issue remains.
@drescherjm thanks a lot. by all the gods, the old and the new, Bless You.
it works.
I spent the last hour finding alternative software, and 2 seemed like they could work, but not good enough.
Thank you
Sorry to hear the 64bitty version is causing problems for you. Glad the 32bitty version is working.
Are you feeling adventurous? Want to try and crack WHY the 64bitty version is dying? You could have your name in lights! (or at least black text)
If you could help us out, it would be appreciated.
Closing this as it doesn't really seem like something we can do anything about. It looks very much like there's some kind of .dll problem on the systems it does happen on.
We'd need someone this is happening for, to take the time and effort to investigate the problem using WinDBG as mentioned by @chrisjlocke above.
If someone's feeling up for doing so however, they're 100% welcome to reopen this issue and get into figuring out how to fix this. It would be very welcome. 😄
Activity
revolter commentedon Sep 13, 2016
It would have helped if you completed the issue template and not remove it. So, what version? What operating system?
justinclift commentedon Sep 13, 2016
@elyorm Thanks for reporting it, we will need more info though so we can investigate. 😄
As well as what @revolter mentions (it's important), info about when/where it crashed would help. For example, did it crash as soon as you opened it, or did it crash in the middle of doing something, (or something else)?
Are you ok to help us out with that info, so we can try figuring it out? 😄
justinclift commentedon Sep 14, 2016
@elyorm ping?
elyorbegmurod commentedon Sep 15, 2016
Version 3.9.0, Qt Version 5.7.0, SQLCipher Version 3.11.0
windows 10
when I click "Open Database"
revolter commentedon Sep 15, 2016
@elyorm Is it happening every time you click
Open Database?@justinclift Do you have time to test this on your VM?
chrisjlocke commentedon Sep 15, 2016
64bit?
Works fine for me. I can only assume (as is usual) Windows will try and open the last used location. If this is on media that no longer exists, DB4S might be getting confused? Is there a registry entry telling DB4S where to open, or does it just rely on Windows?
I assume double clicking a .db file opens the file correctly in DB4S. If you close DB4S, re-open it and then click 'Open Database', does that work? (ie, it has stored its last used location...)
revolter commentedon Sep 15, 2016
Nonetheless, it should not crash. Are you able to force the last path to a non-existing path and reproduce this?
chrisjlocke commentedon Sep 15, 2016
I've set it to weird paths, wrong paths and even 'cannot access' paths. It'll default to the program directory if it can't. A 'cannot access' path correctly comes up with a warning.
I can't reproduce this, so this may not be the cause. 😢
Even deleted the whole registry leg for DB4S and it just recreated what it needed.
I'm currently logged on as an administrative user (so not Administrator, but I have admin privileges). so not sure if a 'normal' user would have a different experience. Will check.
revolter commentedon Sep 15, 2016
Great job! Shame that the news is bad :(
@elyorm We need more info in order to reproduce this.
chrisjlocke commentedon Sep 15, 2016
Deleting the DB4S registry leg could also be an option. I can knock up a VB program to do that, as I was just creating a program to reset the file associations.
justinclift commentedon Sep 15, 2016
We might want to add some debugging info / error handling to the "Open Database" method, even in just a once-off temporary build, to try and understand why it's crashing.
6 remaining items
justinclift commentedon May 17, 2017
@elyorm @drescherjm Would you have time to try our latest nightly 32 + 64 bit builds, and let us know if they still have this crash problem?
https://nightlies.sqlitebrowser.org/latest/
drescherjm commentedon May 17, 2017
justinclift commentedon May 17, 2017
Thanks @drescherjm, that's interesting.
My first guess is there's some kind of dll conflict. There are some tools around to show which dlls are being used by a program, so we should be able to compare what your system is using with a "known good" one.
But yeah, it'll need you to have the laptop in hand. Ping us when you're ok on your end and we can take a look at this. 😄
RangelReale commentedon Jul 5, 2017
Can confirm this happens only in the Win64 version, I was having this frequently, reading this thread I installed the 32bit version, and it seems not to crash.
It just crashes ~3 seconds after the open file dialog opens.
justinclift commentedon Jul 18, 2017
@RangelReale Thanks, that's useful info. It does sound like there's some kind of conflict or mis-loading of 32 bit dll's for the Win64 version then. It'd be useful to know what's causing it, as although it seems pretty rare that doesn't exactly help the people it happens to.
Not really sure how to diagnose this further though. 😖
grifter-yo commentedon Oct 25, 2017
Hello
I hope someone must have found a solution by now.
It crashes every time I click "New Database" or "Open Database".
when I click either, the window to choose a location pops-up, and 2 seconds later, the software stops working
First I tried the portable version. This happened.
Then the x64 .exe file. Again it crashed.
Then I tried the same file for a previous version (3.9.0). Still it happens.
I was installing it in E drive, so for a change I tried to let it install in the default location given in the prompt (C:/ProgramFile/......). But the issue remains.
Can anyone suggest a solution?
Or an alternative?
Thank You
drescherjm commentedon Oct 25, 2017
For me the 32 bit version did not have the crash on the systems that the 64 bit version crashed.
grifter-yo commentedon Oct 25, 2017
@drescherjm thanks a lot. by all the gods, the old and the new, Bless You.
it works.
I spent the last hour finding alternative software, and 2 seemed like they could work, but not good enough.
Thank you
chrisjlocke commentedon Oct 31, 2017
Hi @grifter-yo
Sorry to hear the 64bitty version is causing problems for you. Glad the 32bitty version is working.
Are you feeling adventurous? Want to try and crack WHY the 64bitty version is dying? You could have your name in lights! (or at least black text)
If you could help us out, it would be appreciated.
You can run windbg to identify the call stack at the point of the wibble, which can help identify where it wibbled.
More information here: https://github.com/sqlitebrowser/sqlitebrowser/wiki/Debugging-a-crash-on-Windows
Thanks! Thumbs up, a big head nod and a big cheesy grin could be winging your way.
justinclift commentedon Nov 9, 2017
Closing this as it doesn't really seem like something we can do anything about. It looks very much like there's some kind of .dll problem on the systems it does happen on.
We'd need someone this is happening for, to take the time and effort to investigate the problem using WinDBG as mentioned by @chrisjlocke above.
If someone's feeling up for doing so however, they're 100% welcome to reopen this issue and get into figuring out how to fix this. It would be very welcome. 😄