Runtime error and crash

[Boberro]

What you do when you alt tab out is to release memory. Windows memory managment will try to optimize the memory - it's a common trick to minimize an app to release memory for Windows Terminal Servers..

 

 

What if you play in Window mode but native LCD resolution (maximum)?

[Panzertard]

What if you play in Window mode but native LCD resolution (maximum)?

Minimizing the application is the trigger for Windows.

With fullscreen, you alt-tab, it get's minimized.

With a Window-mode, if it doesn't minimized, then I guess nothing happens. If it minimizes, then the memory manager kicks in.

[Mustang]

What if you play in Window mode but native LCD resolution (maximum)?

 

I wouldn't run in windowed mode, it cripples my FPS.

[Boberro]

Minimizing the application is the trigger for Windows.

With fullscreen, you alt-tab, it get's minimized.

With a Window-mode, if it doesn't minimized, then I guess nothing happens. If it minimizes, then the memory manager kicks in.

 

Good to know I am gonna test it today.

 

 

I wouldn't run in windowed mode, it cripples my FPS.

 

I always thought windowed mode is equally as same as fullscreen in term of frames per second :)

[71st_Mastiff]

I run in windows mode and no issues here, win7 is much more efficient that way i guess.. not really sure.

:pilotfly:

Good to know I am gonna test it today.

 

 

 

 

I always thought windowed mode is equally as same as fullscreen in term of frames per second :)

[Mustang]

Good to know I am gonna test it today.

 

 

 

 

I always thought windowed mode is equally as same as fullscreen in term of frames per second :)

 

Nope, and a few others on here can vouch for this as well.

[KeyCat]

Mustang, sorry if this has been mentioned but did your problems start after the FC2 1.2.1 patch or did you also experienced them before? Also have you got the error on servers other than 104th?

 

I'm experiencing the same/similar issue in both FC2 and BS after the patches when flying on the 104th server, before patching FC2 to 1.2.1 I could fly for hours and hours without issues...

 

/KC

[TheMoose]

I wouldn't run in windowed mode, it cripples my FPS.

 

Sorry to hear that.

 

I run it in windows mode, my windows native is 1920x1200, I run BS at 1680x1024. Runs flawlessly. Looks cool as well. You can "chat" on msn while flying, change your music etc...:D

 

However I did disable desktop composition to improve FPS...

 

Regards,

Edited May 18, 2010 by TheMoose

[Kuky]

crash

# -------------- 20100516-064119 --------------

C:\LockOn Flaming Cliffs 2\bin\x86\stable\edCore.dll

# C0000005 ACCESS_VIOLATION at 00271C90 01:00010C90

#

# EAX = 0018FC44

# EBX = 10A01B68

# ECX = 000000D0

# EDX = 4F146180

# ESI = 4F1475B0

# EDI = 00000000

# CS:EIP = 0023:00271C90

# SS:ESP = 002B:0018FB4C EBP = 0018FEE0

# DS = 002B ES = 002B FS = 0053 GS = 002B

# Flags = 00010202

00271C90 0018FEE0 0001:00010C90 C:\LockOn Flaming Cliffs 2\bin\x86\stable\edCore.dll ?lock@Futex@Sync@@QAEXXZ()+0

00271C90 0018FEE0 0001:00010C90 C:\LockOn Flaming Cliffs 2\bin\x86\stable\edCore.dll ?lock@Futex@Sync@@QAEXXZ()+0

006A637B 0018FF88 0001:002A537B C:\LockOn Flaming Cliffs 2\bin\x86\stable\simulator.exe

75743677 0018FF94 0001:00003677 C:\Windows\syswow64\kernel32.dll BaseThreadInitThunk()+12

778B9D72 0018FFD4 0001:00029D72 C:\Windows\SysWOW64\ntdll.dll RtlInitializeExceptionChain()+63

778B9D45 0018FFEC 0001:00029D45 C:\Windows\SysWOW64\ntdll.dll RtlInitializeExceptionChain()+36

[Kuky]

crash

# -------------- 20100516-080004 --------------

