Toad for Oracle is giving me a memory access violation EVERY time I start it up.
This started (for me) in Toad for Oracle 126.96.36.199, freeware edition.
It happens after clicking the “Connect” button in the session/connection chooser.
(Actually, it happens EVERY time it starts to make a new connection.)
If you click on the link for the additional information, it provides a lot of it but it’s probably only useful to a developer on the Toad Team.
Here’s at least the exception identity:
2.1 Date : Fri, 28 Aug 2015 13:35:41 -0400
2.2 Address : 072EA6C8
2.3 Module Name: Toad.exe - (Toad™ for Oracle®)
2.5 Type : EAccessViolation
2.6 Message : Access violation at address 072EA6C8 in module ‘Toad.exe’. Read of address 00000004
2.7 ID : 5DFB0000
2.8 Count : 1
2.11 Sent : 0
The two addresses and the ID are always the same.
The assembler window also has a couple of interesting comments:
; ToadRegistration.TToadKey.GetKeyDesc (Line=0 - Offset=13)
— disassembly stuff elided here.
; ToadRegistration.TToadKey.GetKeyType (Line=0 - Offset=0)
072EA6C8 83780400 CMP DWORD PTR [EAX+4], 0 ; <-- EXCEPTION
072EA6CC 7403 JZ +3 ; ($072EA6D1) ToadRegistration.TToadKey.GetKeyType (Line=0)
What is REALLY odd is that every time I do a connection, I also get the “Commercial Feature” warning dialog! (I doubt it means an ordinary database connection is a commercial feature, so this may be a clue that it’s trying to do something that the freeware edition shouldn’t.
Here’s hoping that some of the developers of Toad are readers of this forum!
What’s also odd is that after the violation, it seems to connect and operate normally. Which leads me to wonder what happened to the thread that crashed? Did it clean up after the exception?