Mac OS 9 Discussion > Mac OS 9, Hacks & Upgrades
Mac OS 9 Development Requests (OS Level Items)
nanopico:
--- Quote from: GaryN on November 17, 2015, 03:05:06 PM ---Let's hope it doesn't take 25 years!
--- End quote ---
I'm hoping not 25 but maybe like 24? :)
Front 424:
I don't know, one thing i thought of earlier is maybe better error/application crash recovery, so the entire computer doesn't need to be rebooted so much. It seems to me that a total freeze up happened more in OS 9 than later editions, although even if you could successfully exit a program, it was mostly wise to reboot anyway.
Anyone have any input on this? I am not totally sure about it. It wouldn't be a high priority anyway, I thought I would mention.
Having used OS X and multiple Windows versions, it always seemed that an application crash was much more prone in classic OS to lock up the system requiring a restart of some kind.
Thoughts?
EDIT: I've heard some talk about poor memory management around here. Is this possibly related to that?
Something about RAM not being cleared out properly?
nanopico:
--- Quote from: Front 424 on November 17, 2015, 09:35:48 PM ---I don't know, one thing i thought of earlier is maybe better error/application crash recovery, so the entire computer doesn't need to be rebooted so much. It seems to me that a total freeze up happened more in OS 9 than later editions, although even if you could successfully exit a program, it was mostly wise to reboot anyway.
Anyone have any input on this? I am not totally sure about it. It wouldn't be a high priority anyway, I thought I would mention.
Having used OS X and multiple Windows versions, it always seemed that an application crash was much more prone in classic OS to lock up the system requiring a restart of some kind.
Thoughts?
EDIT: I've heard some talk about poor memory management around here. Is this possibly related to that?
Something about RAM not being cleared out properly?
--- End quote ---
Yes it is very annoying when the lock up like that. There is a way to exit out cleanly with Macsbug, so it's possible to build something in.
It would have to be a patch actually to the process manager. The memory management issues stem around allocating 512 MB to the finder when you have 2 GB installed and the fact that there is no protected memory (which is probably part of the source of apps crashing). When an app has crashed the process manager (which allocates the heap and stack for an app) should release those resources better and also check for open files so they are not left hanging in an opened state. You would probably lose any data that had not been saved but that would be an issue in just about any system. It might be useful to identify apps that tend to crash more than others and also when it happens what else is running. It would be easier to analyze the system to figure out the best way to tackle the problem.
But yes I would agree it could go on the list of potential items.
Front 424:
--- Quote from: nanopico on November 18, 2015, 06:20:47 AM ---
Yes it is very annoying when the lock up like that. There is a way to exit out cleanly with Macsbug, so it's possible to build something in.
--- End quote ---
I remember fiddling around with Macsbug a few times, just to do it. I think I recall what you're speaking of, being able to exit a normally fatal crash without having to reboot, but that's been years ago. I take it you could find out using Macsbug what exactly the chain of events are that lead to such a crash?
--- Quote from: nanopico on November 18, 2015, 06:20:47 AM ---It would have to be a patch actually to the process manager. The memory management issues stem around allocating 512 MB to the finder when you have 2 GB installed and the fact that there is no protected memory (which is probably part of the source of apps crashing). When an app has crashed the process manager (which allocates the heap and stack for an app) should release those resources better and also check for open files so they are not left hanging in an opened state. You would probably lose any data that had not been saved but that would be an issue in just about any system. It might be useful to identify apps that tend to crash more than others and also when it happens what else is running. It would be easier to analyze the system to figure out the best way to tackle the problem.
But yes I would agree it could go on the list of potential items.
--- End quote ---
Thanks for clarifying! I probably should have gathered that from some of the other conversations, since I realize now what you're talking about, the 1.5g limit.
Another question, for you or anyone, about the RAM disk workaround. You posted this over here http://macos9lives.com/smforum/index.php?topic=2860.0
--- Quote ---Then use MacsBug to verify it is there. If that works then it tells us that the memory is addressable and the potential of some sort of ram disk up there is possible (though not necessarily easy in any way).
Just thought I'd share this bit of info.
--- End quote ---
What exactly is the plan with that RAM disk?
Front 424:
Also, I've seen this mentioned in here and it is in nanopico's list in the first post about
--- Quote ---Better Multi-tasking
--- End quote ---
What would that encompass and how would one go about it? What functionality do people want to see out of that? Question for anyone :P
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version