Looking for Leaks

[P_Johann]

1 GPU: Palit GTX 1060 Jetstream
2. OS: Windows 10 64 bit Anniversary Edition
3. Driver: 376.19
4. Frame time before: ~12.2ms
5. Frame time after: ~45ms and raising
6. Programs running: Steam, Chrome, Discord, Skype, MSI Afterburner

 

Important notes:

1: My fps capped at 82 via "RivaTuner" built in MSI Afterburner package.

2: Frametime bug occurs only in windowed/fullscreen_window mode. I can run fullscreen client for hours without any dps drops.

3: Closing other software or changing game settings doesn't seem to be doing anything.

[Cherac]

1 hour ago, Cherac said:

Couldn't reproduce. Maybe a bit overkill on the info hence the spoiler tags.

tl;dr: 980, i7, W10 64, 375.70, before and after ~6ms

  Reveal hidden contents

Apollodorus 60 minutes

Frametime:
 Before: 5.9-6.0 ms
 In mission: ~7.0-11.0 ms
 After: 6.1-6.2 ms
 
Loadout
 Mesa
 Dera Vandal (Corrosive/Heat)
 AkMagnus (Toxin)
 Venka Prime (Corrosive - or Viral, can't remember)
 Carrier Prime (no weapon)

Mission Details
 Used:
    All weapons
    All warframe powers
    Ground slam/channeling (for particles)
    Focus power
    Energy restores
 Looted:
    Vacuumable pickups
    Chests/lockers/resource nodes
    Convergence
 Stats:
    1774 Total kills (169 head, 184 melee)
    37 Upgrades
    132 Abilities
    1872 Pickups
    2 Alt+Tab while paused (esc menu)

Related PC Specs
 24" IPS 1920x1200 @ 60
 GTX 980 4GB @ 1190? (stock speed)
 i7 4770 @ 3.4
 8GB DDR3 @ 1866
 375.70 drivers
 3.1.2.31 GeForce Experience
 Windows 10 64bit on boot SSD
 Warframe on storage SSD
 Steam on storage HDD

Non-default Global 3D Settings
 Anisotropic Filtering 16x
 DSR 2.00x
 Smoothing 20%
 MFAA enabled

Ingame Graphical Settings
 Display Mode - Fullscreen
 Resolution - 2715x1697 (DSR 2.00x)
 Refresh Rate - 59.95 Hz
 Aspect Ratio - Auto
 Vsync - Off (normally off)
 Max Framerate - Unlimited (normally 120)
 PhysX - Enabled
 Tessellation - Enabled
 Local Reflec. - Enabled
 Blur Reflec. - Enabled
 Volum. Light. - Enabled
 HDR - Enabled
 Adapt. Expo. - Enabled
 Glare - Enabled
 Ambi. Occl. - Enabled
 High Shader Q. - Enabled
 Geometry - High
 Particles - High
 Shadows - High
 Textures - High
 Anisotropic - Off
 Trilinear - On
 AA - SMAA(Medium)
 DoF - Disabled
 Motion Blur - Disabled
 Bloom - Enabled
 Intensity - ~1/5
 Color Correc. - Disabled
 Dyn. Lighting - Enabled
 Char. Shadows - Enabled
 Weapon Trails - Disabled
 Elemental FX - Disabled

Launcher Settings
 All enabled
 Verified/Optimized after 19.1.0 or something

Running programs
 Steam, overlay + FPS counter
 Discord, no overlay
 Shadowplay, overlay, not recording
 Firefox, 5 tabs, one being a music stream (HTML5)
 Chrome, 2 tabs
 Logitech Gaming Software, mouse, Warframe key bindings
 Corsair keyboard software, Shadowplay key bindings
 DisplayFusion, 300+ wallpapers on random shuffle
 
Other
 I don't know if this is related or not, but everytime I load into the orbiter my framerate drops to about 3 FPS for a few seconds.
 It happens even after a fresh launch/login. I also get a few small hitches when moving from the front of the orbiter to the
 arsenal station for the first time after loading in. I do have quite a few decorations in the transference room though.
 
 I also tried to record something in Warframe this week and the Shadowplay overlay was bugging out a bit. It was very unresponsive at times.
 This one might be related.

 

Looking at the replicated results posted in this thread, the 376.19 drivers seem to be a common factor as well. Is that in line with every reported replications so far?

I downloaded the 376.19 drivers and intentionally did a quick install instead of a clean one to see if it could cause some issues. Did two 20 minute runs on Apollodorus, one with the above settings and one with borderless fullscreen; Still nothing.

On the orbiter load issues I have, I'm quite positive its caused by the decorations. Gonna do a separate bug report tomorrow if there isn't one on the forums yet.

[Tode_Gleich]

I repeated the test at your request and these were my results. I started this test after finishing the sortie, so the game had been running for a bit beforehand.

1. GPU Model (MSI 970 Golden Edition)
2. Operating System (Windows 10 64-Bit)
3. Nvidia Driver Version (376.19)
4. Frame Time Before (6.2ms)
5. Frame Time After (10.2ms)
6. Programs Running (Steam, GeForce Experience, Discord, Avast, Foobar2000, 7 Chrome Tabs, MSI Afterburner)

[Handles]

21 minutes ago, Cherac said:

Looking at the replicated results posted in this thread, the 376.19 drivers seem to be a common factor as well. Is that in line with every reported replications so far?

 

I'm still running 376.09 (Because lazy) and am getting the issue

[[DE]Glen]

7 minutes ago, Umbro_Excalibruh said:

I repeated the test at your request and these were my results. I started this test after finishing the sortie, so the game had been running for a bit beforehand.

1. GPU Model (MSI 970 Golden Edition)
2. Operating System (Windows 10 64-Bit)
3. Nvidia Driver Version (376.19)
4. Frame Time Before (6.2ms)
5. Frame Time After (10.2ms)
6. Programs Running (Steam, GeForce Experience, Discord, Avast, Foobar2000, 7 Chrome Tabs, MSI Afterburner)

Thank you -- that's not as bad as we've seen with the 10x0 cards which I can't quite explain. 

[[DE]Glen]

If this really is only in Windows 10 I really wonder about the Game DVR feature. Neo_182 said he already turned it off but I'm wondering if the other people here able to reproduce the problem have made sure it's off too.

[Tode_Gleich]

I just disabled the Game DVR feature and will report back in 40 minutes.

[Cray]

<I'mDoingMyPart.gif>

 

Did a 60 minute run. Spent first half shootin', second half slicing-and-dicing with Naramon. No luck.

 

Win7, GeForce GTX 960, with 372.90 for driver

Major background programs: Firefox, Discord, Steam (w/Overlay), Teamspeak, Antivirus, Software Firewall

 

 

 

As a side note, I stumbled across a hole in the map, and accidentally fell out of the map. Used /unstuck to speed things up. For a few minutes after that, I had terrible spawn flow. I could not keep up, despite being Nekros. After moving a few rooms over, spawn flow finally picked back up and I was doing fine again. I took an F6 shot of the hole after doing /unstuck. I also saved ee.log, in case this is something someone wants to look into.

Edited December 10, 2016 by DeltaPhantom

[NovaPrime]

I can confirm this bug happened for me as well.

Frame time before running Apollodorus for 30 minutes: 3.1ms

Frame time after running Apollodorus for 30 minutes: 11-12ms

1. GPU Model: MSI Gaming X 1070
2. Operating System: Windows 10 64 bit
3. Nvidia Driver Version: 376.19
4. Frame Time Before: ~3ms
5. Frame Time After: 11-12ms
6. Programs Running: Steam, GeForce Experience, Google Chrome, MSI Afterburner

Full screen mode, PhysX on, Vsync off, 1080p, all other settings maxed

[Cherac]

Enabled game DVR, 20 min Apollodorus, the previous settings (fullscreen) - still unable to reproduce.

[Blur410]

Yeah after running endless missions and alt-tabbing I have noticed a video crash occur. However, the audio at least for me still can be heard. Is this the persistant crash being referred to?

[Tode_Gleich]

I did another 40 minute run with the dvr disabled
 

1. GPU Model (MSI 970 Golden Edition)
2. Operating System (Windows 10 64-Bit)
3. Nvidia Driver Version (376.19)
4. Frame Time Before (3.1ms)
5. Frame Time After (6.4ms)
6. Programs Running (Steam, GeForce Experience, Discord, Avast, Foobar2000, 7 Chrome Tabs, MSI Afterburner)

[Handles]

Update for me: Updated to 379.19 nvidia drivers. No change. Windows update, no change. Turned off Physx, works amazing. Down to 2 ms in ship, from 12. And like, 3 in mission defense missions.

[OfficerBeepsky]

Before the mission

At the end of the mission

Liset

 

 

1. GPU Model ( Asus GeForce GTX 1080 8GB ROG STRIX OC Edition )
2. Operating System (Windows 10 Pro 64-Bit)
3. Nvidia Driver Version (376.19)
4. Frame Time Before (~7ms)
5. Frame Time After (~7ms)
6. Programs Running (Steam, GeForce Experience)
7. Output Resolution (1440p @ 144hz)

 

Pushed it as hard as I possibly could, maxed out literally everything on the settings, and didn't run into the problem. Hovered around 7ms for the frame time the entire time.

Edited December 10, 2016 by OfficerBeepsky

[OfficerBeepsky]

1 hour ago, [DE]Glen said:

If this really is only in Windows 10 I really wonder about the Game DVR feature. Neo_182 said he already turned it off but I'm wondering if the other people here able to reproduce the problem have made sure it's off too.

I can confirm that the Xbox App Game DVR causes a lot of memory leak issues. When I tried to run GTA5 with it enabled on my laptop that has a 970m in it, it would only run for like, fifteen minutes before crashing out.

Edited December 10, 2016 by OfficerBeepsky

[[DE]Glen]

I wonder if we can attack this another way: if you are one of the lucky ones that can reproduce it with PhysX effects enabled:

1. run Windowed or Borderless so you can alt-tab without smashing the driver
2. kick up Task Manager and in the Processes tab show the Commit Size and Handles columns
3. mark down the two values before, go do a mission, mark down what they are after

If it's a raw handle leak then a handle dump might provide some evidence.

The other reproduction I've heard of is to idle in a relay over night; if this works and you wake up to insane frame-times I might be able to get a clue from a procdump snapshot if you're pro with the command prompt. A dump is probably only going to catch it in the act if whatever's bloating is the overwhelming majority of the frame time -- eg: it's normally 2ms staring at the floor but after a long nap in the relay and back to the liset it's 60ms then you've got a good chance of it winning.

[LeoLeonardoIII]

I ran 40 minutes in using my Nikana Prime.

1 GPU Model: NVIDIA GeForce GTX 860M
2 Operating System: Win7
3 Nvidia Driver Version: 21.21.13.7609
4 Frame Time Before: 9.3ms
5 Frame Time After: 9.5ms
6 Programs Running: As the point is to find out if a certain program is causing the issue, I usually run thusly:

Unfortunately I don't think I was affected, but since the point is to help dial in the sights on this problem, I hope this is useful~

[xFrostKnightx]

30 minutes, on Appolodorus

1. [GUP]: Nivida GeForce GTX 970  
2. [OS]: Windows 10 64-bit  
3. [Driver]: 376.19   369.09
4. [Frame time before]: 3.1ms  
5. [Frame time After]: 3.1ms
6. [Programs running]: Steam, Discord

I ran the game in borderless, had all background apps and non-default processes off.  
Edit: Goofed up driver ver. Will update and re-run it I suppose. 

- Re-Run (Updated Driver to 376.19)  Same results. 

Edited December 10, 2016 by xFrostKnightx

[Cray]

1 hour ago, [DE]Glen said:

I wonder if we can attack this another way: if you are one of the lucky ones that can reproduce it with PhysX effects enabled:

1. run Windowed or Borderless so you can alt-tab without smashing the driver
2. kick up Task Manager and in the Processes tab show the Commit Size and Handles columns
3. mark down the two values before, go do a mission, mark down what they are after

If it's a raw handle leak then a handle dump might provide some evidence.

The other reproduction I've heard of is to idle in a relay over night; if this works and you wake up to insane frame-times I might be able to get a clue from a procdump snapshot if you're pro with the command prompt. A dump is probably only going to catch it in the act if whatever's bloating is the overwhelming majority of the frame time -- eg: it's normally 2ms staring at the floor but after a long nap in the relay and back to the liset it's 60ms then you've got a good chance of it winning.

 

Command line 'refuses-to-admit-to-being-a-noob' here, what are the commands I'd need for proc/handle dump?

Edited December 10, 2016 by DeltaPhantom

[Helch0rn]

GPU: GTX 780M

OS: Windows 10 Pro 64 Bit

Driver: 369.09

Before: ~7 ms

After: ~13 ms

Programs running: Steam, Teamspeak, Skype

[NzR.Aaeru]

40 minutes, on Appolodorus.

GPU Model (Palit GTX 1070 Super JetStream)
Operating System (Windows 7 64-Bit)
Nvidia Driver Version (376.09)
Frame Time Before (~4.1ms)
Frame Time After (~4.2ms)
Programs Running (Steam, Chrome (4 tabs), Dropbox, ThunderMaster, AquaSnap 1.18.3, Razer Synapse, CCleaner Free, KeePass, ESET NOD32 Antivirus 9.0.408.0)

Note: I did not install Geforce Experience, and have only installed drivers for the GPU and for PhysX.

[RHEDEN]

Hi, I'm here because of an issue with frame drops that have been occurring since TWW, they drops occur when I log onto Warframe,, when I enter my liset from a mission and when I am in my Arsenal, and sometimes else where.  Here is my test...

1. Cold Boot....[23:50]
2. Nvidia Control Panel Settings (Let the 3D application decide) and G-Sync Off
3. Driver Version: 376.19
4. Warframe download verified and cache optimized...restarted Warframe
5. Warframe options> Show fps [on] | PhysX Enabled [on] | V-Sync [off] | Max Settings | Fullscreen...restart Warframe
6. (Before) FPS: Low 148 Avg. 176 High 186 | Frame Time Avg. 5.6 (up to 6.8 when idle animation plays) | RAM 558 mb
7. 30 Min. Apollodorus with Nekros Prime | Secura Penta(PhysX enabled) | Pox(PhysX enabled) | Jat Kittag(PhysX enabled)
8. (After) Exactly the same as before...

*No other programs where running in the background*  *Warframe is launched by Steam and therefore Steam overlay can be activated* *Native Resolution is [4k] 3840x2160*

*Usually I would run TS3 in the background with Spotify or Browser for music*

HARDWARE

|GPU: NVIDIA TITAN X (Pascal)

|RAM: Corsair Vengeance 32 GB (4x8GB)  

|CPU: Intel i7-6700k @ 4.00 GHz

|HDD:  128 GB SanDisk

|SDD:  1 TB Samsung

|MBO:  ASUS Hero III

|RESOLUTION: 3840x2160 Native [4k] @ 60 Hz

|OS:  Windows 10 64-bit

In conclusion I did not see or obtain the bug, yet while testing I still had gotten the fps drop during logging on and returning from mission, also I got the new [Healing Return] mod from that run XD.

 

 

Edited December 10, 2016 by PrimeV

[Shaonia]

Welp, my test came up with nothing.

Initial frame time: 7.3ms
Frame time after a 10 min run of Apollodorus: 7.3ms _{did the potato alert as a warmup}
Frame time after a 40 min run of Apollodorus: 7.3ms

Specs:
GPU: Asus Strix GTX 970 DirectCU II OC, 4Gb GDDR5
CPU: Intel Core i5-6600K @ 3,5GHz
Display 1: BenQ XL2411Z, 1920x1080 @ 144Hz
Display 2: LG L204WT, 1680x1050 @ 60Hz
Nvidia Driver version: 376.19
OS: Windows 10 Pro 64-bit

I disabled Xbox DVR.

Open programs:
Warframe
Google Chrome (on the 2nd screen, with a video paused on YouTube)
Steam
GeForce Experience
Telegram
Windows Defender
Realtek HD Audio Manager
Notepad

[Dragstein]

Hey there. I used to have same kind of problems myself, as described on the topic. It seemed that only after a short period of time when entering missions, the game begin to struggle to run and my FPS dropped dramatically which usually lead to game crashing. Especially Earth maps seemed to struggle to run after playing for a while and eventually the whole game crashed. I did verify game files with steam and with warframe launcher and also optimized it with the launcher, but they had no effect on the performance whatsoever.

Okay, background on the setup when the problems occured:

1. GPU Model (GTX 1080, Asus STRIX OC'd, seemed to have no effect whether is was OC'd or factory clock settings)
2. Operating System (Windows 10 Pro 64-Bit)
3. Nvidia Driver Version (375.95) <- Hotfix driver which should have fixed Pascal-cards VRAM clock issues. 
4. Frame Time Before (~5.5ms)
5. Frame Time After (N/A game crashed)
6. Programs Running (Steam, GeForce Experience, Discord, Telegram, Asus GPU Tweak II)

Game was running 2560x1440, 165Hz, Borderless full-screen, G-Sync ON and OFF (didn't seem to matter), game max fps set to 144 (also no effect whether it was 144 or 200), all settings maxed out except Anti-Aliasing was set to SMAA (Medium).

I noticed that before the game started to stutter my GPU core clock seemed to drop from around 1950MHz to 1600MHz.

GPU: Asus Strix GTX 1080, 8GB GDDR5X
CPU: Intel Core i7-4770KK @ 4,3GHz
Display 1: Acer Predator XB271HU, 2560x1440 @ 165Hz
Display 2: BenQ RL2455, 1920x1080 @ 60Hz
Nvidia Driver version: 376.19 (now, back when I had issues it was 375.95 as mentioned above)
OS: Windows 10 Pro 64-bit

HOWEVER,

I wasn't able to reproduce the same problems now with new Nvidia drivers  376.19. Only difference on the settings that I had was game set to fullscreen and max refresh rate set to 144Hz instead of 165Hz. After 30min run of  Apollodorus the fps and frame time were excactly the same around 136fps and 7ms.

 

Edited December 10, 2016 by Dragstein

[Lcnt]

Unable to reproduce.

1. GPU Model: GTX 1070 mobile
2. Operating System: Windows 10 64 bits Pro
3. Nvidia Driver Version: 376.19
4. Frame Time Before: ~3.0 ms
5. Frame Time After: ~3.5 ms
6. Programs Running: Steam (no overlay), Opera
7. Additional infos: Warframe standalone client, borderless windowed mode, no GeForce Experience.

I used to have a huge memory leak when running Hieracon on my old setup with an AMD 7970m. Is this related? I'll have to run a few Hieracons to try it out, haven't really paid attention to performances lately, because even when framerate drops on my 1070 it's still above my fps cap.

Edited December 10, 2016 by Lcnt