« Phrases I am truly tired of | Main| A corollary for Bruce »

Mea Culpa


I had made the argument several times on this IdeaJam thread that I simply never encountered Notes crashes that failed to invoke the NSD cleanup process.  Well, I encountered one today.  I tried to Redim an array at runtime outside of the allowable boundaries of an array in the Notes 8.0.1 client.  The Notes C++ client crashed mightly, but the Eclipse context kept running until I forcibly shut it down with the Task Manager.

This is the first time I've encountered such an error since I began beta testing Notes 8.0.0 at the end of 2006.  But in the interest of fairness to the other commenters on that thread, I have now seen the Notes 8 client crash in such a way as I had to shut down individual processes.

Note: this in no way changes the fact that I think people get puffed up about this issue needlessly.  You really should be fixing the things that CAUSE crashes, rather than worrying about whether Notes crashes gracefully or not.

/me gets back to his script to do some proper bounds checking.

Comments

1 - Welcome to the club!

Poor end users typically CAN'T fix the 'root' causes, and they DO care if Notes crashes gracefully or not.

If developers make up 2% of the Notes user base, I'd be surprised.

Aye-letes unite...

2 - Another bit of info...
So I had an nice little crash yesterday, and I let NSD do it's thing.

It took 10 minutes for NSD to finish, which is wayyyy to long IMO..

3 - Craig, "fixing the things that CAUSE crashes" is neither up to end users, nor is it up to Notes developers. It's up to Notes' developers.

Providing illegal array boundaries should cause a run-time error for sure (and since you can write code to pretest for these conditions, you probably should for the sake of your business logic). But it should definitely not crash the whole run-time environment. This is not C or assembler code running on bare metal.

4 - Don't forget the implications this has with the *server*. If your code was running in an agent that had made it into production I think you'd feel quite a bit differently if your server was coughing up blood from a simple ReDim() statement. If I wanted to handle my own memory management I'd be writing in C.

I am glad to hear that 8.x is as reliable as some people are describing it. We're still cruising on 7.x (8.0.2 will likely be the first release that truly addresses all our show-stoppers), and while NSD does run most of the time we still get the occasional MS Runtime Error or RBOD.

5 - >load nostalgia

Ah, RBOD....

>tell nostalgia q

Post A Comment

:-D:-o:-p:-x:-(:-):-\:angry::cool::cry::emb::grin::huh::laugh::lips::rolleyes:;-)

Hire Me 

Lotus-911-Logo.jpg

Search 

Disclaimer 

Welcome to Escape Velocity!

Opinions expressed here by Nathan T. Freeman are not necessarily those of his employer. However, there's a decent chance they are, so check with them if you really want to know.

But really... do you need that kind of validation? Are the opinions expressed here in doubt?

MiscLinks