About Duffbert...

Duffbert's Random Musings is a blog where I talk about whatever happens to be running through my head at any given moment... I'm Thomas Duff, and you can find out more about me here...

Email Me!

Search This Site!

Custom Search

I'm published!

Co-author of the book IBM Lotus Sametime 8 Essentials: A User's Guide
SametimeBookCoverImage.jpg

Purchase on Amazon

Co-author of the book IBM Sametime 8.5.2 Administration Guide
SametimeAdminBookCoverImage.jpg

Purchase on Amazon

MiscLinks

Visitor Count...



View My Stats

« All the Linux activity of late... Ramifications? | Main| So why is it called i18n? »

Memory Is Not Released by the LotusScript PRINT and MESSAGEBOX Statements

Category Software Development

Wow...  this is a sneaky little bug that I didn't know about...  Whoops...  'Cuse me...  That's a "feature" as it is now documented...  :-)

From the KnowledgeBase...

Memory Is Not Released by the LotusScript PRINT and MESSAGEBOX Statements

Document Number:   1089676

Problem
Under certain circumstances, the Print and MessageBox LotusScript statements consume memory without releasing it.

For example, when a particular customer included the Print statement in a loop with a large number of cycles, a crash occurred with the following error:

"Maximum number of memory segments that Notes can support has been exceeded"

Content
The memory used by the Print and Messagebox commands is released once the agent finishes running.  The workarounds are to avoid using the statement(s) in large loops or reduce the number of statements.

This issue was reported to Lotus Quality Engineering; however, it was determined that LotusScript is functioning as designed.
 

Comments

Gravatar Image1 - Ouch. That might explain some problems I have had before. To what releases of Notes does it apply?

Gravatar Image2 - yep. I ran into this just last week. I had a bunch of debug 'funciton calls' in a huge scripted agent. I changed the debug function to use msgbox and WHAM. I was running out of stack space left and right. Print didn't seem to be as bad with this. In fact, I havn't had any problems with the print statement.

Gravatar Image3 - The technote says 5.0 and 4.x, but it also states that LS is "functioning as designed". To me, that says it's still an issue in 6.x too...

Gravatar Image4 - Functioning as designed... erm, it was designed with a memory leak on purpose?

I was having that problem with a R5.11 server.

Post A Comment

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

Want to support this blog or just say thanks?

When you shop Amazon, start your shopping experience here.

When you do that, all your purchases during that session earn me an affiliate commission via the Amazon Affiliate program. You don't have to buy the book I linked you to (although I wouldn't complain!). Simply use that as your starting point.

Thanks!

Thomas "Duffbert" Duff

Ads of Relevance...