of course having all that crap open makes it less stable, dolphin isnt perfect, and with all that crap windows has to give them all some priority, with hyperthreading enabled windows will have 2 processes it can keep running at the same time, i dont know how windows sets the affinity with quad cores for programs that use single core mode, but its safe to say that its process priority is being changed alot, dolphin doesn't get the CPU usage it wants and becomes even more unstable, just because you have a quad core doesnt mean it can do everything perfectly. also if you overclocked your CPU then its even more unstable
(07-08-2012, 01:21 AM)linkinworm Wrote: [ -> ]of course having all that crap open makes it less stable, dolphin isnt perfect, and with all that crap windows has to give them all some priority
No. Priority != CPU time.
(07-08-2012, 01:21 AM)linkinworm Wrote: [ -> ]with hyperthreading enabled windows will have 2 processes it can keep running at the same time
No. Windows runs as many simultaneous processes as you have logical cores on your computer.
(07-08-2012, 01:21 AM)linkinworm Wrote: [ -> ]i dont know how windows sets the affinity with quad cores for programs that use single core mode
Most programs don't set any affinity so they aren't pinned to any specific logical core.
(07-08-2012, 01:21 AM)linkinworm Wrote: [ -> ]but its safe to say that its process priority is being changed alot
No. Process priority is mostly constant, I don't know of any commonly used program that dynamically alters its priority "alot" (whatever this word means).
(07-08-2012, 01:21 AM)linkinworm Wrote: [ -> ]dolphin doesn't get the CPU usage it wants and becomes even more unstable
No. It can definitely get preempted, but actually a lot of time in each Dolphin thread is spent waiting for a synchronization event or a syscall result (the exceptions being mostly the CPU core and the DSP core in LLE mode). In both these cases preempting it will cause no performance decrease as long as Windows is intelligent enough to reschedule it as soon as the event has been triggered. Unless you've got a lot of processes doing CPU intensive tasks in the background Dolphin should be scheduled ASAP if it was preempted. Even then, this should not be a major cause of unstability at all: you can't rely on your OS scheduling you exactly when you need it (unless you're running on a RTOS in highest priority...) and every major OS scheduler behaves differently.
(07-08-2012, 01:21 AM)linkinworm Wrote: [ -> ]just because you have a quad core doesnt mean it can do everything perfectly
Nobody said that AFAICT.
(07-08-2012, 01:21 AM)linkinworm Wrote: [ -> ]also if you overclocked your CPU then its even more unstable
Not relevant here, and most CPUs will "suicide" themselves with an MCE if an overclock is unstable.
(07-07-2012, 11:59 PM)Starscream Wrote: [ -> ]Some of you are only thinking in terms of "normal" PC usage. Yes, if you have "x" amount of RAM and "x" processor, you can run up to "x" amount of programs at the same time perfectly fine, but just like everything else when you compare it to emulation, it's not the same. Other running programs can fight for resources and cause instability while Dolphin is trying to emulate these games. Now, this is not to say having those programs running is definitely what caused his crash, but it certainly didn't help. If you're looking to give yourself the best chance of a game not hanging up on you, you should limit what else is running at the same time that Dolphin is.
Uh, no. im thinking in the realm of tons of stuff open, a virtual machine or 4 running and converting a movie in the background while dolphin is running at playable rates and remaining perfectly stable.
(07-07-2012, 06:33 AM)oerg866 Wrote: [ -> ]Anyway, it probably just crashed because some odd timing issue appeared or something.
May I assume that you haven't thought of clicking "View problem details" and seeing the (NTSTATUS) exception code this time?
If you haven't, try opening the "exceptioninfo.txt" file (if it exists in the same folder as Dolphin.exe), locate the entry for your crash, and note down the code under "Unhandled Exception". The call stack info is unlikely to be of help unless the build is bundled with a symbols (pdb) file, in which case the names of functions may appear.
If you're not lucky, it might have been a typical access violation (0xC0000005), but you never know; it could have been due to an integer division by zero (0xC0000094), heap corruption or whatever, in which case it may be useful to take note of...
This
list of NTSTATUS codes may be outdated such that some exception codes are missing from it (such as for heap corruption = 0xC0000374), but it still can come in handy.
Unfortunately crash minidumps are a bit useless for us because mamario (who builds the "official" builds) does not provide us with the PDBs
Oh god....there are so many retarded posts in this thread that I'm not even going to bother responding to them.
MP isn't perfectly stable on dolphin yet. End of story. It has never been perfectly stable, and this has nothing to do with his background applications. Now hopefully we can leave it at that and I won't have to write another wall of text correcting half of you (although it appears delroth has already done some of that for me).
NaturalViolence: You should consider taking the day off from your main mission in life of telling everyone "you're all wrong and I'm always right about everything and I can post a wall of text to prove it" campaign. We won't hold it against you.
Lol for once I have to agree with Starscream.
But he's right -- the days when you have to "please quit all other applications while running x" are over. It was just bad luck, end of story.
I suggest you pay attention to what the dev above has said. He said it was likely that it crashed because of all those programs, because of how the emulator works and what not. Hee clearly knows what he was talking about.