Thread
:
Classic after the latest update – what’s going on?
View Single Post
Member:
RJKinsman
at: 08:36 PM 11/23/2009
Weird. Well, for now I'm happy. Until yesterday I was very frustrated with Classic, but didn't realize it was common among users until reading this forum on Saturday (11/21). I was plagued with the illegal operation error. For example, NVBackup got this 3 out of 4 times. Also, frequently I got it upon startup.
In my experience, it definitely seems related to what else is installed on the Pre. It seems to behave like a type of problem that we call “a storage violation” in the MVS Mainframe world. (Any mainframers out there? But I digress…). So in the “storage violation” scenario, you have a “perpetrator” and a “victim.” The perpetrator wipes out some storage, but ends normally, “unaware” of the damage it left behind (to the extent a piece of application code can be “aware”). Some time later, the victim comes along, attempting to use the storage it trustingly left behind, only to find it corrupt, and it crashes due to unexpected results. This is a very complex problem to resolve, because the perpetrator is long gone before a problem becomes apparent.
Anyway, yesterday, I stumbled on the pattern that Classic seemed more stable if I started it first after a reset (no airplane mode). I was in the habit of starting Agenda (Homebrew App) whenever the Pre started, and I usually followed that with Classic. I decided to start Classic before starting Agenda, and Classic seemed much more stable. Then I deleted Agenda.
At the same time, I was having trouble with fileCoaster (another Homebrew App). I deleted fileCoaster and installed an updated version using WebOS Quick Install. After that, fileCoaster worked fine.
Since all that, I haven't gotten a single Illegal Operation crash, I keep Classic open all the time, and it has been about 36 hours since the last crash. I even got brave and re-installed Agenda, still no problem.
So, could it be some kind of memory leak?
By the way, I have found since 1.3.1, I'm seeing the “Classic Certification” message for every application the first time I start it after a crash, even the ones that I know are certified. Is anyone else getting that?