C:\LockOn Flaming Cliffs 2\bin\x86\stable\edCore.dll

# C0000005 ACCESS_VIOLATION at 003D1C90 01:00010C90

#

# EAX = 0018FC44

# EBX = 10A01B68

# ECX = 000000D0

# EDX = 5AEDED28

# ESI = 5AEE0580

# EDI = 00000000

# CS:EIP = 0023:003D1C90

# SS:ESP = 002B:0018FB4C EBP = 0018FEE0

# DS = 002B ES = 002B FS = 0053 GS = 002B

# Flags = 00010202

003D1C90 0018FEE0 0001:00010C90 C:\LockOn Flaming Cliffs 2\bin\x86\stable\edCore.dll ?lock@Futex@Sync@@QAEXXZ()+0

003D1C90 0018FEE0 0001:00010C90 C:\LockOn Flaming Cliffs 2\bin\x86\stable\edCore.dll ?lock@Futex@Sync@@QAEXXZ()+0

006A637B 0018FF88 0001:002A537B C:\LockOn Flaming Cliffs 2\bin\x86\stable\simulator.exe

75743677 0018FF94 0001:00003677 C:\Windows\syswow64\kernel32.dll BaseThreadInitThunk()+12

778B9D72 0018FFD4 0001:00029D72 C:\Windows\SysWOW64\ntdll.dll RtlInitializeExceptionChain()+63

778B9D45 0018FFEC 0001:00029D45 C:\Windows\SysWOW64\ntdll.dll RtlInitializeExceptionChain()+36

[Panzertard]

Thanks kuky, I'm still not seeing any pattern to as why those modules and methods are involved in the crash.

Keep them coming. :)

[Mustang]

Noticed some new ones today:

 

# -------------- 20100518-062924 --------------

C:\Program Files\Eagle Dynamics\LockOn Flaming Cliffs 2\bin\x86\stable\MSVCP71.dll

# C0000005 ACCESS_VIOLATION at 7C3A4F27 01:00003F27

#

# EAX = 00000007

# EBX = 00000000

# ECX = 0000005C

# EDX = 7F404B40

# ESI = 0000005C

# EDI = 00000000

# CS:EIP = 001B:7C3A4F27

# SS:ESP = 0023:0012F45C EBP = 51DA5DA0

# DS = 0023 ES = 0023 FS = 003B GS = 0000

# Flags = 00010202

 

-------------------------------------------------------------------------------------------------------------

 

# -------------- 20100518-093554 --------------

C:\Windows\system32\atiumdag.dll

# C0000005 ACCESS_VIOLATION at 6B96E323 01:0004D323

#

# EAX = 6A9D1134

# EBX = 14D7D2B8

# ECX = 00000000

# EDX = 14D7D300

# ESI = 14D7D300

# EDI = 6AC3FD30

# CS:EIP = 001B:6B96E323

# SS:ESP = 0023:0012D8F8 EBP = 0012D934

# DS = 0023 ES = 0023 FS = 003B GS = 0000

# Flags = 00010202

6B96E323 0012D934 0001:0004D323 C:\Windows\system32\atiumdag.dll gfxInitInteropServices()+F493

6B96E323 0012D934 0001:0004D323 C:\Windows\system32\atiumdag.dll gfxInitInteropServices()+F493

6BA134D1 0012D944 0001:000F24D1 C:\Windows\system32\atiumdag.dll gfxInitInteropServices()+B4641

6B970890 0012D95C 0001:0004F890 C:\Windows\system32\atiumdag.dll gfxInitInteropServices()+11A00

6B970947 0012D984 0001:0004F947 C:\Windows\system32\atiumdag.dll gfxInitInteropServices()+11AB7

6B9706C6 0012D998 0001:0004F6C6 C:\Windows\system32\atiumdag.dll gfxInitInteropServices()+11836

6B9F97B3 0012D9C8 0001:000D87B3 C:\Windows\system32\atiumdag.dll gfxInitInteropServices()+9A923

