Hello,

When I work with maximized PL/SQL with many windows when switching between windows menu flashes and long does it take to switch or close the window.

Are you perhaps using Remote Desktop?

I Am experiencing the exact same issue (same version), Remote desktop or no. It goes away when i restart the app, but comes back after using it for a while. The previous version I had installed did not do this.

In addition since installing this new version I've experienced toolbar "whiteouts" where all the toolbar buttons white out but are still able to be clicked. TO fix this one I must close all instances and restart.

My workaround, so far, is to minimize all instances and restore the one I need.
State - Memory Usage
Working - 50MB
Minimized - 5MB
Restore - 10MB

It really reduces flickering.

Regards,
Gustavo

Thanks for the advice Gustavo!

Also wanted to add a screenshot of the menu whiteout:

http://tinypic.com/r/21aco7b/5

Seems to be related to leaving the app open for a long period of time...

I have been having the same problem since an earlier release (probably 9.0.1). There was an earlier post about this issue. Somebody solved it by installing the latest NVidia driver, but that didn't work for me.

My workaround is to un-minimize the window then stretch it to maximum.

I'm just going to go back to version 8 I think. No real response here to the issue so hopefully they're not ignoring it.

No,I do not use remote Desktop.

I have the same problem. It happens when using Remote Desktop and stays even after returning to the console. It also happens after switching users. Restarting the application does NOT fix it.

I have found one way to fix it when not using Remote Desktop by changing the Windows Theme to Windows Classic and then switch it back to Windows 7.

Thanks to this thread I found that when the window is not maximized the problem disappears, but I hope that it will be fixed in the next release because it's still very annoying.

PS: I am using version 9.0.4.1644

I have the same problem using 9.0.5.1648. For me, it is triggered mostly by the "view table" action. I don't use Remote Desktop.

The view table action takes about 4 seconds of flickering, then the UI stabilizes.

The worst part is that this 4 seconds delay increases exponentially if I try to view multiple tables by selecting them first, then using "view table" on the selection.

For example if I select 12 tables the rendering doesn't finish for at least 24 minutes (twenty four minutes). It seems opening multiple "view table" windows simultaneously triggers a huge redraw storm, each window generating redraw events for the other windows, that in response generate other redraw events, and so on.

While this happens, it completely saturates one CPU core.

Closing a "view table" window is also slow, about two seconds, for similar reasons.

To understand the exponential nature of the problem, see the following table:

[Number of selected tables] -> [View table rendering delay]
1 table -> 4 seconds
2 tables -> 6 seconds
3 tables -> 9 seconds
4 tables -> 66 seconds
5 tables -> 190 seconds
6 tables -> 270 seconds
12 tables -> 1440 seconds (actually more then that, but I killed it after 24 minutes)

This is not something new. I've been using PL/SQL Developer for 10 years, and I've always had similar problems when using many windows.

But I find it unacceptable that in 2012, on system with a Core i7 quad core CPU, 8 GB of RAM, SSD, and 1024 MB video card I have to wait minutes to open a few tables.

I think it may be a good time for a full rewrite of the application using a modern framework, like .NET or, even better, Java. Especially when many people that need this application cannot use it because they use Mac OS or Linux.

I uploaded a video recording to document the issue.

http://www.mediafire.com/file/tpx5mfoj4oo14gc/WP_20120201_171033Z.mp4