dbforge Studio for Sql Server becomes unresponsive

[evan.morgoch]

I'm sorry Alexa, but because it's a random issue that's hard to reproduce, I've haven't been able to work often with the setup you wish to have (2 instances open, one with the start up option set to "Show empty", the other not). However, I was just working today with a single instance open, with the show empty option set as the startup option, and encountered the same issue.

Please let me know how you'd like me to proceed/continue testing.

[user_]

hello

I don't want to be rude, but it's time for you to solve the problem.
Some people have formulated it right here - there is no exact trigger.

Please focus on the interaction with the operating system. The SQL statements are certainly not a trigger.

I am also willing to test - please provide information.

thx

[alexa]

We are very sorry to hear you are still experiencing the issue.

As a temporary workaround, you could try the following:
1. Select 'Tools -> Options...' from the main menu. The 'Options' window opens.
2. Navigate to the 'Environment -> General' branch.
3. Unselect the 'Show splash screen on startup' option.

[evan.morgoch]

Hi Alexa,
I've had that option turned off in my environment for a couple weeks now. Anecdotally, it feels like I'm experiencing the issue a little less, but it is still quite frequent, where in I'll have my window lock up a couple times a day.

[alexa]

Thank you for the reply.

Could you please let us know what functionality causes the issue? What functionality of dbForge was active when it happened?

[evan.morgoch]

Pretty basic for me. I just have a series of T-SQL windows open, with active connections to either one or 2 databases. Most queries will be SELECT statements, and will have had some data loaded.

[alexa]

Please try creating a *.reg file with the content below and, then, executing it with administrator permission:

Code: Select all

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Devart\dbForge Studio for SQL Server\5.4.275.0]
"EnableSystemEventsThreadAffinityCompatibility"=dword:00000001

Please let us know if it helps.

[evan.morgoch]

Hi Alexa, I didn't get a chance to try the registry key you metioned. However, with the 5.5 release, is that key still valid, or should it be changed (possible with the version number updated)? Or does the 5.5 version have any bug fixes in it to address this issue?

[alexa]

That was a workaround for the older version. With the new version, there is no need to make the registry change.

[robains]

Unfortunately I'm having the same issue with v5.5.196 so apparently this has not been fixed.

What will happen is the UI just becomes unresponsive, for example the Execute button is grayed out while I'm in a query builder view.

Even more strange behavior is that sometimes the Execute button will be available and when I click execute it just takes me to the "Text" view and not the Data view. No errors being reported. Once this happens the UI becomes unresponsive again.

The ONLY work around is to exit dbForge and restart dbForge, then everything works. But is clearly a coding problem with v5.5.196 or else the "Work around" I have wouldn't work if it was related to my environment (which is Windows 10 Pro 1703).

I'm about to uninstall v5.5.196 and go back to v5.4.275 which has issues also, but nothing as serious as this problem.

Rob.

[alexa]

This appears to be a different issue that we are going to fix in the next product build.

[robains]

Ok, thank you Alexa.

Cheers, Rob.

[mporemba]

An additional info about 5.4.275 I just found out: After the ui was frozen and I closed it using the taskbar saying "Close Window". Looking at the task manager I saw that it is still running in the background.

[alexa]

An additional info about 5.4.275 I just found out: After the ui was frozen and I closed it using the taskbar saying "Close Window". Looking at the task manager I saw that it is still running in the background.

Could you please describe the actions you perform in dbForge before closing it? Does it happen often?

[mporemba]

As I have written already nothing special. After I executed some select and/or update statements I worked with other application and I locked my work station.

While the splash screen and the update check are deactivated and it started with an empty environment the Studio did not freeze. After I activated all three parts it appeared again.