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 on unsaved new database, all logins gone !! #105

Open
mxdmxd opened this issue Feb 13, 2013 · 3 comments
Open

Crash on unsaved new database, all logins gone !! #105

mxdmxd opened this issue Feb 13, 2013 · 3 comments

Comments

@mxdmxd
Copy link

mxdmxd commented Feb 13, 2013

  1. Executable Starkits for Windows 32bit, used on Windows 7 64bit machine.
    https://github.com/downloads/zdia/gorilla/gorilla15363.exe
  2. Open first time
  3. New database
  4. Put in dozens of logins in one subgroup
  5. Did not explicitly click "save as"
  6. Attempt to close the app window
  7. crash when closing, and all the logins are gone!!!

Maybe something wrong with saving the new database for the first time?
If I did "save as" some file in step 4, it does not crash.

In general, how reliable the Executable Starkits of Password Gorrila is? This is scary..

The error log reads:

can't read "::gorilla::fileName": no such variable
can't read "::gorilla::fileName": no such variable
while executing
"gorilla::SaveBackup $::gorilla::fileName "
(procedure "LockDatabase" line 41)
invoked from within
"LockDatabase"
(procedure "::gorilla::IdleTimeout" line 2)
invoked from within
"::gorilla::IdleTimeout"
("after" script)

@zdia
Copy link
Owner

zdia commented Feb 13, 2013

I did follow your steps:

  1. Open first time
  2. New database
  3. Put in dozens of logins in one subgroup
  4. Did not explicitly click "save as"
  5. Attempt to close the app window
  6. crash when closing, and all the logins are gone!!!

But it did not crash. A warning dialog appeared to remind the user that there are unsaved changes.

Your error message indicates rather that the "LockDatabase" procedure is causing the issue and indeed I can confirm the bug which caused your data loss.

If the keep-backup-file flag is set in the preferences and if the database is locked then this error will be produced because in this early stage there is no filename for the database but only a copy in the memory.

I am sorry for this bug but a patch will immediately close this early stage hole. The next version 1.5.3.7 will have fixed this bug.

@mxdmxd
Copy link
Author

mxdmxd commented Feb 13, 2013

Makes sense! I did have backup enabled. I suppose the bug fix will prompt for a filename when the backup happens and no filename is yet available. Thanks for the timely response. I'm all in as user of Gorilla!

@zdia
Copy link
Owner

zdia commented Feb 13, 2013

"I suppose the bug fix will prompt for a filename when the backup happens and no filename is yet available."

Yes, it does so. Commit 203b4a3 will show you details.

" I'm all in as user of Gorilla!"

You are welcome :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants