{"action":"created","issue":{"url":"https://api.github.com/repos/sharpdx/SharpDX/issues/697","labels_url":"https://api.github.com/repos/sharpdx/SharpDX/issues/697/labels{/name}","comments_url":"https://api.github.com/repos/sharpdx/SharpDX/issues/697/comments","events_url":"https://api.github.com/repos/sharpdx/SharpDX/issues/697/events","html_url":"https://github.com/sharpdx/SharpDX/issues/697","id":127814636,"number":697,"title":"Possible issue with v3.0.0 on Windows 10?","user":{"login":"BEEden","id":13035761,"avatar_url":"https://avatars.githubusercontent.com/u/13035761?v=3","gravatar_id":"","url":"https://api.github.com/users/BEEden","html_url":"https://github.com/BEEden","followers_url":"https://api.github.com/users/BEEden/followers","following_url":"https://api.github.com/users/BEEden/following{/other_user}","gists_url":"https://api.github.com/users/BEEden/gists{/gist_id}","starred_url":"https://api.github.com/users/BEEden/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/BEEden/subscriptions","organizations_url":"https://api.github.com/users/BEEden/orgs","repos_url":"https://api.github.com/users/BEEden/repos","events_url":"https://api.github.com/users/BEEden/events{/privacy}","received_events_url":"https://api.github.com/users/BEEden/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2016-01-21T00:03:49Z","updated_at":"2016-01-21T00:24:16Z","closed_at":"2016-01-21T00:14:58Z","body":"I have been using SharpDX for some time now and it has been very reliable and easy to work with.  Recently I upgraded to v3.0.0 and aside from having to make a few changes from Vector2 to RawVector2, it was a no-brainer.  \r\n\r\nHowever, it soon became apparent that I had a few unresolved memory leaks, so I installed the Windows 10 SDK so that I could access the D3D Debug Layer.  This is where my problems started -- although I was able to quickly locate and resolve all of the memory leaks, installing the Windows 10 SDK killed the performance of my project -- whether or not the debug layer is turned on.  I went from being able to have 1200 or so integration-driven Direct2D1 geometries running on-screen at a stable 60fps, down to less than 300 before the application becomes slow and sometimes completely unresponsive.\r\n\r\nAfter spending hours trying to locate the source of the problem, including extensive profiling, I loaded an old SharpDX project from a few months ago and found that it exhibited the same behaviour, even when run from a pre-compiled binary that was built months ago.  I also tried another workstation running Windows 10 and even updated the nVidia driver to the latest version just in case, albeit with no luck.\r\n\r\nIt appears that installing the Windows 10 SDK was the cause of the problem, but uninstalling it does not resolve the issue.  i am running Visual Studio 2013 with all updates installed.  Any suggestions would be gratefully received!  Many thanks."},"comment":{"url":"https://api.github.com/repos/sharpdx/SharpDX/issues/comments/173411254","html_url":"https://github.com/sharpdx/SharpDX/issues/697#issuecomment-173411254","issue_url":"https://api.github.com/repos/sharpdx/SharpDX/issues/697","id":173411254,"user":{"login":"BEEden","id":13035761,"avatar_url":"https://avatars.githubusercontent.com/u/13035761?v=3","gravatar_id":"","url":"https://api.github.com/users/BEEden","html_url":"https://github.com/BEEden","followers_url":"https://api.github.com/users/BEEden/followers","following_url":"https://api.github.com/users/BEEden/following{/other_user}","gists_url":"https://api.github.com/users/BEEden/gists{/gist_id}","starred_url":"https://api.github.com/users/BEEden/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/BEEden/subscriptions","organizations_url":"https://api.github.com/users/BEEden/orgs","repos_url":"https://api.github.com/users/BEEden/repos","events_url":"https://api.github.com/users/BEEden/events{/privacy}","received_events_url":"https://api.github.com/users/BEEden/received_events","type":"User","site_admin":false},"created_at":"2016-01-21T00:24:16Z","updated_at":"2016-01-21T00:24:16Z","body":"Well, I used the term \"possible\", because I didn't want to assume straight away that SharpDX was the problem -- it has been fast, very reliable, very easy to use and I cannot recommend it enough.  I was hoping that someone else might have experienced something similar.  Thanks anyway, xoofx."}}