Shop OBEX P1 Docs P2 Docs Learn Events
Spin Tool "Run Time Memory Error" but program has more than 5,000 longs free — Parallax Forums

Spin Tool "Run Time Memory Error" but program has more than 5,000 longs free

vanmunchvanmunch Posts: 568
edited 2014-06-27 21:03 in Propeller 1
Hey Everyone,

I was wondering if someone could share some light on what is going on. I'm trying to work on a program that should only take up about 3K longs, but I keep getting a "Run time memory Error" saying that the "object exceeds run time memory limit by 758 longs" Is this a known bug with Propeller tool 1.3? I've never had this before and there is plenty of memory left. I haven't had any trouble with much larger programs working...

Anyone else ever have this happen?

I appreciate your thoughts.

Dave

Comments

  • Phil Pilgrim (PhiPi)Phil Pilgrim (PhiPi) Posts: 23,514
    edited 2014-06-20 13:48
    I've never seen it make that report in error. Can you attach an archive of your program?

    -Phil
  • vanmunchvanmunch Posts: 568
    edited 2014-06-20 13:57
    Phil Pilgrim (PhiPi) wrote: »
    I've never seen it make that report in error. Can you attach an archive of your program?

    -Phil

    Hey Phil, can I Email it to you? I'me just starting to combine two different programs and it looks terrible. It gives me the same error when I try to archive it and I just tried it with 1.3.2.

    Dave
  • Phil Pilgrim (PhiPi)Phil Pilgrim (PhiPi) Posts: 23,514
    edited 2014-06-20 14:51
    'Forgot that it has to compile in order to archive. 'Prefer to work within the forum so that others may benefit. Can you just zip your main program and all the objects it uses together and post it here?

    -Phil
  • vanmunchvanmunch Posts: 568
    edited 2014-06-20 14:58
    Phil Pilgrim (PhiPi) wrote: »
    'Forgot that it has to compile in order to archive. 'Prefer to work within the forum so that others may benefit. Can you just zip your main program and all the objects it uses together and post it here?

    -Phil

    I normally don't mind posting my code for everyone to use, but this is for a commercial project and I believe that anything posted to the forums is automatically "open"? If that's no good, I'll just slog on by myself. It's probably a "one in a million" or I've done something goofy. I'm sure I'll figure out a work around. :)
  • Phil Pilgrim (PhiPi)Phil Pilgrim (PhiPi) Posts: 23,514
    edited 2014-06-20 15:14
    vanmunch wrote:
    ... but this is for a commercial project ...
    Then by all means, please do NOT email it to me. Being party to confidential info could compromise my own original work if there's any intersection between the two.

    Thanks,
    -Phil
  • vanmunchvanmunch Posts: 568
    edited 2014-06-20 15:23
    Solved it, that is a really weird bug...
  • MrBi11MrBi11 Posts: 117
    edited 2014-06-20 22:31
    Without disclosing any confidential information could you explain what was the cause & solution so we can learn?
  • Dave HeinDave Hein Posts: 6,347
    edited 2014-06-21 05:09
    I've had problems in the past with running out of memory when I include several objects that include the same set of objects. I think the Prop tool initially builds an image with all the duplicate objects, and it then prunes out the duplicates. However, if the initial image with the duplicate objects exceeds 64K it will cause an error. vanmunch, maybe this is the same error you were getting, though my error wasn't "Run Time Memory Error".
  • Cluso99Cluso99 Posts: 18,069
    edited 2014-06-21 18:19
    I have had problems like this with an older version of PropTool. By adding a chunk of vars the problem was solved. Alternatively, you could use bst until you get over the problem.
  • vanmunchvanmunch Posts: 568
    edited 2014-06-27 21:03
    MrBi11 wrote: »
    Without disclosing any confidential information could you explain what was the cause & solution so we can learn?
    Hey MrBi11, sure thing (hopefully Phil doesn't feel contaminated reading this ;) )

    I discovered two other people who had the same problem 6 and 4 years ago. It turns out that the the DAT section isn't tabulated and mine (and theirs) use the graphics object with over sized buffering. I just reduced the size of the buffer a bit and everything is good. :)

    Dave
Sign In or Register to comment.