Hard Light Productions Forums
General FreeSpace => FreeSpace & FreeSpace Open Support => Topic started by: General Battuta on February 06, 2014, 08:29:03 am
-
Sometimes my events are so arousing that houseguests tear me away from my computer and ravish me. I've been having a lot of problems with emotionally troubled (http://www.hard-light.net/forums/index.php?topic=86760.msg1734028) FSO components lately, so I thought I'd flag this one too: has anyone else noticed that FRED locks up and crashes on its own if left alone for several hours*? Could this be tied to Windows power saving/sleep behavior? Am I the only one who's ever seen this?
*it's pretty good sex
-
My sexual sessions only last 2 minutes so I couldn't really tell.
-
But you might repro the same bug if you fall asleep affectionately for several hours afterward!
-
Am I the only one who's ever seen this?
Yes, and many other things. Now gdiaf. :p
-
If I've hibernated with FRED left open, it's usually ended up being frozen after powering back up.
-
If I've hibernated with FRED left open, it's usually ended up being frozen after powering back up.
Yes! That's what I'm on about.
e: unless you're trying to tell us you, a bear, have hibernated
-
Yeah, I get this too. I have this feeling that it tends to happen more when the events window is open, but I'm not certain of that.
-
Well, without commenting on the sex part, I do notice that FRED can crash after being left alone for several hours, as I've had happen before even without sleep or hibernation mode as I tend to multitask on two PCs at once. It hasn't been a huge issue for me but every bug or potential issue that can be and is resolved, FRED becomes (even) more trustworthy to work with.
-
Yes, this happens. But I know its unrelated to hibernate/sleep because my computer does neither. The screens do shut off though.... But that shouldn't affect it.
I can confirm the sex link though.
-
Confirming unrelated to hibernation or even screen sleep, as my computer does none of those things.
-
Looks like FRED has some SEXProblems
-
oh my a new joke!
wait.
-
It's to be expected, since FRED(2)'s about 14, 15 years old now.
-
What is this, I don't even
-
It's to be expected, since FRED(2)'s about 14, 15 years old now.
My god, what am I thinking. I should turn FRED off rather than expose it to this kind of behavior. :eek2:
-
Hurry the **** up
-
It's to be SEXPected, since FRED(2)'s about 14, 15 years old now.
Fixxored that for you! :p
Sorry bad joke ;)
-
The support forum is for support requests, not attention whoring. Even when it's with FRED.
EDIT: Upon review, this thread is about an actual problem, even if at first glance (and first report) it appeared to be Battuta sharing TMI.
-
If this is a confirmed bug, can someone enter it into Mantis?
I tried leaving my PC on all night, running FRED via the debugger and it did not crash so it doesn't appear to be universal (or I need more sleep).
-
You need more sex, that's what this is all about. I thought you were paying attention, come on.
-
I tried leaving my PC on all night, running FRED via the debugger and it did not crash so it doesn't appear to be universal (or I need more sleep).
Given the above while knowing next to nothing about FRED's internals, I'd wonder if it's something like a memory bug that only shows up in release builds.
As such, Battuta, maybe try a debug build of FRED and report back? (on FRED, not the sex)
[And please reply on the wxL thread while you're at it. :doubt:]
-
Left my PC on all night, FRED open, event window NOT open, no crash. Unfortunately this is no kind of scientific proof of a connection at all. *sigh*
-
Just managed to crash FRED by leaving it running the background for six hours while I did other stuff.
-
But was the events window open!?
-
No.
Given the timescale, this is going to a real pain to work out.
-
Shiiiiiiit. Okay, what if it has to do with...God, I don't know. I'll try systematically altering my system's sleep settings and see if that has any influence, I guess?
-
is there any way of like... overclocking fred, so you can run it on the timescales needed quickly
-
I dunno, but I got FRED to crash today without the events editor open by leaving it alone for ~8 hours.
-
Could this be like... a really slow memory leak or something? FRED slowly eating up RAM?
I dunno, just wild ideas here.
-
I'm just guessing but could this be caused by an overflow in FS's timer?
According to io/timer.h it "rolls about" every 9 hours. Whenever it does, a "TIMER ROLLED!" appears in fred2_open.log.
-
Hm. Would that be affected by user activity? I've never had FRED crash while actually using it in the past year or so.
-
I don't see how. The timer runs, regardless of what you're doing. I'm not going to flat out state that this isn't a possible cause for stuff; but as far as I can tell, FRED does not use timer functions anywhere (the only point I can see is some internal FPS tracking done by the renderer that may roll over and die once the timer rolls, but that's about it)
-
Who volunteers to only FRED for 10 hours to find out if user activity matters?
-
Who volunteers to only FRED for 10 hours to find out if user activity matters?
Did that several days running (http://i.somethingawful.com/forumsystem/emoticons/emot-science.gif)
-
Really into this thread being pinned!
(http://i.imgur.com/PR9NyC4.gif)
-
...And Battuta invokes Godwin's Law.
EDIT: Please take further discussion to the Mantis ticket created specifically for this bug: http://scp.indiegames.us/mantis/view.php?id=3006