Lost connection due to idle timeout causes Toad to crash. Gets an Access Violation error and ORA-03113 error. (4289694)

Lost connection due to idle timeout causes Toad to crash. Gets an Access Violation error and ORA-03113 error.

When two db server sessions are open (two different servers) and one is at idle for a while (around 10-20 min), when the idle db is accessed again (i.e. click on a taskbar item for that db server), it locks up, hang, or crashes Toad. Toad can just disappear as well. This happens on one specific db only. The other db is fine. There might be an idle timeout setting on the problem database. Toad may not be handling the idle timeout properly, hence it crashes. 

ERRORS:

1) ORA-03113: end-of-file on communication channel

2) Access violation at address 000000000419C77B in module 'Toad.exe'. Read of address FFFFFFFFFFFFFFFF 

This issue is fixed in Toad for Oracle 12.10. This version can be downloaded from the downloads section of our website, which you can access by clicking here.

TOR-994

The Developers found: 1) Can reproduce this with 64-bit 12.7, 12.8, and 12.9. 2) Using a 64-bit client, version 11.2. 3) Start Toad, make 2 connections. 4) Open Object Palette (OP). 5) Shut down the database for the non-active connection in Toad. 6) Switch connections in Toad. 7) Toad disappears. Variations (one at a time, not all at once – interesting ones are 1 and 3): 1: If using a 32-bit version of Toad (with an Oracle 12.1.0.2 client, 32-bit), there is no error at all. 2: If using an Oracle 12 client, Toad shows an EL dialog (the internal one, not the usual one) and then Toad disappears after you click OK. 3: If you don’t open the OP, and instead try to run a query in an Editor after changing connections, you just get a nice Oracle error and Toad does not crash. 4: If you stop and restart the database, so connection is lost but could be re-established, Toad still crashes. 5: If you kill the session instead of shutdown the database, Toad still crashes. So, it seems that there are two possible workarounds: Either: 1. Close the Object Palette (OP), and leave it closed, at least when changing sessions – having it hidden does not count – it needs to be closed. OR 2. Try a 32-bit Toad with a 32-bit Oracle Client. Obviously, the first option would be simpler to try. Toad Dev Team will continue to work on this and fix it so the OP can be left open in 64-bit environment. Note: This issue fixed on Toad Beta 12.10.