DisplaFusion V9.0 Memory Bug

WARNING: You currently have Javascript disabled!
This website will not function correctly without Javascript enabled.

<< Discussions Reply

Feuerforst

4 discussion posts

Hey,

i've updatet my DisplayFusion yesterday to Version 9.0

And now i have some Big Memory Problems.

• Attachment [protected]: DisplayFusionDebugInfo.zip [38,555 bytes]

• Attachment: img_002.jpg [68,471 bytes]

img_002.jpg

Oct 26, 2017 (modified Oct 26, 2017) • #1

Feuerforst

4 discussion posts

And the RAM Usage is still going up

• Attachment [protected]: img_003.jpg [70,881 bytes]

Oct 26, 2017 • #2

We've had a few others run into this as well but haven't been able to reproduce it here yet. Could you attach a debug log? Here are the steps:

On the DisplayFusion Settings > Troubleshooting tab, change the Logging drop-down to "L1: Log Minimal" and click Apply
When the memory usage is over 1 GB, move on to the next step
Send us the DisplayFusion.log and DebugInfo.html files (can be found by clicking the Open Log button on the Troubleshooting tab)
Disable debug logging after sending the log

Oct 27, 2017 • #3

Henrik Bo Andersen

17 discussion posts

I'm experiencing the exact same abnormal memory use. When memory use increases, Displayfusion gets unresponsive. I'm hiding the taskbar and when this happens I can't get the taskbar to show.

Henrik

Oct 27, 2017 • #4

@Henrik: Could you try installing 9.0 Beta 4 to see if that makes any difference? We're trying to figure out if this started with Beta 5, or earlier.

Thanks!

Oct 27, 2017 • #5

Henrik Bo Andersen

17 discussion posts

I'll do that.

Henrik

Oct 27, 2017 • #6

Jonathan Livingston

6 discussion posts

Hello!

Another log.

• Attachment [protected]: DebugInfo.txt [177,404 bytes]

• Attachment [protected]: DisplayFusion.log [484,833 bytes]

• Attachment [protected]: taskman.jpg [289,633 bytes]

Oct 27, 2017 • #7

Thanks Jonathan! Could you guys try 8.1.2 and all the betas leading up to 9.0 to see which beta it starts happening in?

8.1.2: https://www.binaryfortress.com/Files/DisplayFusion/DisplayFusionSetup-8.1.2.exe
9.0 Beta 1: https://www.binaryfortress.com/Files/DisplayFusion/DisplayFusionSetup-9.0-Beta1.exe
9.0 Beta 2: https://www.binaryfortress.com/Files/DisplayFusion/DisplayFusionSetup-9.0-Beta2.exe
9.0 Beta 3: https://www.binaryfortress.com/Files/DisplayFusion/DisplayFusionSetup-9.0-Beta3.exe
9.0 Beta 4: https://www.binaryfortress.com/Files/DisplayFusion/DisplayFusionSetup-9.0-Beta4.exe
9.0 Beta 5: https://www.binaryfortress.com/Files/DisplayFusion/DisplayFusionSetup-9.0-Beta5.exe
9.0 Final: https://www.displayfusion.com/Download

I realize that's a lot of work, but we're hoping if we can find which beta it broke in, we'll be able to figure out which change broke it

Oct 27, 2017 • #8

Feuerforst

4 discussion posts

Took the whole day, that this happend again.
here are the Log Files, i hope it will help to find the Prpblem