6B92AC7F 0012D9EC 0001:00009C7F C:\Windows\system32\atiumdag.dll OpenAdapter()+81FF

6B921E34 0012DA20 0001:00000E34 C:\Windows\system32\atiumdag.dll DllMain()+E34

6EF8BFC3 0012DA34 0001:0001AFC3 C:\Windows\system32\d3d9.dll Direct3DCreate9Ex()+D8E8

6EFDD74C 0012F874 0001:0006C74C C:\Windows\system32\d3d9.dll Direct3DCreate9()+B516

6EFC90CB 0012F8C0 0001:000580CB C:\Windows\system32\d3d9.dll DebugSetMute()+35122

6EFC8E93 0012FA3C 0001:00057E93 C:\Windows\system32\d3d9.dll DebugSetMute()+34EEA

03574FF7 0012FA40 0001:00013FF7 C:\Program Files\Eagle Dynamics\LockOn Flaming Cliffs 2\bin\x86\stable\Visualizer.dll ?Render@SceneManager_Implement@@UAEXXZ()+1A7

03EA48B0 0012FA44 0000:00000000

006D9D64 0012FA48 0002:00016D64 C:\Program Files\Eagle Dynamics\LockOn Flaming Cliffs 2\bin\x86\stable\simulator.exe

 

------------------------------------------------------------------------------------------------------------

 

# -------------- 20100518-054553 --------------

C:\Windows\system32\atiumdva.dll

# C0000005 ACCESS_VIOLATION at 6E431535 01:00000535

#

# EAX = 00000000

# EBX = 17395FA0

# ECX = 543C63A0

# EDX = 6E431530

# ESI = 17395FA0

# EDI = 00000000

# CS:EIP = 001B:6E431535

# SS:ESP = 0023:0D0FFA94 EBP = 61598A78

# DS = 0023 ES = 0023 FS = 003B GS = 0000

# Flags = 00010206

6E431535 61598A78 0001:00000535 C:\Windows\system32\atiumdva.dll mmdllInitUMDFuncs()+4E5

6E431535 0D0FFA90 0001:00000535 C:\Windows\system32\atiumdva.dll mmdllInitUMDFuncs()+4E5

 

another thing: something i've noticed, just before the crashes alot of objects start to lose their skins and start to look seethrough, usually an alt-tab corrects this, but it's usually at this point a crash occurs too.

Edited May 18, 2010 by Mustang

[Kuky]

For me, every time crash is to occur I start getting pauses and stutters... last night I fired Kh-25ML, just before impact I got about 30sec long pause... when game continued I had some damage (overflew the target area during the pause time) and few seconds later after game sort of came back I got it to crash and exited to brief menu.

 

I think crash normally happens about 1-1.5h into flying the mission. I need to keep task manager open while I fly to keep an eye on memory usage

[Panzertard]

I'm curious - could it be related to how much details you guys run at - vs - memory available (builtin) to the graphic adapters?

Can you please list this from your Dxdiag(s) on the computers that crash:

          Chip type: GeForce GTX 295
          DAC type: Integrated RAMDAC
        Device Key: Enum\PCI\VEN_10DE&DEV_05E0&SUBSYS_40241682&REV_A1
    Display Memory: 3688 MB
  Dedicated Memory: 877 MB
     Shared Memory: 2811 MB

 

DxDiag report:

• Use Start->Run: DXDIAG and "Save All Information, to a TXT file" for the report.

[Mustang]

Card name: ATI Radeon HD 3850 AGP

Manufacturer: ATI Technologies Inc.

Chip type: ATI display adapter AGP (0x9515)

DAC type: Internal DAC(400MHz)

Device Key: Enum\PCI\VEN_1002&DEV_9515&SUBSYS_0028174B&REV_00

Display Memory: 760 MB

Dedicated Memory: 509 MB

Shared Memory: 251 MB

 

note: i've tried:

low, medium and high scenes

low, medium and high visibility

mirrors are always off

water has been tried on the 1 setting in options.lua

tried all shadows settings

tried all my screen resolutions all the way down to 1024x768 from my default 1920x1080

