Official Fulqrum Publishing forum - Help the devs

Official Fulqrum Publishing forum (http://forum.fulqrumpublishing.com/index.php)

- IL-2 Sturmovik: Cliffs of Dover (http://forum.fulqrumpublishing.com/forumdisplay.php?f=189)

- - Help the devs - upload your crash dump files! (http://forum.fulqrumpublishing.com/showthread.php?t=26007)

Quote:

Originally Posted by mazex (Post 353022)

I have also experienced the online crash after 20-30 minutes twice (have only had time to fly online twice on the new patch so 100% there). I have mailed the dmp-files with a detailed description to Ilya - but I did notice one interesting thing before killing "launcher.exe" the last time... The 32-bit process took 3Gb of memory. That should be "against the wall" even if it's compiled to be large address aware. Feels like a memory leak to me as an old C++ programmer...

Anyone else that has noticed this?

By the way, I had 20 dmp-files from the same minute it crashed the last time.

Got an out of memory again today when changing skins... See my mail below to Ilya (including my mail from yesterday) - reposting it here if anyone else has gotten the same problem (and so you can have an eye open for it!)

Quote:

Hi again Ilya!

I have now repeated the first bug I reported yesterday and can confirm that there is a memory leak regarding skin loading. Thats good news at least!

I was flying on Repka again. Flew a mission in the Spitfire II, shot down a 109, managed to damage my engine trying to catch another with to little radiator and went back and landed. I then tried spawning but got the message from the server "To many planes of this type". Pressed escape which unfortunately does not give you the option to "exit this flight" - so you really leave that Spit II running? Anyway - as there is not "exit this flight" available I guess the server has to "clean out" those planes when a user from the "escape menu" selects create new flight? So I did create a new Spit 1a plane at the same airfield and realised it had that funky "JUNGLE" skin I talk about in my mail below from yesterday. So i did press escape again and set out to "create" a new Spitfire 1a but without the "JUNGLE" skin. So when I klicked the "Plane" button to customize my plane I kept an eye at my Logitech LCD Display where I can see the current CPU and memory usage. I had kept a watchful eye on that as I had the memory leak problems described in "crash number 2" below where the game froze with 3Gb memory used.

So - just after joining the Repka server I checked that launcher.exe used around 1.2Gb of memory, after landing the Spitfire II after the first mission it used 1.7Gb but it decreased a bit back to 1.6... Fine I thought. Then when I changed from the "JUNGLE" skin to the default "1939B" skin I looked at the memory usage (which was 50% then of my total 8Gb). Imediately after selecting the 1939B skin it started going up to 55%. Changed to 1939A and it continued rising. Then I realized it was rising at 1% per second anyway and when it came to something like 75% (very soon) I got a "launcher.exe" has stopped responding error from the OS.

So - it seems you must look at the skin loading routine. There must be some memory that is not released when selecting a new skin and there is something that crasches after a while and just eats all memory in some situations. When I try it in single player after NOT having flown a mission I can not reproduce it though so it seems like you have to have flown before for it to happen!

Good luck /mazex

2011/10/23 xxxx <xxx.xxx@gmail.com>:
> Hi Ilya!
>
> Unfortunately I had two CTD:s while playing online on the Repka 1.11
> Steppes server tonight on the latest official patch (Steam cache
> verifyed etc - computer extremely stable with all latest drivers). The
> first time it happened after crashing and then when selecting a new
> plane (Spitfire 1a) I tried to change the skin. I found a skin called
> "JUNGLE" in the list and selected it (maybe a user skin downloaded
> online?). Immediately after selecting it I got a "Launcher.exe has
> stopped responding", and when I had killed the process I saw a dump
> file that was 0 kb... I enclose the .dds file I found in my cache
> folder that contains the skin. After restarting I could select it
> though without crash...
>
> OK, so I did a second attempt after rebooting my computer to be sure
> no stray processes where running. After taking off I played two
> missions - one for 10 minutes - shot down one me109 in my Spitfire 1a
> and then selected the Spifire II (in limited supply at that server).
> After taking off I battled with one 109 and shot him up badly by he
> managed to crach on his own field (the one at ~E4). After that I saw
> two 109:s low over the edge of the field so I turned against them (I
> was right over their field by then). Then the game "froze" with the
> sound of my Merlin at full speed looping all over, CPU at 0%. When I
> CTRL+ALT+DEL to start the task manager to kill "launcher.exe" I saw
> that the launcher.exe (32-bit) process was taking 3070Mb of memory...
> Tried taking a screenshot of the task manager before killing the
> process but it seems the focus may have been on the dead process in
> some way so the screen shot was just blank. But I am sure it was 3Gb.
>
> So... That must be "against the wall", even if the game is compiled to
> be large adress aware (/LARGEADDRESSAWARE compiler directive has a
> limit of 3Gb?). Feels like a memory leak to me as an old C++
> programmer?
>
> I then looked in the cppcrash folder and found 20! .dmp-files from the
> time of the crash (I had cleaned it after the previous crash)... I
> include an image showing the folder and one of the files.
>
> Good luck with the game - it's really getting good now!
>
> Regards /xxxx (mazex at the 1C forum and online)
>
> My system:
>
> CPU: Intel i7 2600k @ 4.5 Ghz
> GPU: Asus GTX580 Direct CU II with the latest beta drivers 285.38
> Mother Board: Asus P8P67 Pro
> Memory: G-Skill 8GB DDR3 1600 Mhz
> Disks: Intel X25-M G2 SSD (OS) + Raptor 150 (Steam/Games) + 1TB WD (Extra)
> PSU: Corsair CMPSU-HX 750W
> Sound card: Creative X-Fi Fatality Pro (PCI) with the latest 2.18.15 driver
> OS: Windows 7 x64
> TrackIR 4
> Logitech G940 joystick
>

Here are mine from yesterday:
Edit: happened during online sessions all attached file because of Launcher crashes.

Sys Specs:
OS:Windows 7 Ultimate 64bit
CPU: AMD Phenom II X6 Black Edition 1090T (3,20GHz)
MoBo: Asus M4A87TD/USB3
RAM: 8GB Corsair DDR3
GPU: Gigabyte GeForce 560ti (1024MB)with 285.38 Driver
HDD: 1000GB Samsung SpinPoint F3
Saitex X52 Joystick and Throttle, X52 Rudder Pedals, TrackIR 4

This thread is great, but I really think that the devs need a bit of background information (what happened, is it possible to reproduce the bug etc) on each crash to be able to use the dumps for any real bug tracking?

Quote:

Originally Posted by robtek (Post 351064)

Last crash occured during online play and created 8 dump files with 0kb:

18_10_11__20_31_30_18344_872.dmp
18_10_11__20_31_30_18344_451.dmp
18_10_11__20_31_30_18344_498.dmp
18_10_11__20_31_30_18344_545.dmp
18_10_11__20_31_30_18344_591.dmp
18_10_11__20_31_30_18344_732.dmp
18_10_11__20_31_30_18344_763.dmp
18_10_11__20_31_30_18344_810.dmp

The launcher.exe used more than 3 GB Ram at this time and a squadmate had also a launcher.exe crash at the same time.

I'd say memory leak.

I sure agree on the memory leak theory - but maybe it's a server script that has "gone wild" spawning to much stuff or invalid objects? It seems weird that your squad mate got the same error at the same time if it's some leak in an obscure corner of the code that you should be alone to experience exactly at that time?

Anyway, I have gotten three similar incidents while flying online myself (launcher.exe going to 3Gb and then crash as it's a 32-bit process). I realized that I got it twice after changing skins though - see my post a bit further back in this thread.

Flew for 3 hours solid online yesterday without a single crash. In fact nobody in our group was crashing on the ATAG server. If something got changed...it worked.
SKUD

I was able to fly for hours without any freezes on a server with arcade setting. Back on server with full real settings I've got a freeze after 20 minutes or so.

Finally captured one.

Specs:
CPU i5-760 @ 3.4
COOLER MASTER Hyper 212 Plus
GPU Palit GTX 560ti 2GB w 280.26 drivers
Mobo ASUS P7P55 D-E Pro
Memory G-Skill 8GB DDR3 1600 Mhz
PSU Corsair CMPSU-750TX 750w
HDD WD Caviar 500GB
Monitor 24" HP LA2405wg @ 1200x1920
Win 7 64 bit
TrackIR 4

FWIW there was only 1 .dmp file in my cppcrash folder, from may 7. I have had many crashes since then. In fact the game is basically unusable for me; I can fly over water, but if I go over land, I will get a BSOD within 5 minutes. And yes I have tried messing with all sorts of settings, drivers, etc. I even replaced my PSU in hopes of solving the problem.

All temps in my system are well within range when running CloD (<60). But GPU usage runs near 100% now matter how far I turn settings down. That must have something to do with it.

I tried once again tonight, after tweaking Nvidia settings again, and once again got a BSOD. This time though after I got the rig started up again, it pointed me to a .dmp file located in C:\Windows\Minidump folder. That's what I'm attaching.

Hope it helps.

Quote:

Originally Posted by Speckled_Jim (Post 354046)

Have you tried latest drivers?
http://www.nvidia.co.uk/Download/Find.aspx?lang=en-uk

My dump files are in the 1C Soft Club/.../cppcrash folder but they are usually empty :(

Here are couple from a day or so ago.

I was in FMB and trying to set a flight of He 111 to with t/o and landing waypoints and in between. Set a furhter He 111 as player then went into Single missions where I saved the mission and twice I got CTD and 'Launcher.exe' not responding.