Beta 17.1.517.3008 issues

Toad for Oracle - Beta
1

Toad Beta 17.1.517.3008 issues

  1. Blob edit window become ugly
    image

  2. Operations

  • Edit queries and obtain exec plans
  • Close main windows
  • Window closed, but popups "commit transaction" and "save file query" continue to show
  • Toad process remains in memory

Both issues appears in the previous Beta.

2

I see your blob edit is wider now. Is that what you mean by "became ugly"? That window is in the process of being redone (changes coming soon), so I am going to ignore this one for now.

I can't reproduce Toad process staying in memory. :frowning:

3

Hi, John.

OK, thanx.

OK, I try to investigate and give more details.

4

  1. This query shown on exit when the main window already disappeared.
    image

  2. Toad remains in process list.

    image
    image940×33 1.82 KB

5

I don't have any popup windows, but when I exit Toad it also does not always completely close down for me and the process needs to be killed.

Thanks,
Rich

6

Are you closing main windows by the X or File->Exit?
I assume this is when the "file save" first appears. What do you click in that dialog when it appears?

7

By the X upper right button.

8

I answer "No" to this dialog.

9

If you first close all Editor windows before closing Toad does it work as expected?

10

I am partially able to reproduce this with the beta, but not my dev build.

When I click the X, I see the prompts as you describe but then Toad fully shuts down.

11

When I launch the GA version, Process Explorer shows a subprocess for Toad. When I launch the latest beta, it does not. I can supply more details on that subprocess if needed.

GA terminates correctly, but latest beta just hangs out there with no windows associate with it. When I relaunch Toad from killing it, I have an SB fire up with each new connection. The SB is not maximized like it normally would be.

I'm closing Toad with the big red "X".

Rich

12

The GA subprocess... is this another Toad.exe shown or something else? GA will spawn an instance of CertifiedVersionEngine.exe. Beta does not. Here is what GA loads for me.

image
image698×69 8.48 KB

1 Like
13

Yep. That is what I was seeing as well.

Just noting differences. Interestingly, Process Explorer hangs when trying to grab the properties of a Toad process. It's a secret!

Rich

14

No. Process remains.

15

Another scenario, appears on the 17.1.532.3067

  1. Start Toad
  2. Press "New Connection"
  3. Connect
  4. Open "Schema Browser"
  5. Close Toad main window

Toad process remains in memory.

16

Not fixed in the 17.1.543.3127

17

Does Toad always remain in memory regardless of what you do?

What about in these circumstances:

  • Open Toad, do not make connection, do not open any other windows, close Toad
  • Open Toad, make connection, close any windows that automatically open, close Toad
  • Open Toad, do not make connection, open Editor, close Toad
  • Disable themes and then do something you know will leave Toad process running and close Toad
18

Me pasa lo mismo.

19

Open Toad, do not make connection, do not open any other windows, close Toad
Se cierra OK
Open Toad, make connection, close any windows that automatically open, close Toad
Se cierra OK
Open Toad, do not make connection, open Editor, close Toad
Se cierra OK
Disable themes and then do something you know will leave Toad process running and close Toad
NO lo hare porque tengo temor que se me desconfigure el TEMA personalizado

20

You can start Toad using a "virtual" appdata folder that will allow Toad to run as if it were a fresh installation without modifying your current configuration. It uses a temp folder for that run's configuration files and the temp folder is removed when closing Toad.

Start Toad and supply the /VIRTUAL CLEAN switches. Example, Toad.exe /VIRTUAL CLEAN.