tried 4x, 2x and no anti-aliasing

tried 8x, 4x and no anisotropic filtering

tried CatalystAI high, low and off

tried various drivers versions all the way upto 10.4 (cleaning out old drivers whilst doing so)

updated DirectX (latest Feb 2010)

checked and updated all MS VC++ runtime redists

 

i could go on and on with the things i've tried, i was up a big part of the night and into the morning trying stuff, nothing seems to totally fix my crashes (apart from the alt-tabbing, but even that gets flakey after an hour or so)

 

One more thing, i had none of these issues with DCS Black Shark, now it's the same version engine/compatibility-wise as FC2.0 i get the exact same problems.

Edited May 18, 2010 by Mustang

[Boberro]

Okey, I minimalized my game to Windows taskbar and nothing amazing happened... Game was as slow as before, RAM usage as same as before :)

[KeyCat]

Here is one from me when I took an A-10 for a spin after the 1.2.1 patch on 104th...

 

# -------------- 20100516-195050 --------------

D:\Games\DCS - Flaming Cliffs\bin\x86\stable\DXRenderer.dll

# C0000005 ACCESS_VIOLATION at 039204CE 01:0002F4CE

#

# EAX = 00000000

# EBX = 00000001

# ECX = 00000000

# EDX = 00000002

# ESI = 0013F5D8

# EDI = 6D961E00

# CS:EIP = 001B:039204CE

# SS:ESP = 0023:0013F4DC EBP = 00000000

# DS = 0023 ES = 0023 FS = 003B GS = 0000

# Flags = 00210202

039204CE 00000000 0001:0002F4CE D:\Games\DCS - Flaming Cliffs\bin\x86\stable\DXRenderer.dll ?DrawStringWs@DXUnicodeFont@Graphics@@MAEMMMMMABUBox2f@DXFont@2@PBDABVColor@2@PAUWsFontVertex@42@PAGAAH5@Z()+29E

 

For my system specifiations see thread in BS part of forum, I'm pretty sure we are dealing with the same issue in both sims here...

 

http://forums.eagle.ru/showthread.php?t=54162

 

Below is four crashlogs and breif specifications from a friend named Salsam (he is not active on this forum so I told him I would post it) all while flying A-10/Su-25T on 104th server.

 

# -------------- 20100516-191504 --------------

C:\Program Files\Eagle Dynamics\LockOn Flaming Cliffs 2\bin\x86\stable\MitkaGraphics.dll

# C0000005 ACCESS_VIOLATION at 0FF6545A 01:0002445A

#

# EAX = 00000000

# EBX = 0FFEB690

# ECX = 00000003

# EDX = 0FFEB6A0

# ESI = 100BCFE8

# EDI = 00000000

# CS:EIP = 001B:0FF6545A

# SS:ESP = 0023:0DC9FBB4 EBP = 01C0FDD0

# DS = 0023 ES = 0023 FS = 003B GS = 0000

# Flags = 00010246

0FF6545A 01C0FDD0 0001:0002445A C:\Program Files\Eagle Dynamics\LockOn Flaming Cliffs 2\bin\x86\stable\MitkaGraphics.dll ?LoadSurface@@YA_NPAUIDirect3DDevice9@@PAUTexture@cdds@@HPAUIDirect3DTexture9@@H@Z()+47A

0FF6545A 01C0FDD0 0001:0002445A C:\Program Files\Eagle Dynamics\LockOn Flaming Cliffs 2\bin\x86\stable\MitkaGraphics.dll ?LoadSurface@@YA_NPAUIDirect3DDevice9@@PAUTexture@cdds@@HPAUIDirect3DTexture9@@H@Z()+47A

C23BD233 0824448B 0000:00000000

 

# -------------- 20100516-204922 --------------

C:\Windows\system32\kernel32.dll

# E06D7363 at 758DFBAE 01:0003EBAE

#

# EAX = 0012F4AC

# EBX = 0012F5C4

# ECX = 00000003

# EDX = 00000000

# ESI = 7C380EDC

