Command window bug

[Anna]

Hello -

Twice now when I used the Command Window to compile a very large package (20,000+ lines, 963KB), my PL/SQL Developer session does not return. Just now I tried it again, and I saw that PL/SQL was using increasing amounts of memory and about 90% of my CPU time.

A similar error occurred when I used the Compile Invalid Objects and one of them was a large package. I did not look at my CPU and memory usage then, but the window never returned - I had to use Task Manager to kill PL/SQL Developer.

I am using a 5 license version of 5.1.4.730 77.71872.

Anna

 

[Marco Kalter]

I am not aware of such a problem. I don't assume this is reproducible?

 

[Anna]

Hi Marko,

Yes, it is reproducable. Everytime I try to compile the same package. Also, today I used the Export table command to export (as SQL Inserts) 246000+ rows to a file. This went okay. Then I tried to using the Import tables command to insert those rows into our test environment. This process caused my PLSQL Developer session to eat up 200+ MB of RAM and most of my CPU process.

Thanks for replying!

Anna

 

[Marco Kalter]

Okay. Can you send me this package as an e-mail attachment?

 

[Anna]

Hi Marco,

First, I'm sorry that I've called you Marko twice now. I don't know why I keep reading your name wrong. In any case, I've just sent the package to your email address.

Thanks for your help! I really do like PL/SQL Developer a lot and think it's the best product of it's type.

Thanks,

Anna