dbForge Studio trial is crashing

[alexa]

Could you please perform the following:
1. Download and install one of the following debuggers https://go.microsoft.com/fwlink/p/?LinkId=526733 or http://www.microsoft.com/whdc/devtools/ddk/default.mspx
2. Run windbg.exe . By default it is located in

Code: Select all

c:\Program Files (x86)\Windows Kits\10\Debuggers\x64\

3. Select 'File -> Open Executable' from the main menu.
4. Select the dbforgemysql.exe file.
5. Select 'Debug -> Go' from the main menu.
6. Reproduce the issue.
7. Select 'View -> Call Stack' from the main menu and provide us the result.

Also, please check the following folder for the dump and, if it exists, please send it to us for investigation

Code: Select all

%LOCALAPPDATA%\CrashDumps\

[mfolguera]

Hello,

We run debug as you told us. we attach the results

Stack:

Code: Select all

ole32!CClipDataObject::QueryInterface+0xbc
clr!SafeQueryInterface+0xe8
clr!COMInterfaceMarshaler::InitializeFlags+0x54
clr!COMInterfaceMarshaler::FindOrCreateObjectRefInternal+0x106
clr!GetObjectRefFromComIP+0x150
clr!UnmarshalObjectFromInterface+0x50
clr!StubHelpers::InterfaceMarshaler__ConvertToManaged+0xca
System_Windows_Forms_ni+0x84afaf
System_Windows_Forms_ni+0x9486a6
System_Windows_Forms_ni+0x948679
System_Windows_Forms_ni+0x9489cb
Devart_Shell_TextEditor_ni+0x2469df
Devart_Shell_TextEditor_ni+0x20b4c4
Devart_Shell_TextEditor_ni+0x1c6333
Devart_Shell_Studio_ni+0x1dbd36
Devart_Shell_Common_ni+0x2457a3
Devart_Shell_Studio_ni+0x1e35a2
Devart_Shell_Studio_ni+0x22a84a
Devart_Shell_Studio_ni+0x22b1f8
Devart_Shell_Studio_ni+0x2085c0
Devart_Shell_Studio_ni+0x246283
0x00007fff`2beafa03
System_Windows_Forms_ni+0x246052
System_Windows_Forms_ni+0x261040
System_Windows_Forms_ni+0x2607ec
System_Windows_Forms_ni+0x2605e5
Devart_Shell_Studio_ni+0x251b82
Devart_Shell_Studio_ni+0x2510be
dbforgemysql_ni+0x14147b
clr!CallDescrWorkerInternal+0x83
clr!CallDescrWorkerWithHandler+0x4e
clr!MethodDescCallSite::CallTargetWorker+0xf8
clr!RunMain+0x1e7
clr!Assembly::ExecuteMainMethod+0xb6
clr!SystemDomain::ExecuteMainMethod+0x664
clr!ExecuteEXE+0x3f
clr!CorExeMainInternal+0xb2
clr!CorExeMain+0x14
mscoreei!CorExeMain+0x112
MSCOREE!CorExeMain_Exported+0xb
KERNEL32!BaseThreadInitThunk+0x14
ntdll!RtlUserThreadStart+0x21

Debug Main Window:

Code: Select all

(19b4.4e9c): C++ EH exception - code e06d7363 (first chance)
(19b4.4e9c): C++ EH exception - code e06d7363 (first chance)
(19b4.4e9c): C++ EH exception - code e06d7363 (first chance)
(19b4.4e9c): C++ EH exception - code e06d7363 (first chance)
(19b4.4e9c): C++ EH exception - code e06d7363 (first chance)
(19b4.4e9c): Windows Runtime Transform Error - code 40080202 (first chance)
(19b4.4e9c): C++ EH exception - code e06d7363 (first chance)
(19b4.4e9c): C++ EH exception - code e06d7363 (first chance)
(19b4.4e9c): C++ EH exception - code e06d7363 (first chance)
(19b4.4e9c): C++ EH exception - code e06d7363 (first chance)
(19b4.4e9c): C++ EH exception - code e06d7363 (first chance)
(19b4.4e9c): C++ EH exception - code e06d7363 (first chance)
(19b4.4e9c): Access violation - code c0000005 (first chance)
First chance exceptions are reported before any exception handling.
This exception may be expected and handled.
ole32!CClipDataObject::QueryInterface+0xbc:
00007fff`c1c5444c 488b00          mov     rax,qword ptr [rax] ds:feeefeee`feeefeee=????????????????
*** WARNING: Unable to verify checksum for C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\System.Windows.Forms\3ff93d82615268dec17455e71346a529\System.Windows.Forms.ni.dll
*** WARNING: Unable to verify checksum for C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\Devart.Shel3a7cba17#\f1e5e72f0cca4ad6d405702fa34eacb0\Devart.Shell.TextEditor.ni.dll
*** ERROR: Module load completed but symbols could not be loaded for C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\Devart.Shel3a7cba17#\f1e5e72f0cca4ad6d405702fa34eacb0\Devart.Shell.TextEditor.ni.dll
*** WARNING: Unable to verify checksum for C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\Devart.Shell.Studio\e517a5b970ec291400ead2d49b6afa53\Devart.Shell.Studio.ni.dll
*** ERROR: Module load completed but symbols could not be loaded for C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\Devart.Shell.Studio\e517a5b970ec291400ead2d49b6afa53\Devart.Shell.Studio.ni.dll
*** WARNING: Unable to verify checksum for C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\Devart.Shell.Common\090981667f5a470193a5763dd21d6576\Devart.Shell.Common.ni.dll
*** ERROR: Module load completed but symbols could not be loaded for C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\Devart.Shell.Common\090981667f5a470193a5763dd21d6576\Devart.Shell.Common.ni.dll
*** WARNING: Unable to verify checksum for C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\dbforgemysql\c6271e0ead8e221cf05e8906fb2e5d5a\dbforgemysql.ni.exe
*** ERROR: Module load completed but symbols could not be loaded for C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\dbforgemysql\c6271e0ead8e221cf05e8906fb2e5d5a\dbforgemysql.ni.exe

I have no folder in %LOCALAPPDATA%\CrashDumps\

[alexa]

Thank you for the reply.

Could you please let us know if the issue reproduces constantly and provide us the content of the clipboard at the moment of the error? You can check this with the following tool http://www.freeclipboardviewer.com/clipbrd.exe.html

[mfolguera]

Thank you for the reply.

Could you please let us know if the issue reproduces constantly and provide us the content of the clipboard at the moment of the error? You can check this with the following tool http://www.freeclipboardviewer.com/clipbrd.exe.html

Sorry for answer delay... . At crash moment I only have this content in clipboard:

Code: Select all

                
if (m_valuation_value_range_id > 0)
                {
                    if (l_is_first)
                    {
                        l_str.Append("?");
                        l_is_first = false;
                    }
                    else
                    {
                        l_str.Append("&");
                    }
                    l_str.Append(CM.Config.Querystring.valuation_value_range.ToString());
                    l_str.Append("=");
                    l_str.Append(m_valuation_value_range_id.ToString());

                }

Thanks in advance

[alexa]

You could try turning off the antivirus or add dbForge to the exceptions list.

[[email protected]]

Hi,
I have the same problem,
I've installed the dbforge updates every time I get a popup, but it keeps crashing ...
It worked ok before (for over a year), I think for me it started crashing after the Win 10 creator update ...

It always happens when dbforge studio is idle for a little while ... (even as little as 15 min ..)
Popup "has stopped working" -> close and restart and it resumes as it was before ...

[alexa]

Could you please perform the procedure we described earlier with the only difference that dbForge Studio for MySQL needs to be installed with the 'Do not generate images' option on the 'STARTUP OPTIMIZATION' page of the install wizard.

So, please perform the following:
1. Uninstall dbForge Studio for MySQL.
2. Install it selecting the 'Do not generate images' option on the 'STARTUP OPTIMIZATION' page of the install wizard.
3. Download and install one of the following debuggers https://go.microsoft.com/fwlink/p/?LinkId=526733 or http://www.microsoft.com/whdc/devtools/ddk/default.mspx
4. Run windbg.exe . By default it is located in

Code: Select all

c:\Program Files (x86)\Windows Kits\10\Debuggers\x64\

5. Select 'File -> Open Executable' from the main menu.
6. Select the dbforgemysql.exe file.
7. Select 'Debug -> Go' from the main menu.
8. Reproduce the issue.
9. Select 'View -> Call Stack' from the main menu and provide us the result.
10. Check the following folder for the dump and, if it exists, please send it to us for investigation

Code: Select all

%LOCALAPPDATA%\CrashDumps\

You can send a reply straight to our support system at supportATdevartDOTcom and alexaATdevartDOTcom.

[molino]

Hello,
I also have a lot of crashes of dbforge when it is for some time in idle. It crashes often multiple times a day which makes the work with dbforge a pain
Developing under Windows 10 installed on VMware Workstation.

[SimonT]

I want to chime in here and say that I have the same issue with dbForge Studio for SQL Server. It randomly crashes in the background. Here is the relevant error from the Event Viewer:

Faulting application name: dbforgesql.exe, version: 5.4.275.0, time stamp: 0x58cbf3e9
Faulting module name: ucrtbase.dll, version: 10.0.15063.413, time stamp: 0x5ba8b66e
Exception code: 0xc0000409
Fault offset: 0x00000000000734be
Faulting process id: 0x2454
Faulting application start time: 0x01d307de04dfc6ff
Faulting application path: C:\Program Files\Devart\dbForge Studio for SQL Server\dbforgesql.exe
Faulting module path: C:\WINDOWS\System32\ucrtbase.dll
Report Id: 35adee6c-2681-49ed-a800-02161a321163
Faulting package full name:
Faulting package-relative application ID:

I do not have time to debug further.

[alexa]

In accordance with http://www.edugeek.net/forums/office-so ... ashes.html , you could try making the following registry entry:
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows\LegacyDefaultPrinterMode (DWORD) Set the value from 0 to 1
It changes the Switch for the Standard Printer off.

In that article, it's said that Word crashes with similar errors. It uses the same system modules as dbForge. So, we suspect the issue initially lies in some Windows updates.

[mfolguera]

No changes for me, it still crashing...

[alexa]

We are currently working on resolving this issue with Microsoft and awaiting their reply on this.

We will answer you as soon as any result is achieved.

[mfolguera]

It seems that we have found a pattern that repeats when DBForge crash. At the time of crash, a SQL file hosted in a synchronised Google Drive folder are open. It's a file with a large number of not very complex INSERT INTO.

Look like:

INSERT INTO xxxxxxxxxx (field1, field2, field3, field4, field5) VALUES(XX,XX,XX,XX,XX);
INSERT INTO xxxxxxxxxx (field1, field2, field3, field4, field5) VALUES(XX,XX,XX,XX,XX);
INSERT INTO xxxxxxxxxx (field1, field2, field3, field4, field5) VALUES(XX,XX,XX,XX,XX);
INSERT INTO xxxxxxxxxx (field1, field2, field3, field4, field5) VALUES(XX,XX,XX,XX,XX);
...

We have over 600 lineas

I wish it to be helpful

[GeybSF]

It seems that we have found a pattern that repeats when DBForge crash. At the time of crash, a SQL file hosted in a synchronised Google Drive folder are open. It's a file with a large number of not very complex INSERT INTO.

Look like:

INSERT INTO xxxxxxxxxx (field1, field2, field3, field4, field5) VALUES(XX,XX,XX,XX,XX);
INSERT INTO xxxxxxxxxx (field1, field2, field3, field4, field5) VALUES(XX,XX,XX,XX,XX);
INSERT INTO xxxxxxxxxx (field1, field2, field3, field4, field5) VALUES(XX,XX,XX,XX,XX);
INSERT INTO xxxxxxxxxx (field1, field2, field3, field4, field5) VALUES(XX,XX,XX,XX,XX);
...

We have over 600 lineas

I wish it to be helpful

I was try it,nope.
Sadly is not working...At Least for me.
Maybe there are other reasons and solutions to the problem?thanks in advance.
As one writer said:"My dream will come true,but no."

[mfolguera]

It seems that we have found a pattern that repeats when DBForge crash. At the time of crash, a SQL file hosted in a synchronised Google Drive folder are open. It's a file with a large number of not very complex INSERT INTO.

Look like:

INSERT INTO xxxxxxxxxx (field1, field2, field3, field4, field5) VALUES(XX,XX,XX,XX,XX);
INSERT INTO xxxxxxxxxx (field1, field2, field3, field4, field5) VALUES(XX,XX,XX,XX,XX);
INSERT INTO xxxxxxxxxx (field1, field2, field3, field4, field5) VALUES(XX,XX,XX,XX,XX);
INSERT INTO xxxxxxxxxx (field1, field2, field3, field4, field5) VALUES(XX,XX,XX,XX,XX);
...

We have over 600 lineas

I wish it to be helpful

I was try it,nope.
Sadly is not working...At Least for me.
Maybe there are other reasons and solutions to the problem?thanks in advance.
As one writer said:"My dream will come true,but no."

Yes, it seems that for a while now it is falling more often without reason, 10 or more in a day. even without many open files. it's crazy! I really like the environment in dbforge, but I think I'll try another alternative. It's a pity because in our company we believe in buying the pro version, but with this behavior, no way....