# EDI = 0012F53C

# CS:EIP = 001B:758DFBAE

# SS:ESP = 0023:0012F4AC EBP = 0012F4FC

# DS = 0023 ES = 0023 FS = 003B GS = 0000

# Flags = 00000206

 

# -------------- 20100517-195904 --------------

C:\Windows\system32\kernel32.dll

# E06D7363 at 7691FBAE 01:0003EBAE

#

# EAX = 0012F680

# EBX = 7C36BB92

# ECX = 00000003

# EDX = 00000000

# ESI = 7C380EDC

# EDI = 0012F710

# CS:EIP = 001B:7691FBAE

# SS:ESP = 0023:0012F680 EBP = 0012F6D0

# DS = 0023 ES = 0023 FS = 003B GS = 0000

# Flags = 00000212

 

# -------------- 20100518-212222 --------------

C:\Program Files\Eagle Dynamics\LockOn Flaming Cliffs 2\bin\x86\stable\MitkaGraphics.dll

# C0000005 ACCESS_VIOLATION at 1429545A 01:0002445A

#

# EAX = 00000000

# EBX = 1431B690

# ECX = 00000003

# EDX = 1431B6A0

# ESI = 0FA21500

# EDI = 00000000

# CS:EIP = 001B:1429545A

# SS:ESP = 0023:0DDAFBB4 EBP = 01C0FDD0

# DS = 0023 ES = 0023 FS = 003B GS = 0000

# Flags = 00010246

1429545A 01C0FDD0 0001:0002445A C:\Program Files\Eagle Dynamics\LockOn Flaming Cliffs 2\bin\x86\stable\MitkaGraphics.dll ?LoadSurface@@YA_NPAUIDirect3DDevice9@@PAUTexture@cdds@@HPAUIDirect3DTexture9@@H@Z()+47A

1429545A 01C0FDD0 0001:0002445A C:\Program Files\Eagle Dynamics\LockOn Flaming Cliffs 2\bin\x86\stable\MitkaGraphics.dll ?LoadSurface@@YA_NPAUIDirect3DDevice9@@PAUTexture@cdds@@HPAUIDirect3DTexture9@@H@Z()+47A

C23BD233 0824448B 0000:00000000

 

I only managed to get a brief system specification from Salsam over TS yesterday but he told me that the first three crashlogs was with 191.07 WHQL drivers and before yesterdays flight he had upgraded to latest 197.45 WHQL drivers.

 

OS: Vista

GPU: nVidia 9800 GX2 (tested with both 191.07 WHQL and latest 197.45 WHQL)

 

Been looking at the posted logs and they are "all over it" and no real pattern shows up but it's a complicated piece of software (and a pretty complex MP mission on 104th) so I guess anything can happen. Only the devs will be able to figure out the exact cause of this bug/issue and all we can do is guessing and (more importantly) provide them with as much facts and data as possible so they hopefully can reproduce it on their end...

 

/KC

Edited May 19, 2010 by KeyCat

[Mustang]

Another way to deliberatly trigger a runtime crash on my PC, is to cycle through the airfield F11 views over and over, for best effect rotate the camera 360 so all the scenery gets loaded up, eventually (on my PC anyways) textures start to vanish off objects/vehicles etc and finally it crashes to desktop, all in the space of 1 minute.

Edited May 19, 2010 by Mustang

[RvEYoda]

Another way to deliberatly trigger a runtime crash on my PC, is to cycle through the airfield F11 views over and over, for best effect rotate the camera 360 so all the scenery gets loaded up, eventually (on my PC anyways) textures start to vanish off objects/vehicles etc and finally it crashes to desktop, all in the space of 1 minute.

 

Good catch.

 

That does sound like a memory leak. When I get home I will try to reproduce this.

If I get the same results I'll ask the developers and let you know their answer

(if I am permitted to relay it :))

 

In the mean time I ask more people to try exactly this method and report back!

Edited May 19, 2010 by =RvE=Yoda

[Mustang]

Good catch.

 

That does sound like a memory leak. When I get home I will try to reproduce this.

