unrealED dont like it to get closed

[Skywolf]

when i close unrealED 2.0 it just leaves running in the background. the only way to stop it is by pressing ctrl-alt-del and go to processes and search for unrealED and then force it to close. the worst part about this is that i cant run unreal or unrealED again until i close the old unrealED. also when i forget it to do and don't want to run unreal it take after some minutes 100% of my cpu!!! and even when i shutdown my pc without closing it i get such a stupid end task error and i need to press the end task button, but most times i just go away from my pc and do i leave my pc behind running for about an hour until i comeback and see that it is still running . even reinstalling the 227F patch doesnt work . i have this problem already a long time and it really starts to pissing me of .

is there a way to fix this?

[GreatEmerald]

I remember hearing about something like this somewhere... But it wasn't about the editor anyway. But yea, that's really unusual. Anything in the Editor.log file? What's your OS? Do you experience any other strange bugs with other programs?

[Bleeder91[NL]]

Had the same problem with firefox, it got fixed suddenly, no idea how it got fixed. I has Vista though.

[Skywolf]

end of my log:

Log: Closed viewport
Log: Closed viewport
Log: Closed viewport
Log: Closed viewport
Log: Missing name
Log: Closed viewport
Log: Missing name
Log: Closed viewport
Log: Missing name
Log: Missing name
Log: appRequestExit(0)
Exit: Preparing to exit.
Log: Purging garbage
Log: Unbound to Editor.dll
Log: Unbound to Core.dll
Log: Unbound to Engine.dll
Log: Unbound to Window.dll
Log: 15441.0ms Unloading: Package Editor
Log: 15442.0ms Unloading: Package Core
Log: 15442.0ms Unloading: Package Engine
Exit: Editor shut down
Log: Unbound to ALAudio.dll
Log: 15477.0ms Unloading: Package ALAudio
Exit: OpenAL Audio subsystem shut down.
Exit: Transaction tracking system shut down
Log: Unbound to Fire.dll
Log: 15699.0ms Unloading: Package Fire
Log: Unbound to IpDrv.dll
Log: 15700.0ms Unloading: Package IpDrv
Log: 15701.0ms Unloading: Package UWindow
Log: 15722.0ms Unloading: Package UnrealShare
Log: 15727.0ms Unloading: Package GenFX
Log: 15727.0ms Unloading: Package AmbOutside
Log: 15727.0ms Unloading: Package AmbAncient
Log: 15789.0ms Unloading: Package UnrealI
Log: 15820.0ms Unloading: Package IpServer
Log: 15821.0ms Unloading: Package UBrowser
Log: 15827.0ms Unloading: Package UMenu
Log: 15905.0ms Unloading: Package UWebAdmin
Log: Unbound to Emitter.dll
Log: 15909.0ms Unloading: Package Emitter
Log: 15911.0ms Unloading: Package hovercars
Log: Unbound to WinDrv.dll
Log: DirectDraw End Mode
Log: Flushing cache
Exit: DirectDraw released
Exit: Windows client shut down
Log: Unbound to Render.dll
Log: 16273.0ms Unloading: Package Render
Exit: Lighting subsystem shut down
Exit: Rendering shut down
Log: Unbound to SoftDrv.dll
Log: Unbound to OpenGLDrv.dll
Log: Garbage: objects: 31745->0; refs: 0
Exit: Object subsystem successfully closed.
Exit: Exiting.
Uninitialized: Name subsystem shut down
Uninitialized: Memory Allocation Status
Uninitialized: Curr Memory 0.036M / 1.555M
Uninitialized: Peak Memory 35.769M / 37.594M
Uninitialized: Allocs 107 Current / 167872 Total
Uninitialized: Log file closed, 10/16/10 15:09:40

[GreatEmerald]

Hmm, it says that the unload procedure lasted around 832.0 ms which equals 0.8 seconds. For me it lasts 184 ms, so yours is definitely slower, but not by that much. The "Log: Missing name" errors shouldn't be there, though. Try using a different renderer for the viewport, maybe software, and see what happens.

Also, does this happen every time? Did it happen in the past? And what's your OS?

[Skywolf]

since around 2 months ago and yes this happens always (exept ones in the 2000000000 times, then do i get a rapport send error message). i run unreal 227F on windows XP.

software rendering: work perfect (exept very slow)

openGL rendering: leaves hanging (but runs fast, which was the reason that i use this one).

direct 3D rendering: closes good but it takes a while before it closes and before it starts. also gives many grapich bugs like no screen refreshing after draging a windows over it. (and it goes also very slow)

also do this hanging problem happens a long time after starting using openGL, so it was ones perfect.
changing some settings in advanced options?

btw: that it loads faster could be because your pc is faster (mine have a 1,6 ghz)

[GreatEmerald]

Aha, I see. Well, I'm afraid that in order to solve the problem you will have to reinstall Windows. Behaviour like that is typical when something in the system gets corrupted ([url=http://www.zdnet.com/blog/storage/how-microsoft-puts-your-data-at-risk]blasted NTFS[/url] :\ ). Not much you can do about that, unless you want to spend a few weeks searching for the file that got corrupted.

[Skywolf]

perfect exaple of why windows sucks so it doesnt make sense when i install the openGL driver again?

[GreatEmerald]

Well, if you're lucky, it will work. But you have to be really lucky.

[Pitbull]

While I don't like system restore much you could try restoring to a time before your troubles.

[Skywolf]

can't, system restore only goes back to 1 month

[[]KAOS[]Casey]

"Missing name"

I'd recommend runing "chkdsk /f" in the windows run command/command prompt, and running memtest ( http://www.memtest.org/ )

..it's possible your ram or HDD is messed up causing some invalid names, but don't worry until you see the test results. You should never get an invalid name on something like a viewport.

[Skywolf]

well chkdsk says something like 0k damaged or something. but i couldt read it because it closes very fast. do you need to make a cd or floppy for running memtest? (that is what i get out of what they saying)

[GreatEmerald]

It's supposed to be chkdsk C:\ /f I believe. And run it through the command prompt or you won't see the output.
Yes, you need to install it into a floppy/CD/DVD/USB, boot from it and leave it overnight.

[[]KAOS[]Casey]

/f forces a reboot to actually do anything...

[GreatEmerald]

Oh really?

Code: Select all

CHKDSK [volume[[path]filename]]] [/F] [/V] [/R] [/X] [/I] [/C] [/L[:size]] [/B]


  volume          Specifies the drive letter (followed by a colon),
                  mount point, or volume name.
  filename        FAT/FAT32 only: Specifies the files to check for fragmentation
.
  /F              Fixes errors on the disk.

[[]KAOS[]Casey]

[img]http://www.klankaos.com/lolGE.png[/img]
Derp.

[GreatEmerald]

Interesting, in that case Roland would have got the question as well. Try to do a run chkdsk /f and you'll get the question.
Also, I you can check it without restarting without /F, which is the logical thing to do since if there are no errors, there's no need to restart. ...apparently, my laptop has errors, too O.o

[Skywolf]

yep, i get that message that was the reason that i cant read it because the pc restarts after the scan