ID:133217
Jan 22 2009, 4:36 am
|
|
So whenever your compiling new files or files that were recently updated or altered, and your computer freezes up because you have many programs open and you are forced to hard boot. Your files will be come corrupted. Icons will be unreadable and code files will contain a blank page. Wouldn't it be great if a file does become corrupted, it will revert to its last save instead of having to start ALL OVER again.
|
Unfortunately what you're describing is happening because the file system is being forced to abandon its work halfway through the job. If the files are getting corrupted, there's nothing BYOND can do to restore them because it has nothing to work with. It would probably be possible to add in some kind of optional backup system, but I think you'd be better off making backups yourself if this is a frequent problem.
If your system is crashing so hard that you're forced to do a hard reboot, it sounds like you'd do well to address the issues underlying that instead. I've been in that situation before where something crashing does kill the whole system, so I know where you're coming from. However that kind of thing should happen very rarely. If you're concerned it could happen during compilation, the best move you can make is to close some of the excess programs before compiling. It also can't hurt to look for things you can stop from starting up with the system, like programs that load in the background but are never needed. Most cases of widespread system instability come from things like that, or from malfunctioning drivers. Lummox JR |
In response to Lummox JR
|
|
I'd just like to point out one thing. Dream Maker is fairly unstable when compiling large projects. Large source codes, lots of icons and so on, they tend to make Dream Maker crash fairly often when compiling (though nothing is lost when it does crash). Only once have I had dream maker crash and crash my computer at the same time (and one or two files became useless in the process).
It is also not a computer related issue. It use to happen on my old computer (running XP), and it still happens on my new computer (running Vista). |
In response to Lummox JR
|
|
Would it be possible to add that optional feature. When you compile, auto back up source files before compiling?
|
In response to Max Omega
|
|
Seconded. I'm all for source control software but this is just a good idea all around anyways.
George Gough |
In response to The Magic Man
|
|
The Magic Man wrote:
I'd just like to point out one thing. Dream Maker is fairly unstable when compiling large projects. Large source codes, lots of icons and so on, they tend to make Dream Maker crash fairly often when compiling (though nothing is lost when it does crash). Only once have I had dream maker crash and crash my computer at the same time (and one or two files became useless in the process). I've had Dream Maker spontaneously and catastrophically crash on compile on everything from gigantic projects to environments I created just to have a testing verb. I think there's some fun gremlin ambling around in the compiler, but I haven't been able to cause a crash intentionally yet. At any rate, I've never lost any work that way, and it seems like the crash occurs right after saving all the files but right before the compile process begins. |
In response to Mobius Evalon
|
|
Mobius Evalon wrote:
The Magic Man wrote:I've got a codebase that seems to be able to cause a crash 100% of the time (tested on two separate computers). http://buttware.com/ss13-recreatable-crash.zip |
If you are having this problem on a regular basis just make manual backups of your files before compiling.