aMule Forum
English => en_Bugs => Topic started by: thedude0001 on January 17, 2005, 05:03:24 PM
-
This is from the changelog of rc8:
When aMule crashes, it not longer fails saving:
* Preferences (Saved on 'OK')
* Categories (Saved on changes)
* Total upload / download bytes (saved while running).
This worked on rc8 for me. But now I had amule-cvs-20050111 runnning until it crashed on me just now and again he "forgot" the upload / download of this session. Another setting that was lost were some deactivated categories and the width of the categories in the shared files tab.
-
When amule crashes, it means it doesn't work like it should - so whatever happens to it's internal data it's undefined. It will, however, attempt to save as match as it can, but no promises here - memory is already corrupted (otherwize it wouldn't crash on a first place).
Now, we don't want to have another SIGSEG while saving data - so exception handler must be brief as possible: NO closing files/sockets/windows, NO freeing memory, NO calling destructors etc. Becouse all those make access to internal datastructure which is corrupted somewhere.
Conclusion: when it crashes - come here to complain, post backtrace, curse developers. There's good chance that one of them will actually understand a problem and fix it :)
-
About the backtrace: mea culpa, I just read the wiki post about gdb yesterday, now my amule runs inside gdb and I will start posting useful backtraces. :))
I get your point, but rc8 seemed to save the total upload / download every hour or so, so if it crashes only the data since the last save was lost. But on todays crash amule just forgot everything about the 3 days it was running...
-
Moin!
My muli crashed (CVS version). And it didn't save the uploadcounter.
After the crash it was set back to a value thats nearly 24 hours old. I can't imagine why this value, I didn't anything to amule since this time.
Skuro
BTW: the crah was caused by amuleweb again..
-
humpf, mumble mumble, ok, I'll fix it AGAIN.