App Hang on Windows 7 x64
Posted: Wed Dec 05, 2012 4:19 pm
Hi,
I have a program created using D2010 which has ran for many years on XP, which now needs to run on Win7. I am testing using Win7 x64.
When I try to open the TFileOpen or TFileSave dialog in my program, the app hangs. I saw that v6.5.3 introduced a fix for some problem with Windows dialogues, so have just upgraded to v6.5.5, yet the problem still exists.
One form I have can be used in my main project, which uses the Tsilang translation components, and also in a stripped-down utility program (non-translated). The call to (T)FileOpen.Execute causes the app to hang, but only when made in the main (translated) app. The form itself has no translated text or si components.
I see the problem with TFileOpen + TFileSave dialogs (and also the si wrapper components), and also with the Vista Dialog components. Other dialogs such as TOpenTextFile operate normally (though the dialog text items do not change when I change my selected language). Do you treat TFileOpen and TOpenTextFile differently?
The problem does not occur when I add the standard dialogs to your sample programs.
Are you somehow hooking the TFileOpen component / windows standard dialog for an application? Is there a simple way to disable the TsiLang system / switch off any hooks, to make sure that the problem I am seeing is caused by the translation system? I do not want to manually remove the translation components as this would affect over 50 forms, plus many support units.
The call stack for the hung thread shows that it is in ntdll.NtWaitForSingleObject.
Any suggestions would be greatly appreciated. If we can show that the si components (or the way we are using them) are causing the issue then we would be happy to pay for the premium support to make progress.
TIA
Ian
I have a program created using D2010 which has ran for many years on XP, which now needs to run on Win7. I am testing using Win7 x64.
When I try to open the TFileOpen or TFileSave dialog in my program, the app hangs. I saw that v6.5.3 introduced a fix for some problem with Windows dialogues, so have just upgraded to v6.5.5, yet the problem still exists.
One form I have can be used in my main project, which uses the Tsilang translation components, and also in a stripped-down utility program (non-translated). The call to (T)FileOpen.Execute causes the app to hang, but only when made in the main (translated) app. The form itself has no translated text or si components.
I see the problem with TFileOpen + TFileSave dialogs (and also the si wrapper components), and also with the Vista Dialog components. Other dialogs such as TOpenTextFile operate normally (though the dialog text items do not change when I change my selected language). Do you treat TFileOpen and TOpenTextFile differently?
The problem does not occur when I add the standard dialogs to your sample programs.
Are you somehow hooking the TFileOpen component / windows standard dialog for an application? Is there a simple way to disable the TsiLang system / switch off any hooks, to make sure that the problem I am seeing is caused by the translation system? I do not want to manually remove the translation components as this would affect over 50 forms, plus many support units.
The call stack for the hung thread shows that it is in ntdll.NtWaitForSingleObject.
Any suggestions would be greatly appreciated. If we can show that the si components (or the way we are using them) are causing the issue then we would be happy to pay for the premium support to make progress.
TIA
Ian