Public Discussions > General Discussion
OS/2 Auto-restarting apps after crash / restart
Doug Bissett:
--- Quote ---I think the feature is a good one, but it needs to be expanded to be useful to a user.
--- End quote ---
I think it will be a lot of overhead, with very little advantage. Programs would need to be (re)written to use the feature, and ported programs (most of them, these days) probably wouldn't work well with it, unless they have some major changes. Leave it on your todo list, but there are many things that need to be higher priority. Suspend/Resume comes to mind, and that may be related.
--- Quote ---It would even be a good one for an app to implement to allow a new type of menu option, instead of just File -> Exit or Close, now File -> Suspend or Suspend. It updates that OS object, then exits, so it can resume right where it was later.
--- End quote ---
That is actually possible today, if the program is written to do it. I suppose that some sort of OS support would make it easier to do, but the program would need to be written to make use of such a feature. I suppose that you could just snapshot the memory spaces, but how would you handle DLLs, and things like video buffers? Sounds like a lot of, time consuming, work, to me.
Dave Yeo:
Just having a working hibernate would have mostly the same effect, resume from hibernation would open apps at the same point.
RickCHodgin:
--- Quote from: Dave Yeo on November 15, 2018, 06:57:50 am ---Just having a working hibernate would have mostly the same effect, resume from hibernation would open apps at the same point.
--- End quote ---
I had that thought too, but hardware suspend / hibernate is a little different. It requires the same hardware, everything about the machine is saved / suspended. With auto-restart, new hardware could be employed, new drivers or driver versions. It would just save you the steps of manually getting back to where you were and it would be contextual, meaning each session ends and resumes as you were when shutting down.
I'll think about it. Still not convinced, but am leaning that way.
RickCHodgin:
--- Quote from: Doug Bissett on November 15, 2018, 04:42:28 am ---That is actually possible today, if the program is written to do it. I suppose that some sort of OS support would make it easier to do, but the program would need to be written to make use of such a feature. I suppose that you could just snapshot the memory spaces, but how would you handle DLLs, and things like video buffers? Sounds like a lot of, time consuming, work, to me.
--- End quote ---
The app would have its normal launch / startup, but then would receive a new message with its last saved auto-startup object. It would parse that object and self-restore its context. The OS would've provided the across-boot storage of context, sending out new messages instructing the app to save / restore its state. The app could simply ignore those messages, but having OS facilities would make it easier to utilize and implement. There would be no limit beyond physical resources on what each apo could store.
The OS could also provide slots per app, with each one being its own context.
Using that mechanism, multiple Suspend / Resume states could be available, and not just at auto-restart, but at any time. Rather than File -> Open, there could be File -> Continue where you continue right from where you left off.
I'll think about it.
Navigation
[0] Message Index
[*] Previous page
Go to full version