We have been experiencing numerous sudden crashes of Toad in a variety of circumstances. I posted one in this topic (Crash Bug in Connections Dialog), but there have been many more.
We use 25.3 exclusively in our VDI environment in which is AWS. In my case, it is in Windows Server 2019. I had a crash this morning and yesterday morning as well. The support bundle does not reflect today’s crash though.
Today, I was working in the Editor and had opened a describe window. When I closed that describe window, Toad just vanished without reporting any errors. The crash bundle does not show today’s crash in the “Most Recent Error Detail” section. Instead, it shows the crash that occurred yesterday.
I can submit that crash bundle but would rather not do so here.
Cheers,
Russ
LOLs That most recent crash in the bundle was actually for Monday week past, and I’ve had three of four crashes since then. I saw Mon, Jan 5 in the date and thought, “Today’s Tuesday, so must have been from yesterday.”
When Toad vanishes, it's usually a stack overflow (at least that's the only cause of vanishing that I'm aware of) and in stack overflows, we aren't able to collect an error log.
It's only the times that you see this kind of dialog where we collect the error log
There must be something about your VDI environment that Toad doesn't like. We've had a few odd problems with server 2019 in the past but nothing this severe.
Can you tell me what software is used to enable the VDI environment? Maybe I can replicate it.
You are of course always welcome to send me your call stacks or error logs by email - john.dorlon@quest.com.
I have emailed that support bundle. I have official hoops to jump through to do that, but you should have it now.
Toad’s vanishing trick is a new feature of 25.3. We did not see it in prior versions. Also, I found that my VDI is running Windows Server 2022.
We connect to our VDIs using Amazon Workspaces Client version 5.30.0.5657.
Cheers,
Russ
Thanks, I got it. Was about to say - looks like you are on server 2022. I'll try Amazon workspaces client and see what happens.
I'm not sure (yet) why 25.3 has the problem and prior versions did not. 26.1 will be coming out soonish (late Feb). Hopefully we'll get lucky and the problem will go away again in that version!
Well, it happened again. I had a describe window open, and Toad vanished within about a second of closing that window. There was only one connection with only an editor open which had a couple tabs. I had just launched Toad and had not done very much, so it was not very heavily loaded when this happened.
Cheers,
Russ
In both of the cases that you've mentioned, the problems seem to be when popup windows are closed. Do the crashes you've been having all have this in common?
I can replicate that crash by the following steps:
- Launch Toad.
- Open a connection.
- In the Editor tab, “desc dbms_xplan”.
- Do something in the describe window like navigating to a function.
- Close the describe window.
- Toad crashes.
It did not crash if I just opened a describe and then closed it again. It only crashed after I navigated to a function. Maybe Toad caught on to the fact that I was looking at an undocumented function.
Cheers,
Russ
huh. interesting - and puzzling.
I replicated my other crash issue in a Toad that I had just opened and had not connected to anything. In this situation, Toad threw up an error dialog.
I am working on getting that Toad.el file to you. At the bottom is info about the last crash. That file records my O/S as Windows 2019 Server. I confirmed in the O/S that mine is 2022 Datacenter edition, so I don’t know why the discrepancy.
I should point out that I have to use this Windows edition because of some things we need that go beyond the norms. I hope it is not Windows that is causing trouble.
Cheers,
Russ
It seems unlikely. You are not the only user of Win Server 2019 or 2022. I would think not even with AWS VDI. We're trying to get that set up here, but it's non-trivial, as they say.
Yeah, that is is certainly NOT trivial.
You should have the Toad.el file now.
Cheers,
Russ
Got it, thanks. That call stack looks like the one you sent in Nov. If the problem happens from other windows besides Oracle Client and describe, let me know.
Yeah, there are lots of “events” in that log.
I just triggered a crash using Help+About in a new Toad session with nothing else open.
Also, just opening and closing Help, About over and over again does not crash Toad. But, if I click one of the tabs such as Licenses and then OK, it dies.
I can also make it crash in Settings.
Ok. I think I know the common thread is here, but still not exactly why the error happens.
The call stacks indicate that the AV has to to with Windows Narrator screen reader features on a particular type of control that we use (and I know you don't have that enabled, which is weird, but this code shouldn't fire unless you have it on). But I can add an option to disable that code. Since it won't be useful for most users, would work for you if I just gave you a way to disable it by an entry in Toad.ini? Is that easy for you to get to/edit in your environment? If not, I can put it in options somewhere.
Also, another weird thing is that this code (the screen-reading code) was in place starting in Toad version 25.2, so I don't know why you didn't have the problem in that version. But this is all I have to go on for now...
-John