If I get the same results I'll ask the developers and let you know their answer

(if I am permitted to relay it :))

 

In the mean time I ask more people to try exactly this method and report back!

 

I must stress this is on a *clean* install of FC2.0, i have absolutely no mods installed, no files have been tinkered with, it's not installed in Program Files, it's all stock 1.2.1.

 

I really hope this can be reproduced on other people PC's, i know that my rig is clean, not overclocked, and well maintained and pretty decent.

 

edit: another observation, i also know when it's about to crash when i press printscreen and theres no pause, it's as if the videoRAM is so swamped with data it cannot capture a screengrab from the framebuffer and create a picture.

Edited May 19, 2010 by Mustang

[Kuky]

I just got another crash, but I think it's because I didn't allow the game to go back to server list in multiplayer and clicked on exit too early

 

# -------------- 20100519-124835 --------------

C:\LockOn Flaming Cliffs 2\bin\x86\stable\edCore.dll

# C0000005 ACCESS_VIOLATION at 00271C90 01:00010C90

#

# EAX = 0018FC44

# EBX = 10C01B68

# ECX = 000000D0

# EDX = 530C34A0

# ESI = 530C48D0

# EDI = 00000000

# CS:EIP = 0023:00271C90

# SS:ESP = 002B:0018FB4C EBP = 0018FEE0

# DS = 002B ES = 002B FS = 0053 GS = 002B

# Flags = 00010202

00271C90 0018FEE0 0001:00010C90 C:\LockOn Flaming Cliffs 2\bin\x86\stable\edCore.dll ?lock@Futex@Sync@@QAEXXZ()+0

00271C90 0018FEE0 0001:00010C90 C:\LockOn Flaming Cliffs 2\bin\x86\stable\edCore.dll ?lock@Futex@Sync@@QAEXXZ()+0

006A637B 0018FF88 0001:002A537B C:\LockOn Flaming Cliffs 2\bin\x86\stable\simulator.exe

75A33677 0018FF94 0001:00003677 C:\Windows\syswow64\kernel32.dll BaseThreadInitThunk()+12

770E9D72 0018FFD4 0001:00029D72 C:\Windows\SysWOW64\ntdll.dll RtlInitializeExceptionChain()+63

770E9D45 0018FFEC 0001:00029D45 C:\Windows\SysWOW64\ntdll.dll RtlInitializeExceptionChain()+36

[Mustang]

I've just managed to reproduce that same crash just now Kuky:

 

# -------------- 20100519-133106 --------------

C:\Eagle Dynamics\LockOn Flaming Cliffs 2\bin\x86\stable\edCore.dll

# C0000005 ACCESS_VIOLATION at 00961C90 01:00010C90

#

# EAX = 0012FC44

# EBX = 0E776088

# ECX = 000000D0

# EDX = 3DAEAE80

# ESI = 3DAEC5A8

# EDI = 00000000

# CS:EIP = 001B:00961C90

# SS:ESP = 0023:0012FB4C EBP = 0012FEE0

# DS = 0023 ES = 0023 FS = 003B GS = 0000

# Flags = 00010202

00961C90 0012FEE0 0001:00010C90 C:\Eagle Dynamics\LockOn Flaming Cliffs 2\bin\x86\stable\edCore.dll ?lock@Futex@Sync@@QAEXXZ()+0

00961C90 0012FEE0 0001:00010C90 C:\Eagle Dynamics\LockOn Flaming Cliffs 2\bin\x86\stable\edCore.dll ?lock@Futex@Sync@@QAEXXZ()+0

006A637B 0012FF88 0001:002A537B C:\Eagle Dynamics\LockOn Flaming Cliffs 2\bin\x86\stable\simulator.exe

76871194 0012FF94 0001:00050194 C:\Windows\system32\kernel32.dll BaseThreadInitThunk()+12

77C8B3F5 0012FFD4 0001:0005A3F5 C:\Windows\SYSTEM32\ntdll.dll RtlInitializeExceptionChain()+63

