Crash when doing comparission

Toad Edge
1

Hi guys

I'm doing a database comparison and the process crashes after a few seconds and the toad closes completely

this is the crash log, can someone help me

A fatal error has been detected by the Java Runtime Environment:

EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00007fffbe6c4cd0, pid=29620, tid=34384

JRE version: OpenJDK Runtime Environment (11.0.1+13) (build 11.0.1+13)

Java VM: OpenJDK 64-Bit Server VM (11.0.1+13, mixed mode, tiered, compressed oops, g1 gc, windows-amd64)

Problematic frame:

C 0x00007fffbe6c4cd0

No core dump will be written. Minidumps are not enabled by default on client versions of Windows

If you would like to submit a bug report, please visit:

Crash Report

The crash happened outside the Java Virtual Machine in native code.

See problematic frame for where to report the bug.

--------------- S U M M A R Y ------------

Command Line: -Dfile.encoding=UTF-8 -Dcom.quest.toad.jdbc.mysql8=lib/drivers/mysql-jdbc8.jar -Dcom.quest.toad.jdbc.mysql=lib/drivers/mysql-jdbc.jar -Dcom.quest.toad.jdbc.postgres=lib/drivers/postgresql-jdbc.jar -Dcom.quest.toad.jdbc.edb=lib/drivers/edb-jdbc.jar -Dcom.quest.toad.jdbc.redshift=lib/drivers/redshift-jdbc.jar -Dlog4j.configuration=file:configuration/log4j.xml -Dorg.bouncycastle.fips.approved_only=true -Xbootclasspath/a:lib/bc/bc-fips-1.0.2.jar;lib/bc/bcpkix-fips-1.0.5.jar;lib/bc/bctls-fips-1.0.11.1.jar -Dhttps.protocols=TLSv1,TLSv1.1,TLSv1.2,TLSv1.3 -Dosgi.nl=en_US -Xms128m C:\Program Files\Quest Software\Toad Edge\plugins\org.eclipse.equinox.launcher_1.4.0.v20161219-1356.jar -os win32 -ws win32 -arch x86_64 -showsplash -launcher C:\Program Files\Quest Software\Toad Edge\ToadEdge.exe -name Toad Edge --launcher.library C:\Program Files\Quest Software\Toad Edge\plugins\org.eclipse.equinox.launcher.win32.win32.x86_64_1.1.551.v20171108-1834\eclipse_1630.dll -startup C:\Program Files\Quest Software\Toad Edge\plugins\org.eclipse.equinox.launcher_1.4.0.v20161219-1356.jar --launcher.overrideVmargs -exitdata de8_a4 -vm C:\Program Files\Quest Software\Toad Edge\lib\open-jdk\bin\javaw.exe -vmargs -Dfile.encoding=UTF-8 -Dcom.quest.toad.jdbc.mysql8=lib/drivers/mysql-jdbc8.jar -Dcom.quest.toad.jdbc.mysql=lib/drivers/mysql-jdbc.jar -Dcom.quest.toad.jdbc.postgres=lib/drivers/postgresql-jdbc.jar -Dcom.quest.toad.jdbc.edb=lib/drivers/edb-jdbc.jar -Dcom.quest.toad.jdbc.redshift=lib/drivers/redshift-jdbc.jar -Dlog4j.configuration=file:configuration/log4j.xml -Dorg.bouncycastle.fips.approved_only=true -Xbootclasspath/a:lib/bc/bc-fips-1.0.2.jar;lib/bc/bcpkix-fips-1.0.5.jar;lib/bc/bctls-fips-1.0.11.1.jar -Dhttps.protocols=TLSv1,TLSv1.1,TLSv1.2,TLSv1.3 -Dosgi.nl=en_US -Xms128m -jar C:\Program Files\Quest Software\Toad Edge\plugins\org.eclipse.equinox.launcher_1.4.0.v20161219-1356.jar

Host: Intel(R) Core(TM) i7-8565U CPU @ 1.80GHz, 8 cores, 15G, Windows 10 , 64 bit Build 19041 (10.0.19041.1566)
Time: Thu Mar 10 10:02:00 2022 Hora est�ndar romance elapsed time: 193 seconds (0d 0h 3m 13s)

2

Welcome to the Toad Edge forum...

I cannot reproduce this issue with 2.4.0 (and 2.4.1 just came out... is it happening with the latest version?) I'd test with the latest version first, before anything else.

But if this is happening in the latest versions, please open a Support ticket with Quest, so that the issue can be documented by the engineers. They can attempt to reproduce the issue, and document the resolution for others in Quest's Knowledge Base. They likely will need your inputs (e.g. database version, actual schema DDL to re-create your database/s, etc.