Holy Memory Leak, Batman. The good news is that although my memory usage on SQLDeveloper has crept up to 775MB this morning before getting slow enough to have to kill it, it did manage to save the file and somewhat interact at that point. It used to be that once it had crept up to about 600MB that it would just go blank and be useless. So, now it seems to tolerate the memory problems better, but still has a problem with memory consumption gradually creeping up to intolerable levels as time goes on.
So, what was I doing that cost all this memory?
I had 5 text files open (not huge files, mind you -- all less than 1000 lines), no database connections open, and I was editing one of the files (Search and Replace, Ctrl-G to go to a line, edit, save, copy paste -- just normal editing). That's it.
Looks like I will have to kill from the Task Manager, as it didn't shut itself down all the way.
SQL Developer has always done this to me. I'm a Developer, so I open the tool in the morning and keep it open. Originally, I had to kill around 2 in the afternoon. With version 1.5.5, I had to kill around 11 in the morning and 2 in the afternoon. With the new version, it looks like I still have to kill, but it manages to use even more memory before I have to kill it.
I've been trying to get my company to switch from TOAD to SQLDeveloper, but nobody else can stand all the bugs. TOAD is a hog, too, and I haven't used it seriously for a couple of years, but the TOAD guys aren't having to kill twice a day. One of the guys on the team really wants to use SQLDeveloper, but he's on Vista and SQLDev is absolutely unbearable on Vista.
Makes me wonder if I'm an idiot for continuing to be a SQLDeveloper junkie. I love the tool, but it's never been smooth, seamless, or reliable. Kinda like driving a DeLorean or something. Well, maybe more like a Yugo. No, it's way cooler and more useful than a Yugo, but certainly not as sleek or fast as a DeLorean. Hmmm.....how about an old Dodge 4x4 truck. Love it to death, it's powerful, cheap and useful, does way cool stuff, but it might die any minute. Maybe I like it because I have a Gambler streak in me and just want to see if I can beat the odds.
So, what was I doing that cost all this memory?
I had 5 text files open (not huge files, mind you -- all less than 1000 lines), no database connections open, and I was editing one of the files (Search and Replace, Ctrl-G to go to a line, edit, save, copy paste -- just normal editing). That's it.
Looks like I will have to kill from the Task Manager, as it didn't shut itself down all the way.
SQL Developer has always done this to me. I'm a Developer, so I open the tool in the morning and keep it open. Originally, I had to kill around 2 in the afternoon. With version 1.5.5, I had to kill around 11 in the morning and 2 in the afternoon. With the new version, it looks like I still have to kill, but it manages to use even more memory before I have to kill it.
I've been trying to get my company to switch from TOAD to SQLDeveloper, but nobody else can stand all the bugs. TOAD is a hog, too, and I haven't used it seriously for a couple of years, but the TOAD guys aren't having to kill twice a day. One of the guys on the team really wants to use SQLDeveloper, but he's on Vista and SQLDev is absolutely unbearable on Vista.
Makes me wonder if I'm an idiot for continuing to be a SQLDeveloper junkie. I love the tool, but it's never been smooth, seamless, or reliable. Kinda like driving a DeLorean or something. Well, maybe more like a Yugo. No, it's way cooler and more useful than a Yugo, but certainly not as sleek or fast as a DeLorean. Hmmm.....how about an old Dodge 4x4 truck. Love it to death, it's powerful, cheap and useful, does way cool stuff, but it might die any minute. Maybe I like it because I have a Gambler streak in me and just want to see if I can beat the odds.
No comments:
Post a Comment