77C8B3C8 0012FFEC 0001:0005A3C8 C:\Windows\SYSTEM32\ntdll.dll RtlInitializeExceptionChain()+36

[RvEYoda]

I've just managed to reproduce that same crash just now Kuky:

 

# -------------- 20100519-133106 --------------

C:\Eagle Dynamics\LockOn Flaming Cliffs 2\bin\x86\stable\edCore.dll

# C0000005 ACCESS_VIOLATION at 00961C90 01:00010C90

#

# EAX = 0012FC44

# EBX = 0E776088

# ECX = 000000D0

# EDX = 3DAEAE80

# ESI = 3DAEC5A8

# EDI = 00000000

# CS:EIP = 001B:00961C90

# SS:ESP = 0023:0012FB4C EBP = 0012FEE0

# DS = 0023 ES = 0023 FS = 003B GS = 0000

# Flags = 00010202

00961C90 0012FEE0 0001:00010C90 C:\Eagle Dynamics\LockOn Flaming Cliffs 2\bin\x86\stable\edCore.dll ?lock@Futex@Sync@@QAEXXZ()+0

00961C90 0012FEE0 0001:00010C90 C:\Eagle Dynamics\LockOn Flaming Cliffs 2\bin\x86\stable\edCore.dll ?lock@Futex@Sync@@QAEXXZ()+0

006A637B 0012FF88 0001:002A537B C:\Eagle Dynamics\LockOn Flaming Cliffs 2\bin\x86\stable\simulator.exe

76871194 0012FF94 0001:00050194 C:\Windows\system32\kernel32.dll BaseThreadInitThunk()+12

77C8B3F5 0012FFD4 0001:0005A3F5 C:\Windows\SYSTEM32\ntdll.dll RtlInitializeExceptionChain()+63

77C8B3C8 0012FFEC 0001:0005A3C8 C:\Windows\SYSTEM32\ntdll.dll RtlInitializeExceptionChain()+36

 

Steps to reproduce please (otherwise I cannot report to devs).

See if you can figure out a foolproof way of creating this crash, like you did

with the F-11/spin bug :) (i am still not home so cannot confirm yet)

 

I'll need details like "start attached mission, press escape,

press Q and quickly press..."

 

I expect to send 2 major crash reports when I get home, in about 3 hrs

Edited May 19, 2010 by =RvE=Yoda

[Mustang]

Steps to reproduce please (otherwise I cannot report to devs).

See if you can figure out a foolproof way of creating this crash, like you did

with the F-11/spin bug :) (i am still not home so cannot confirm yet)

 

I'll need details like "start attached mission, press escape,

press Q and quickly press..."

 

I expect to send 2 major crash reports when I get home, in about 3 hrs

 

I can reproduce this over and over on my rig by doing the following:

 

Launch multiplayer, click client, then as soon as the server list starts to populate quickly click the back button... you *should* get a "lockon has stopped working...." and an edCore.dll error and a following Mitkagraphics.dll error.

 

I hope this helps!

 

P.S: the F11 crash bug is not caused by the view spinning out of control or anything, i refered to the spinning because you need to rotate the camera 360 to load all the graphics up in the scene.

Edited May 19, 2010 by Mustang

[RvEYoda]

I can reproduce this over and over on my rig by doing the following:

 

Launch multiplayer, click client, then as soon as the server list starts to populate quickly click the back button... you *should* get a "lockon has stopped working...." and an edCore.dll error and a following Mitkagraphics.dll error.

 

I hope this helps!

 

P.S: the F11 crash bug is not caused by the view spinning out of control or anything, i refered to the spinning because you need to rotate the camera 360 to load all the graphics up in the scene.

 

Yes, it was poor naming perhaps :P

 

Update:

Back button bug confirmed

 

Unable to reproduce the F11 bug. I was running 1024 windowed mode. Any recommendations on what settings I should use?

I have been pressing F11 for 2 minutes and using fast rotate (in a server with 30 players)

 

After 5 minutes memory usage (normal RAM) is still at 410 MB

Edited May 19, 2010 by =RvE=Yoda