I`ve never tryed the Beta Versions.
Just 8.1.2 and than V 9.0

• Attachment [protected]: DisplayFusionDebugInfo.zip [252,767 bytes]

Oct 27, 2017 (modified Oct 27, 2017) • #9

Jonathan Livingston

6 discussion posts

Quote:

Thanks Jonathan! Could you guys try 8.1.2 and all the betas leading up to 9.0 to see which beta it starts happening in?

Not at all.
Will try as far as possible.

Oct 27, 2017 • #10

Feuerforst

4 discussion posts

I'll try Beta 3. To delimit the Problem

I know that i never had any Problems with 8.1.2

Downloads are not working

• Attachment: img_006.jpg [28,077 bytes]

img_006.jpg

• Attachment: img_007.jpg [39,147 bytes]

img_007.jpg

Oct 27, 2017 (modified Oct 27, 2017) • #11

Jonathan Livingston

6 discussion posts

Quote:

I know that i never had any Problems with 8.1.2

Absolutely.

Oct 28, 2017 • #12

Jagoba Los Arcos

6 discussion posts

The first symptom I see when it starts go bad is all tray icons get corrupted on all screens except in primary. Then, display fusion become unresponsive and i need kill it to recover.

I downgraded versions one by one, For me this happen on beta 5 or higher, on beta 4 all fine so far.

Oct 28, 2017 • #13

Henrik Bo Andersen

17 discussion posts

Beta 4 is still running without any problems. Memory-use keeps below 100 MB.
Henrik

Oct 28, 2017 • #14

Ok great, thanks guys! Could you try disabling some features (Alt+Tab Handler, Window Snapping, etc) to see if any of them make a difference?

Oct 28, 2017 • #15

Jagoba Los Arcos

6 discussion posts

i installed beta 5 again. I was running it in a config with 4 monitors, one of them i have splited into two virtual. Display fusion get again 1gb memory and crashed. I should say that I was not using the pc, i mean, i let it with some browsers and other programs open and i went out of home, when i come back, display fusion was stuck. I restarted pc now and i will let DF configured without the windows split. Let's see if now it crash again...

Oct 28, 2017 • #16

Diftraku

3 discussion posts

I began having similar issues after updating from an earlier 9.0 beta to 9.0 beta 4 and then to 9.0 stable. Running on Win10 Pro (version 1709, build 16299.19).

I've mostly noticed it while watching Netflix and Youtube on Google Chrome in fullscreen but these might not be relevant, as it usually takes a while for DisplayFusion to start chugging RAM. I had it go up to 11GB just now.

I've disabled Window Triggers earlier to no avail, thinking it was the cause. I've enabled L1 logging, disabled Alt+Tab handling, disabled Window Snapping and maximizing windows while dragging to other screens for now. Will report back if the memory usage explodes again.

• Attachment: df_ram_usage.png [6,564 bytes]

df_ram_usage.png

Oct 28, 2017 • #17

Gabriel Moreno66171

7 discussion posts

Hello, I'm using DF for several years, never having a problem.

I'm experiencing the same memory bug.

• Attachment: DF RAM 01.JPG [91,576 bytes]

DF RAM 01.JPG

• Attachment: DF RAM 02.JPG [93,364 bytes]

DF RAM 02.JPG

Oct 29, 2017 • #18

Jagoba Los Arcos

6 discussion posts

more testing, been running beta 5 without windows spanning, again ram out of control and DF stuck, and i not even touch the computer. I also have it runining witout wallpaper images, only black color. My other config options are default ones.

Is there any other configuration you want i test?
BTW, i will run it again with L1 log enabled

Oct 29, 2017 • #19

Jagoba Los Arcos

6 discussion posts

I have the process right now at 250mb of memory and growing. I have the logs, but i see there is sensitive information there. Where can i send you this logs privately? i am not happy posting them here

Oct 29, 2017 • #20

Jagoba Los Arcos

6 discussion posts

i didnt see that attach can be protected

here are the logs, just after a crash at 2gb memory, hope this helps.

• Attachment [protected]: df_logs.zip [334,758 bytes]

Oct 29, 2017 • #21

Gabriel Moreno66171

7 discussion posts

How can I go back to the previous release 8.1.1? I run DF from Steam client.

By the way, I'll attach my logs soon. I hope it helps.

Oct 29, 2017 (modified Oct 29, 2017) • #22

fernandezcojones

2 discussion posts

I too suffer from this problem, was fine on version 8. Almost 10 GB of RAM hogged within 2 hours of start... that is massive.

I don't have time to check the betas, unfortunately. I tried to monitor exactly what I do in order to replicate this, but I wasn't able to come up with anything solid. All I did was playing games for 2 hours and this happened.

Oct 29, 2017 (modified Oct 29, 2017) • #23

Ok, thanks guys!

@Gabriel, you can download and install 8.1.2 from here: https://www.displayfusion.com/Download/#oldverions

If you install over top of your existing install, it will keep the Steam license intact.

Oct 30, 2017 • #24

Bishi

19 discussion posts

Also experiencing this issue, DF currently using all available RAM (3GB+) this is DF 9.0 Pro (non-beta)

• Attachment [protected]: DisplayFusion.log [140,444 bytes]

Oct 30, 2017 • #25

Ok guys, we have a new test build to try that may fix up this memory leak. Could you download and install it over top of your existing install, and let us know how it works out?
https://www.binaryfortress.com/Files/DisplayFusion/DisplayFusionSetup-9.0-20171030-1145.exe

Oct 30, 2017 • #26

Jagoba Los Arcos

6 discussion posts

installing, thanks

Oct 30, 2017 (modified Oct 30, 2017) • #27

Gabriel Moreno66171

7 discussion posts

Yesterday the bug happened several times. Today, at the moment, zero times. It's weird.

I'll install the new build inmediately anyway.

Thanks!

Oct 30, 2017 • #28

David Atkinson1

5 discussion posts

Keith , I have installed 9.0-20171030-1145. Initially all seemed OK. One window open on each of 2 monitors , memory stable hovering around 55MB. However, I toggled a Task Manager window to the primary from alternate screen , after which memory started increasing incrementally again. At approx 600MB DF froze completely forcing me to kill the Process and reload as alternate screen & taskbar + app were unresponsive. After reloading DF moving between screens did not trigger the memory leakage but opening DF Settings to save the logs did!. Logs attached covering as described.

• Attachment [protected]: DF_debug.zip [209,902 bytes]

Oct 30, 2017 (modified Oct 30, 2017) • #29

Diftraku

3 discussion posts

After disabling features as suggested and running DisplayFusion for a while, DisplayFusion caused the RAM to ran out (16GB) and took with it Chrome as it crashed. Attached is L1 level log files with crash and opening the program again to get the path to the log files.

I will have to downgrade to an older version as DisplayFusion is completely unusable with this memory leak going unchecked.

• Attachment [protected]: DebugInfo.txt [102,062 bytes]

• Attachment [protected]: DisplayFusion.log [5,122,813 bytes]

Oct 30, 2017 • #30

Maliquem

23 discussion posts

After a little time, the taskbar os my two secondary monitor stop working properly.
This started to happen after i updated to the 9.0 version.

Image attached.

This post was merged on Nov 1, 2017.

• Attachment [protected]: displayfusion bug.PNG [28,337 bytes]

Oct 31, 2017 • #31

Could you attach a copy of your troubleshooting info?

Open the Settings > Troubleshooting tab
Click the "Copy to Clipboard" button
Paste the text into a text file (please don't paste the text directly into your reply, the formatting gets garbled and makes it difficult to parse)
Reply with the file attached

Thanks!

This post was merged on Nov 1, 2017.

Oct 31, 2017 • #32

Maliquem

23 discussion posts

Here

This post was merged on Nov 1, 2017.

• Attachment [protected]: DisplayFusion 9.0 bug.txt [114,538 bytes]

Oct 31, 2017 • #33

feaRless

4 discussion posts

I have the same problem.
I've seen the process take as much as 19GB ram. After that DF is unresponsive and the process has to be killed.
I had the problem with 9.0 beta 5 and with the 9.0 stable release. It was not happening with 9.0 beta 4 if i recall correctly.
I believe the problem occurs faster if i watch fullscreen streams in firefox, but i have no proof.
OS: Windows 10 Prof. x64 v1709
Will hand in a log with enabled debugging the next time the problem occurs.

• Attachment [protected]: displayfusion1.jpg [22,972 bytes]

• Attachment [protected]: displayfusion2.jpg [12,327 bytes]

• Attachment [protected]: DisplayFusionDebugInfo.zip [25,710 bytes]

Nov 1, 2017 • #34

ral1sh

56 discussion posts

I'm seeing the same issue on DisplayFusion v9.0. I've seen it a few times, but just now managed to capture a VMMap and process dump (a whopping ~11GB!). A few observations which may be of assistance in tracking the problem down (very quick analysis):

There's a huge number of allocation on the managed and unmanaged heap (see attached).

Looking at the managed heap statistics the two major offenders are (I'm assuming the first one has a "malformed" type name due to some sort of code obfuscation):

Code
Copy
Select All

<snip>
00007ffd800ed7f8  7616032    182784768 .+
00007ffddb28bd38   209966    952711704 System.Byte[]
Total 9884624 objects

For the "malformed" type all of the allocations are 24 bytes each:

Code
Copy
Select All

<snip>
0000000007ac6128 00007ffd800ed7f8       24     
0000000007ac6140 00007ffd800ed7f8       24     
0000000007ac6158 00007ffd800ed7f8       24     
0000000007ac6170 00007ffd800ed7f8       24     
0000000007ac6188 00007ffd800ed7f8       24     
<snip>

Dumping one of the objects gives:

Code
Copy
Select All

Name:        .+
MethodTable: 00007ffd800ed7f8
EEClass:     00007ffd801382b8
Size:        24(0x18) bytes
File:        C:\Program Files (x86)\Binary Fortress\DisplayFusion\DisplayFusion.exe
Fields:
              MT    Field   Offset                 Type VT     Attr            Value Name
00007ffd800c1038  400216d        8                  .  0 instance 0000000000000000 
00007ffd800a9938  400216e     1920 ...legates.GetString  0   static 0000000007581b28

The Byte array is more interesting. Dumping one of them:

Code
Copy
Select All

Name:        System.Byte[]
MethodTable: 00007ffddb28bd38
EEClass:     00007ffddaca26c8
Size:        41088(0xa080) bytes
Array:       Rank 1, Number of elements 41064, Type Byte (Print Array)
Content:     .PNG........IHDR..............>a.....sRGB.........gAMA......a.....tEXtSoftware.Adobe ImageReadyq.e<....IDATx^...X...=.sNz1E.{...
Fields:
None

Let's write that out to disk:

Code
Copy
Select All

.writemem C:\Users\SDL\Desktop\test.png ba438b8 La068
Writing a068 bytes.....................

Sure enough, it's a PNG, and yes I can view it:

Code
Copy
Select All

test.png: PNG image data, 128 x 128, 8-bit/color RGBA, non-interlaced

I went through a whole bunch of them, and nearly all of them seemed to be PNG icons. There's also a lot of duplicates, but they're nonetheless unique entries in the array. Some sort of icon/image cache maybe?

Hope this helps narrow it down ...

• Attachment: VMMap.PNG [47,457 bytes]

VMMap.PNG

Nov 1, 2017 (modified Nov 1, 2017) • #35

ral1sh

56 discussion posts

Right, this time it happened again and I caught it happening rather than when memory usage had peaked. A huge number of threads are being created which are almost all waiting on unique event handles to be signalled. My earlier dump had a huge 4886 threads and 32,586 event handles. I've attached a dump of unique stacks which might provide some insight. If any DF devs want me to provide other info let me know. I could potentially turn on handle tracing or break on thread creation to try and capture the stack trace corresponding to all these threads being created.

• Attachment: Unique Stacks.txt [63,084 bytes]

Nov 1, 2017 • #36

Gabriel Moreno66171

7 discussion posts

Quote:

Hello everybody.

Until now, 36 hours after installing this build, the memory usage dropped dramatically, at least in my computer. No memory leak had happened. It looks like this build works for me.

Thanks about the help.

Nov 1, 2017 • #37

I have the same issue, but I think is related to memory issue. It stops working after memory peak, and all icons from right side of taskbar are gone.

It looks this memory issue can be reltaed to taskbar icons.
I'm using the latest build from memory issue thread.

This post was merged on Nov 1, 2017.

Nov 1, 2017 (modified Nov 1, 2017) • #38

@ral1sh: We had found those leaking PNG images as well, and they should be fixed up in the test build (https://www.binaryfortress.com/Files/DisplayFusion/DisplayFusionSetup-9.0-20171030-1145.exe). The test build will still create a massive number of threads under certain circumstances so we're still trying to track that down. I'll pass your info on to our devs and if they need to grab some info from you, they'll definitely give you a shout.

Thanks!

Nov 1, 2017 • #39

@Marcin: Yep, you're definitely right. I've merged that topic with the big one

Nov 1, 2017 • #40

Henrik Bo Andersen

17 discussion posts

Quote:

It seem to have worked

Still no crashes

Nov 1, 2017 • #41

For the folks that are still running into issues with the previous test build, could you try this new one? Please note that the Monitor Fading feature is disabled in this build.
http://www.binaryfortress.com/Files/DisplayFusion/DisplayFusionSetup-9.0-20171102-1545.exe

Nov 3, 2017 • #42

David Atkinson1

5 discussion posts

Quote:

This build appears stable to me after 8 hours running.

Nov 3, 2017 • #43

Excellent, glad to hear it! We'll have a more proper fix coming in the next public beta version

Nov 3, 2017 • #44

Special

120 discussion posts

So what is the cause of this, and why do some get it and others don't?

Nov 3, 2017 • #45

It actually had to do with some polling we added for the new Process Created trigger event. We've just posted 9.1 Beta 1, so if everyone can update to that and let us know how it works out, that would be great!

Nov 3, 2017 • #46

Knurr298739

1 discussion post

Quote:

I've tried installing it but my antivirus thought it's a virus and put it in quarantine....didn't have the problem with the 9.0 1545 fix posted yesterday. Is this normal for a beta version? I've never installed one for DF before...

Nov 4, 2017 • #47

Gabriel Moreno66171

7 discussion posts

Quote:

Installing now and checking.

A few days ago this version (https://www.binaryfortress.com/Files/DisplayFusion/DisplayFusionSetup-9.0-20171030-1145.exe) worked for me for several days until DF began to consuming more memory (aprox. 600-800 Mb). The RAM consume increased very slowly anyway.

Nov 4, 2017 • #48

@Knurr: We updated our code signing certificate with 9.1 B1, so that might have thrown it off. If you want to be safe, you can run the installer through virustotal.com to verify that it's clean.

Nov 4, 2017 • #49

Maliquem

23 discussion posts

The new build was working properly yesterday. But today the same problem show up again... And freeze my explorer.exe too.

• Attachment [protected]: DisplayFusion 9.0 log.txt [124,384 bytes]

Nov 4, 2017 • #50

@Maliquem: It looks like you're still running one of the older test builds. Could you try 9.1 Beta 1 that we released on Friday?

Nov 6, 2017 • #51

Gabriel Moreno66171

7 discussion posts

Quote:

@Maliquem: It looks like you're still running one of the older test builds. Could you try 9.1 Beta 1 that we released on Friday?

After 72 hours on testing, this build is, by now, stable in RAM usage for me (50-100 Mb).

I'll keep on testing it.

Nov 9, 2017 • #52

fernandezcojones

2 discussion posts

Testing the Beta since it's release, my memory usage is now at a stable 50-100 MB at all times. Seems to be working great, thanks!

Nov 11, 2017 • #53

ral1sh

56 discussion posts

Also can confirm I haven't seen the problem since v9.1 Beta 1. Great work!

Nov 12, 2017 • #54

Excellent, glad to hear it. Thanks for following up!

Nov 13, 2017 • #55

Gabriel Moreno66171

7 discussion posts

After days of testing the beta version, it has been stable at every time. I installed the final last release a few days ago and is stable too.

Thank you Keith for your support.

I'm happy to see so good support from DF team =D

Nov 18, 2017 • #56

No worries, glad to hear it. Thanks for the kind words!

Nov 20, 2017 • #57

Was this helpful?

(1)

(-)