Navigator fails on body package, crashes on refresh

This does not happen with all of our packages, but most of them - when I open them in TOAD (13.2.0.81), the “first tab” opens fine, navigator looks good, can refresh without issue - but the second tab (package body) the navigator tab is blank, though the file itself looks fine. I click refresh (in the package body tab), and it crashes (not instantly, spinning wheel of death, Windows 10 Pro, still going after 10 minutes).

Fresh download of the Beta, had just opened it, so options should be default. If there is some specific debug information or anything you’d like, let me know. I opened a bunch, and I can’t find any consistent thing between the files that “work” and “don’t” to distinguish them from each other, it just seems to be random.

There is an ongoing issue running Code Analysis on some code at the moment. In your case the workaround may be to disable the “Check rules as you type” option on the Code Analysis page in Options. Let me know if you continue seeing issues after disabling.

You will need to kill this running Toad session though, unfortunately. It will never return.

No problem, was just testing it out anyway - and yes, that was definitely the issue, will disable that in the meantime. Thanks!

also i realized that CPU was high, 40% used by toad, after disabling this option it returns normal .

Hi, we recently updated Toad for Oracle to version 13.2.0.258 and we have the same problem: if we have selected 'Check Rules as you type', some packages won't load into the Editor window and Toad hangs. The same package loads correctly in previous versions of Toad, and it loads correctly if we unmark the option.

Is there a plan to solve the problem, or do we have to go back to version 13.1?

Thanks in advance.

Hi etrabado,

Would you be able to send us an example of a package that doesn't load correctly in Toad 13.2 in a private e-mail? That would help us track down what might be causing what you're seeing. You can feel free to send it to john[dot]bowman[at]quest.com.

Thanks!

-John

Hi! We have had these issues with a few packages in TOAD 13.2.0.258 and just upgraded TOAD to 13.3 hoping the bug was fixed. But the bug still exist!

Brg
JI