third_party_content:community:commentary:forums_nonworks:89575b9c1e2b5cb7852565f40013a461

Sign up on the Revelation Software website to have access to the most current content, and to be able to ask questions and get answers from the Revelation community

At 27 APR 1998 11:34:32PM Don Bakke wrote:

What normally causes a break in f.distributer? Is it low available memory?

Thanks,

dbakke@srpcs.com

SRP Computer Solutions


At 29 APR 1998 04:01PM Aaron Kaplan wrote:

Sometimes it's just a simple VEML based on the node or tree list exceeding max length.

apk@sprezzatura.com

Sprezzatura, Inc.

www.sprezzatura.com_zz.jpg


At 29 APR 1998 05:35PM Don Bakke wrote:

Sometimes it's just a simple VEML based on the node or tree list exceeding max length.

Actually, that's the error I normally see (Break on line 3…)

But is this supposed to happen? Shouldn't nodes and tree lists be maintained by the system so this doesn't occur?

My reason for suspecting memory was because this happened on a workstation that was trying to run a report and it only had around 200K of available memory. We rebooted the system and got it back to 230K and the report ran without a hitch.

dbakke@srpcs.com

SRP Computer Solutions


At 30 APR 1998 10:27AM Aaron Kaplan wrote:

Memeory really shouldn't have anything to do with it. Could just be luck of the draw, which is why it breaks randomly. If memory serves, there's not much edit checking in there.

apk@sprezzatura.com

Sprezzatura, Inc.

www.sprezzatura.com_zz.jpg

View this thread on the forum...

  • third_party_content/community/commentary/forums_nonworks/89575b9c1e2b5cb7852565f40013a461.txt
  • Last modified: 2023/12/28 07:40
  • by 127.0.0.1