Category: Rant

I’m coming down to the wire of this database re-architecture task. I’ve been working 60 hours a week for 8 weeks now on this thing, and it’s due this Friday. Unfortunately, I have come to the stunning realization that there is a gaping problem in my design.
Continue reading “Oops”

See this dialog? I’m seeing a lot of it. I’m working on a very large project, and this one particular file is the main GUI for our system. The guy who started it was in love with Visual Age For Java, and didn’t like splitting his stuff into separate classes, and after I took it over I’ve pretty much continued along the same lines, so this file is over 10,000 lines long. Yes, you read that right, ten thousand lines of poorly documented code.

Just about every word you type into Eclipse in this file either leads to a long delay as the CPU maxes out and the disk churns, or this dialog. I’ve tried quitting everything else to provide more memory for it to work in (you’d think 2Gb of RAM would be enough for Eclipse, Safari, iChat and iTunes to get along, and you’d be wrong).

Sigh.

UpdateOk, what sort of moron declares a method to throw “Exception”?

Well, after I got home I tried Adobe Fucking Updater again. This time it popped up a dialog saying “no updates to be installed” so quickly I didn’t even notice how much RAM it was taking. Certainly a far cry from hours and gigabytes of memory that it took when I ran it at work.

Also, I did a Time Machine backup for the first time in a few days. I’d started it in the morning, but it was taking too long so I’d aborted it after about half an hour. I started it again when I got home, and expected it to take 5 or 10 minutes like it usually does, or maybe a bit longer because I’d just installed the Leopard 10.5.2 and Graphics updates. Instead it ground and ground and ground and finally finished 3.5 hours after it had started. I’m told this is because the disk was nearly full, and it had to re-arrange old backups to discard the appropriate old ones.

Adobe is not my favourite software company. I’ve ranted before about splash screens that cannot be moved or covered. Today I was browsing a PDF file in Safari, which was an excruciatingly slow activity for some reason. But then it got an order of magnitude slower, and I see the infamous “Adobe Updater” icon in the dock.

I try to pop up the Activity Monitor to see what’s up. It takes at least 5 minutes, and it shows Safari and Eclipse, the two main reasons for having this computer here at work, as “Not responding”. It also shows that Adobe Updater has an RSIZE of 1.4GB+, and a VSIZE of 3.0GB+, and both numbers are still growing. I kill the Adobe Updater, and Safari and Eclipse both take a while to finish swapping back in their active parts and start working again.

But 10 minutes or so later, the Adobe Fucking Updater starts again. This time I decided to humour it. I closed Eclipse and Safari and waited. And it didn’t take long for the AFU to take up all the memory I had, and then die. I think it got up to about 3.3Gb of VSIZE. And yet, doing a quick back of the envelope calculating, I’m pretty sure it could have sucked every Adobe software product I have on my disk into memory and still not used 3+Gb.

So what the hell is happening? Why is Adobe Fucking Updater so badly written? Why is it chewing memory like that?

I have a theory that it might have something to do with being behind the corporate web proxy (which also sucks mightily). Or it just might be that Adobe’s programmers are incompetent morons who should all be fired and told to never touch a computer again. Or more likely, both. When I get home tonight, I’ll try updating again and see if it really needs more memory than I’m willing to give it.