|
Nezic Apprentice
Joined: 10 Oct 2000 Posts: 119 Location: Colorado
|
Posted: Sun Feb 07, 2010 11:27 pm
[3.14] Strangness when closing one out of several instances of same session |
This might have been the same in 3.13, but I'm not sure. It is probably also related to my post about using 'Hide': http://forums.zuggsoft.com/forums/viewtopic.php?t=34658
If you open two instances of the same session and then close the first one (right-click on tab, then 'Close'), the settings end up being very strange in the Package Editor. After repeating this test several times, I also saw TeSSH crash after closing the first tab instead of getting messed up settings.
Steps:
1. Start a fresh copy of TeSSH.
2. Create a new session and save it.
3. Connect to the session 'Offline'.
4. Open the Sessions window again.
5. Connect a second time to the session 'Offline'.
6. Open the Package Editor and note the current (empty) settings in each tab.
7. Close the Package Editor.
8. Right-click on the first (left) connection tab and pick 'Close'.
Results:
Either:
- TeSSH crasshes.
- Messed up settings are seen in the Package Editor. (The session name is missing from the tree, and there are two settings under Clickable URLs showing.) |
|
|
|
Zugg MASTER
Joined: 25 Sep 2000 Posts: 23379 Location: Colorado, USA
|
Posted: Mon Feb 08, 2010 5:43 pm |
I'll add that to the bug list and take a look at it.
|
|
|
|
Nezic Apprentice
Joined: 10 Oct 2000 Posts: 119 Location: Colorado
|
Posted: Tue Feb 23, 2010 10:18 pm |
By the way, here is the crash report info for this (can't believe I forgot to include it before):
Code: |
date/time : 2010-02-23, 15:15:53, 563ms
computer name : #####
user name : #####
registered owner : #####
operating system : Windows Vista Service Pack 1 build 6001
system language : English
system up time : 5 days 22 hours
program up time : 41 seconds
processors : 2x Intel(R) Core(TM)2 Duo CPU T7500 @ 2.20GHz
physical memory : 1058/3070 MB (free/total)
free disk space : (C:) 39.29 GB
display mode : 1920x1200, 32 bit
process id : $13f8
allocated memory : 67.30 MB
executable : TeSSH.exe
exec. date/time : 2010-02-08 11:54
version : 3.14.0.1
compiled with : BCB 2006/07
madExcept version : 3.0k
contact name : #####
contact email : #####
callstack crc : $66cfe471, $2ae5395a, $2ae5395a
exception number : 1
exception class : Exception
exception message : Error saving data in background - UPDATE settings SET userval='{CC2F280A-CD26-45E1-B1CC-0CBD8991CA60}' WHERE id = 0 :: SQL Error: database is locked.
Main ($15cc):
00e7261c +250 TeSSH.exe PkgDM 4877 +43 TPkg.Save
00d7d2a7 +02b TeSSH.exe PARENT 7947 +5 CloseModule
00d7d480 +1a8 TeSSH.exe PARENT 7992 +39 TParentForm.CloseSession
00d7d5f6 +04a TeSSH.exe PARENT 8039 +3 TParentForm.CloseWindow
00d755b6 +0be TeSSH.exe PARENT 4146 +13 TParentForm.CloseWindow1Click
00d7e3d9 +011 TeSSH.exe PARENT 8604 +1 TParentForm.WMCloseWindow
004bfe9f +2bb TeSSH.exe Controls TControl.WndProc
004c3ea3 +4fb TeSSH.exe Controls TWinControl.WndProc
004a6403 +553 TeSSH.exe Forms TCustomForm.WndProc
00d25e38 +020 TeSSH.exe DXSounds 2128 +9 TCustomDXSound.FormWndProc
00d24328 +00c TeSSH.exe DXClass 635 +1 TControlSubClass.WndProc
004c35cc +02c TeSSH.exe Controls TWinControl.MainWndProc
0047d868 +014 TeSSH.exe Classes StdWndProc
761db9fc +016 USER32.dll CallWindowProcA
0070c863 +0a7 TeSSH.exe aqDockingUtils 1728 +7 CallDefWndProc
0070c951 +0dd TeSSH.exe aqDockingUtils 1776 +41 TaqWindowEventFilter.WndProc
0047d868 +014 TeSSH.exe Classes StdWndProc
761c5a27 +00a USER32.dll DispatchMessageA
004ae578 +0fc TeSSH.exe Forms TApplication.ProcessMessage
004ae5b2 +00a TeSSH.exe Forms TApplication.HandleMessage
004ae8a7 +0b3 TeSSH.exe Forms TApplication.Run
00ecc1fc +088 TeSSH.exe TeSSH 317 +20 initialization
766a490f +010 kernel32.dll BaseThreadInitThunk |
|
|
|
|
Zugg MASTER
Joined: 25 Sep 2000 Posts: 23379 Location: Colorado, USA
|
Posted: Wed Feb 24, 2010 5:25 pm |
Yep. What is happening here is that both sessions are trying to simultaneously save their settings to the same package file. That's why the error says "database is locked"....it is locked by the other thread that is saving the settings for the other session. Closing the Package Editor triggers the forced save of settings, as does closing a session window.
|
|
|
|
|
|