Prime lags after extensive processing

[Marcio]

(03-15-2015 06:54 PM)bobkrohn Wrote:  Like I have said, I can't believe more people are not reporting these issues.
They exist, I am not "making this up" for dramatic effect like a Münchausen patient*. I enjoyed reading the wiki article.
The only answer is that very few are doing serious programming on the Prime. Most likely, and that seems to be our problem. Maybe it's a bit too much for a calculator that can't handle large amount of data and has memory management issues.
Have attached screen pics of yesterday's exasperating experience.
I can't fabricate these pics. They are real. Oh, the Chinese characters, I have seen and reported them before on the forums. They suspect it's, again, memory issues. HP needs to address this ASAP.

You mentioned that you discovered your "bad coding".
i.e. "After I figured out where the problem was, I fixed it. "
What exactly was the "bad coding" you did ?
Share so I can see if I'm doing the same thing.

A little math problem. I was evaluating a function that had a heaviside-step like behaviour and it turns out the Prime (or my code?) couldn't handle the abrupt changes (not all PC apps can, ergo the "bad coding", as some people would call), so I smoothed the corners by replacing the original a function with a similar one that had similar behaviour and that gave the same results numerically.
http://en.wikipedia.org/wiki/Heaviside_step_function.

As you say, any legitimate code as defined in documentation should not create these problems. They should be trapped internally.
I'm not doing anything unusual. Reading/Writing Lists, Matrices, Spreadsheet, using text Strings for User input/output, common math Functions (no CAS or complicated Calculus type Functions), using the Triangle solver.
Right now I have no Notes type Subs in use.
Any memory Thrashing should be automatically taken care of, transparent to User.
Even the old HP-41 would occasionally show a message of some sort that said it was compressing the RAM. It just did it on it's own.

I guess that was not implemented in the Prime.

It's an HP problem. We have no control. They have a moral obligation to fix these issues in a timely manner.

Couldn't agree more!!!

Marcio