Comment Feed for Channel 9 - Diagnosing Application Issues - 01 http://media.ch9.ms/ch9/5411/99b0bb0b-e67c-4bad-9c58-f34d89c85411/NetDebuggingDiagnosingApplicationIssues01_220.jpg Channel 9 - Diagnosing Application Issues - 01 Download PPTX slide here: Part 1  You can't troubleshoot a problem effectively until you first know what the problem is. When applications encounter stability or performance issues in the production environment, obtaining an accurate problem definition is a key first-step to reducing Time To Resolution.  Learn how Microsoft Support leverages various tools & techniques to help customers define the problems plaguing their production applications.   .NET Debugging for the Production Environment, Part 2 en Thu, 20 Jun 2013 08:27:38 GMT Thu, 20 Jun 2013 08:27:38 GMT Rev9 Re: Diagnosing Application Issues - 01 Great video!  Would also be nice to see some troubleshooting of IIS 7.5 hosted WCF services (long running and/or high memory).

posted by scott_m

]]> http://channel9.msdn.com/(A(cSFyXJXzzAEkAAAANzEyZjRjOTAtYTMyMC00ZGEwLTliYjItOTg2NTIwMzI2MjVjgc-VZjdKOTJIVbCoVXIqp0D5hoQ1))/Series/-NET-Debugging-Stater-Kit-for-the-Production-Environment/Diagnosing-Application-Issues-01#c634715312607239769 Wed, 02 May 2012 04:54:20 GMT http://channel9.msdn.com/(A(cSFyXJXzzAEkAAAANzEyZjRjOTAtYTMyMC00ZGEwLTliYjItOTg2NTIwMzI2MjVjgc-VZjdKOTJIVbCoVXIqp0D5hoQ1))/Series/-NET-Debugging-Stater-Kit-for-the-Production-Environment/Diagnosing-Application-Issues-01#c634715312607239769 scott_m Re: Diagnosing Application Issues - 01 @scott_m - Thanks for the suggestion.  The next series of recordings will focus on high memory.  The debugging techniques are the same regardless of whether it's for WCF or a Winforms app or ASP.NET, etc.  Stay tuned...

posted by BradL

]]> http://channel9.msdn.com/(A(cSFyXJXzzAEkAAAANzEyZjRjOTAtYTMyMC00ZGEwLTliYjItOTg2NTIwMzI2MjVjgc-VZjdKOTJIVbCoVXIqp0D5hoQ1))/Series/-NET-Debugging-Stater-Kit-for-the-Production-Environment/Diagnosing-Application-Issues-01#c634715789659522890 Wed, 02 May 2012 18:09:25 GMT http://channel9.msdn.com/(A(cSFyXJXzzAEkAAAANzEyZjRjOTAtYTMyMC00ZGEwLTliYjItOTg2NTIwMzI2MjVjgc-VZjdKOTJIVbCoVXIqp0D5hoQ1))/Series/-NET-Debugging-Stater-Kit-for-the-Production-Environment/Diagnosing-Application-Issues-01#c634715789659522890 BradL Re: Diagnosing Application Issues - 01 Cool! In our current application I feel like every part of the application is slowin things just a little bit. I wonder how I can figure out what is the most important/impactful thing to optimize.

posted by Stilgar

]]> http://channel9.msdn.com/(A(cSFyXJXzzAEkAAAANzEyZjRjOTAtYTMyMC00ZGEwLTliYjItOTg2NTIwMzI2MjVjgc-VZjdKOTJIVbCoVXIqp0D5hoQ1))/Series/-NET-Debugging-Stater-Kit-for-the-Production-Environment/Diagnosing-Application-Issues-01#c634715811222463077 Wed, 02 May 2012 18:45:22 GMT http://channel9.msdn.com/(A(cSFyXJXzzAEkAAAANzEyZjRjOTAtYTMyMC00ZGEwLTliYjItOTg2NTIwMzI2MjVjgc-VZjdKOTJIVbCoVXIqp0D5hoQ1))/Series/-NET-Debugging-Stater-Kit-for-the-Production-Environment/Diagnosing-Application-Issues-01#c634715811222463077 Stilgar Re: Diagnosing Application Issues - 01 @Stilgar - What's worked for me &  my customers in the past is to first concentrate on resolving problems, and _then_ think about optimizations.  If you feel your app is running slowly, get data that will help to show if there is, in fact, a problem.
If this video didn't help you find your problem, try Part2 in this series, Using Perfmon to Diagnose Application Issues.

posted by BradL

]]> http://channel9.msdn.com/(A(cSFyXJXzzAEkAAAANzEyZjRjOTAtYTMyMC00ZGEwLTliYjItOTg2NTIwMzI2MjVjgc-VZjdKOTJIVbCoVXIqp0D5hoQ1))/Series/-NET-Debugging-Stater-Kit-for-the-Production-Environment/Diagnosing-Application-Issues-01#c634715946878423605 Wed, 02 May 2012 22:31:27 GMT http://channel9.msdn.com/(A(cSFyXJXzzAEkAAAANzEyZjRjOTAtYTMyMC00ZGEwLTliYjItOTg2NTIwMzI2MjVjgc-VZjdKOTJIVbCoVXIqp0D5hoQ1))/Series/-NET-Debugging-Stater-Kit-for-the-Production-Environment/Diagnosing-Application-Issues-01#c634715946878423605 BradL Re: Diagnosing Application Issues - 01 Hopefully I would be able to find the code guilty of this unmanaged memory leak I found in some slow netbooks:
http://stackoverflow.com/questions/10038155/how-to-detect-net-wpf-memory-leak-or-gc-long-run

posted by Nestor Sanchez A

]]> http://channel9.msdn.com/(A(cSFyXJXzzAEkAAAANzEyZjRjOTAtYTMyMC00ZGEwLTliYjItOTg2NTIwMzI2MjVjgc-VZjdKOTJIVbCoVXIqp0D5hoQ1))/Series/-NET-Debugging-Stater-Kit-for-the-Production-Environment/Diagnosing-Application-Issues-01#c634716082470988518 Thu, 03 May 2012 02:17:27 GMT http://channel9.msdn.com/(A(cSFyXJXzzAEkAAAANzEyZjRjOTAtYTMyMC00ZGEwLTliYjItOTg2NTIwMzI2MjVjgc-VZjdKOTJIVbCoVXIqp0D5hoQ1))/Series/-NET-Debugging-Stater-Kit-for-the-Production-Environment/Diagnosing-Application-Issues-01#c634716082470988518 Nestor Sanchez A Re: Diagnosing Application Issues - 01 Wow ! Very interesting series.

posted by felix9

]]> http://channel9.msdn.com/(A(cSFyXJXzzAEkAAAANzEyZjRjOTAtYTMyMC00ZGEwLTliYjItOTg2NTIwMzI2MjVjgc-VZjdKOTJIVbCoVXIqp0D5hoQ1))/Series/-NET-Debugging-Stater-Kit-for-the-Production-Environment/Diagnosing-Application-Issues-01#c634716468462024282 Thu, 03 May 2012 13:00:46 GMT http://channel9.msdn.com/(A(cSFyXJXzzAEkAAAANzEyZjRjOTAtYTMyMC00ZGEwLTliYjItOTg2NTIwMzI2MjVjgc-VZjdKOTJIVbCoVXIqp0D5hoQ1))/Series/-NET-Debugging-Stater-Kit-for-the-Production-Environment/Diagnosing-Application-Issues-01#c634716468462024282 felix9 Re: Diagnosing Application Issues - 01 nice series. But why don't you use procdump from sysinternals?

posted by MagicAndre1981

]]> http://channel9.msdn.com/(A(cSFyXJXzzAEkAAAANzEyZjRjOTAtYTMyMC00ZGEwLTliYjItOTg2NTIwMzI2MjVjgc-VZjdKOTJIVbCoVXIqp0D5hoQ1))/Series/-NET-Debugging-Stater-Kit-for-the-Production-Environment/Diagnosing-Application-Issues-01#c634720182435056778 Mon, 07 May 2012 20:10:43 GMT http://channel9.msdn.com/(A(cSFyXJXzzAEkAAAANzEyZjRjOTAtYTMyMC00ZGEwLTliYjItOTg2NTIwMzI2MjVjgc-VZjdKOTJIVbCoVXIqp0D5hoQ1))/Series/-NET-Debugging-Stater-Kit-for-the-Production-Environment/Diagnosing-Application-Issues-01#c634720182435056778 MagicAndre1981 Re: Diagnosing Application Issues - 01 @MagicAndre1981:You can use whatever tool you like that does .dump /ma.  Personal preference certainly plays a role.  The reason I focus on DebugDiag is b/c that's what most of our customers use to get dumps in production (and pre-prod).  So what advantages does it have over procdump?  I haven't used procdump in a while, but from what I recall...
- Let's say you set up a Crash Rule to dump foo.exe when it experiences ExceptionX.  If foo.exe shuts down for whatever reason and ExceptionX never happened, DD's Crash Rule kicks back in after foo.exe restarts.  So DD's Crash Rules sustain process restarts & machine reboots.
- DD tracks native leaks (very well, I might add), whether it's a leak in the native heaps or from calls to VA or a handle leak.  Yes, this series will focus on .NET debugging, but it's not uncommon that we have to wander into native debugging to find root cause.  So if a customer starts w/ DD, they don't have to switch to a different tool.
- DD also has an analyzer for hangs, crashes, and native leaks.
- Customers like the GUI/wizard of DD.  It's very intuitive.

There may be additional reasons.  These are the ones that come to mind first.

posted by BradL

]]> http://channel9.msdn.com/(A(cSFyXJXzzAEkAAAANzEyZjRjOTAtYTMyMC00ZGEwLTliYjItOTg2NTIwMzI2MjVjgc-VZjdKOTJIVbCoVXIqp0D5hoQ1))/Series/-NET-Debugging-Stater-Kit-for-the-Production-Environment/Diagnosing-Application-Issues-01#c634720478062644825 Tue, 08 May 2012 04:23:26 GMT http://channel9.msdn.com/(A(cSFyXJXzzAEkAAAANzEyZjRjOTAtYTMyMC00ZGEwLTliYjItOTg2NTIwMzI2MjVjgc-VZjdKOTJIVbCoVXIqp0D5hoQ1))/Series/-NET-Debugging-Stater-Kit-for-the-Production-Environment/Diagnosing-Application-Issues-01#c634720478062644825 BradL Re: Diagnosing Application Issues - 01 Thanks, excellent video.

Could you please share the links you showed in video? It's difficult to type in all those links.

posted by wowps

]]> http://channel9.msdn.com/(A(cSFyXJXzzAEkAAAANzEyZjRjOTAtYTMyMC00ZGEwLTliYjItOTg2NTIwMzI2MjVjgc-VZjdKOTJIVbCoVXIqp0D5hoQ1))/Series/-NET-Debugging-Stater-Kit-for-the-Production-Environment/Diagnosing-Application-Issues-01#c634720572931101166 Tue, 08 May 2012 07:01:33 GMT http://channel9.msdn.com/(A(cSFyXJXzzAEkAAAANzEyZjRjOTAtYTMyMC00ZGEwLTliYjItOTg2NTIwMzI2MjVjgc-VZjdKOTJIVbCoVXIqp0D5hoQ1))/Series/-NET-Debugging-Stater-Kit-for-the-Production-Environment/Diagnosing-Application-Issues-01#c634720572931101166 wowps Re: Diagnosing Application Issues - 01

, BradL wrote

- Let's say you set up a Crash Rule to dump foo.exe when it experiences ExceptionX.  If foo.exe shuts down for whatever reason and ExceptionX never happened, DD's Crash Rule kicks back in after foo.exe restarts.  So DD's Crash Rules sustain process restarts & machine reboots.
- DD tracks native leaks (very well, I might add), whether it's a leak in the native heaps or from calls to VA or a handle leak.  Yes, this series will focus on .NET debugging, but it's not uncommon that we have to wander into native debugging to find root cause.  So if a customer starts w/ DD, they don't have to switch to a different tool.
- DD also has an analyzer for hangs, crashes, and native leaks.
- Customers like the GUI/wizard of DD.  It's very intuitive.

ok, thanks.

1 question. ProcDump has those new MiniPlus dumps, which are smaller than full dumps. Have you tried them? Are they good to debug issues?

posted by MagicAndre1981

]]> http://channel9.msdn.com/(A(cSFyXJXzzAEkAAAANzEyZjRjOTAtYTMyMC00ZGEwLTliYjItOTg2NTIwMzI2MjVjgc-VZjdKOTJIVbCoVXIqp0D5hoQ1))/Series/-NET-Debugging-Stater-Kit-for-the-Production-Environment/Diagnosing-Application-Issues-01#c634721060034013908 Tue, 08 May 2012 20:33:23 GMT http://channel9.msdn.com/(A(cSFyXJXzzAEkAAAANzEyZjRjOTAtYTMyMC00ZGEwLTliYjItOTg2NTIwMzI2MjVjgc-VZjdKOTJIVbCoVXIqp0D5hoQ1))/Series/-NET-Debugging-Stater-Kit-for-the-Production-Environment/Diagnosing-Application-Issues-01#c634721060034013908 MagicAndre1981 Re: Diagnosing Application Issues - 01 @wowps:DD usage (written before the 1.2 release): http://msdn.microsoft.com/en-us/library/ff420662.aspx#Usage.  Also, see the DD help file.  Download the latest DD from microsoft.com/downloads.
AD+: read Debugger.chm in the Debugging Tools for Windows package
ASP.NET Health Monitoring: http://msdn.microsoft.com/en-us/library/bb398933(v=vs.100).aspx">http://msdn.microsoft.com/en-us/library/bb398933(v=vs.100).aspx
ASP.NET Performance Monitoring: http://msdn.microsoft.com/en-us/library/ms972959.aspx

posted by BradL

]]> http://channel9.msdn.com/(A(cSFyXJXzzAEkAAAANzEyZjRjOTAtYTMyMC00ZGEwLTliYjItOTg2NTIwMzI2MjVjgc-VZjdKOTJIVbCoVXIqp0D5hoQ1))/Series/-NET-Debugging-Stater-Kit-for-the-Production-Environment/Diagnosing-Application-Issues-01#c634721285558859166 Wed, 09 May 2012 02:49:15 GMT http://channel9.msdn.com/(A(cSFyXJXzzAEkAAAANzEyZjRjOTAtYTMyMC00ZGEwLTliYjItOTg2NTIwMzI2MjVjgc-VZjdKOTJIVbCoVXIqp0D5hoQ1))/Series/-NET-Debugging-Stater-Kit-for-the-Production-Environment/Diagnosing-Application-Issues-01#c634721285558859166 BradL Re: Diagnosing Application Issues - 01 @MagicAndre1981:I haven't messed with MiniPlus dumps.  If memory serves correct, they have their root in tshooting Exchange issues and come in handy when dumping large processes (e.g., x64 processes with a lot of committed memory).  I'm not implying they're exclusive for Exchange issues, as I don't think that's the case.  I'm not aware of an equivalent switch for the .dump command that'll create MiniPlus's.
Without any experience with them, I can't say much about them.

posted by BradL

]]> http://channel9.msdn.com/(A(cSFyXJXzzAEkAAAANzEyZjRjOTAtYTMyMC00ZGEwLTliYjItOTg2NTIwMzI2MjVjgc-VZjdKOTJIVbCoVXIqp0D5hoQ1))/Series/-NET-Debugging-Stater-Kit-for-the-Production-Environment/Diagnosing-Application-Issues-01#c634721287445259615 Wed, 09 May 2012 02:52:24 GMT http://channel9.msdn.com/(A(cSFyXJXzzAEkAAAANzEyZjRjOTAtYTMyMC00ZGEwLTliYjItOTg2NTIwMzI2MjVjgc-VZjdKOTJIVbCoVXIqp0D5hoQ1))/Series/-NET-Debugging-Stater-Kit-for-the-Production-Environment/Diagnosing-Application-Issues-01#c634721287445259615 BradL Re: Diagnosing Application Issues - 01 Hi ---

 

Is it possible for us to get the slides for each one of these sessions?

 

posted by dm1608

]]> http://channel9.msdn.com/(A(cSFyXJXzzAEkAAAANzEyZjRjOTAtYTMyMC00ZGEwLTliYjItOTg2NTIwMzI2MjVjgc-VZjdKOTJIVbCoVXIqp0D5hoQ1))/Series/-NET-Debugging-Stater-Kit-for-the-Production-Environment/Diagnosing-Application-Issues-01#c634721887852955619 Wed, 09 May 2012 19:33:05 GMT http://channel9.msdn.com/(A(cSFyXJXzzAEkAAAANzEyZjRjOTAtYTMyMC00ZGEwLTliYjItOTg2NTIwMzI2MjVjgc-VZjdKOTJIVbCoVXIqp0D5hoQ1))/Series/-NET-Debugging-Stater-Kit-for-the-Production-Environment/Diagnosing-Application-Issues-01#c634721887852955619 dm1608 Re: Diagnosing Application Issues - 01 @dm1608:We're working on it.  No ETA yet.

posted by BradL

]]> http://channel9.msdn.com/(A(cSFyXJXzzAEkAAAANzEyZjRjOTAtYTMyMC00ZGEwLTliYjItOTg2NTIwMzI2MjVjgc-VZjdKOTJIVbCoVXIqp0D5hoQ1))/Series/-NET-Debugging-Stater-Kit-for-the-Production-Environment/Diagnosing-Application-Issues-01#c634724817944610445 Sun, 13 May 2012 04:56:34 GMT http://channel9.msdn.com/(A(cSFyXJXzzAEkAAAANzEyZjRjOTAtYTMyMC00ZGEwLTliYjItOTg2NTIwMzI2MjVjgc-VZjdKOTJIVbCoVXIqp0D5hoQ1))/Series/-NET-Debugging-Stater-Kit-for-the-Production-Environment/Diagnosing-Application-Issues-01#c634724817944610445 BradL Re: Diagnosing Application Issues - 01 I concur.  Slides would be great.  My organization is entirely new to .NET and we need all the resources that the great folks at MS provide Big Smile

 

posted by deadonthefloor

]]> http://channel9.msdn.com/(A(cSFyXJXzzAEkAAAANzEyZjRjOTAtYTMyMC00ZGEwLTliYjItOTg2NTIwMzI2MjVjgc-VZjdKOTJIVbCoVXIqp0D5hoQ1))/Series/-NET-Debugging-Stater-Kit-for-the-Production-Environment/Diagnosing-Application-Issues-01#c634726058554194408 Mon, 14 May 2012 15:24:15 GMT http://channel9.msdn.com/(A(cSFyXJXzzAEkAAAANzEyZjRjOTAtYTMyMC00ZGEwLTliYjItOTg2NTIwMzI2MjVjgc-VZjdKOTJIVbCoVXIqp0D5hoQ1))/Series/-NET-Debugging-Stater-Kit-for-the-Production-Environment/Diagnosing-Application-Issues-01#c634726058554194408 deadonthefloor Re: Diagnosing Application Issues - 01 I just started watching this series.  Great series!  I'm learning a lot, especially about things I didn't even know was there, like Perfmon.  I've got a question about performance monitor.  I have been able to find it on my Windows 7 box, but can't on my old XP box.  Here at work we have a mixture of XP and Win7, so it would be great if I could run that on XP as well.  Is it there?

posted by RodAtWork

]]> http://channel9.msdn.com/(A(cSFyXJXzzAEkAAAANzEyZjRjOTAtYTMyMC00ZGEwLTliYjItOTg2NTIwMzI2MjVjgc-VZjdKOTJIVbCoVXIqp0D5hoQ1))/Series/-NET-Debugging-Stater-Kit-for-the-Production-Environment/Diagnosing-Application-Issues-01#c634727741334745205 Wed, 16 May 2012 14:08:53 GMT http://channel9.msdn.com/(A(cSFyXJXzzAEkAAAANzEyZjRjOTAtYTMyMC00ZGEwLTliYjItOTg2NTIwMzI2MjVjgc-VZjdKOTJIVbCoVXIqp0D5hoQ1))/Series/-NET-Debugging-Stater-Kit-for-the-Production-Environment/Diagnosing-Application-Issues-01#c634727741334745205 RodAtWork Re: Diagnosing Application Issues - 01 @RodAtWork:Yes, it's there.  Start, Run, perfmon.  You should see it in the sys32 directory.

posted by BradL

]]> http://channel9.msdn.com/(A(cSFyXJXzzAEkAAAANzEyZjRjOTAtYTMyMC00ZGEwLTliYjItOTg2NTIwMzI2MjVjgc-VZjdKOTJIVbCoVXIqp0D5hoQ1))/Series/-NET-Debugging-Stater-Kit-for-the-Production-Environment/Diagnosing-Application-Issues-01#c634728293311257167 Thu, 17 May 2012 05:28:51 GMT http://channel9.msdn.com/(A(cSFyXJXzzAEkAAAANzEyZjRjOTAtYTMyMC00ZGEwLTliYjItOTg2NTIwMzI2MjVjgc-VZjdKOTJIVbCoVXIqp0D5hoQ1))/Series/-NET-Debugging-Stater-Kit-for-the-Production-Environment/Diagnosing-Application-Issues-01#c634728293311257167 BradL Re: Diagnosing Application Issues - 01 Please provide the PPT to all

posted by Rama Krushnudu

]]> http://channel9.msdn.com/(A(cSFyXJXzzAEkAAAANzEyZjRjOTAtYTMyMC00ZGEwLTliYjItOTg2NTIwMzI2MjVjgc-VZjdKOTJIVbCoVXIqp0D5hoQ1))/Series/-NET-Debugging-Stater-Kit-for-the-Production-Environment/Diagnosing-Application-Issues-01#c634735506331481209 Fri, 25 May 2012 13:50:33 GMT http://channel9.msdn.com/(A(cSFyXJXzzAEkAAAANzEyZjRjOTAtYTMyMC00ZGEwLTliYjItOTg2NTIwMzI2MjVjgc-VZjdKOTJIVbCoVXIqp0D5hoQ1))/Series/-NET-Debugging-Stater-Kit-for-the-Production-Environment/Diagnosing-Application-Issues-01#c634735506331481209 Rama Krushnudu Re: Diagnosing Application Issues - 01

, BradL wrote

@RodAtWork:Yes, it's there.  Start, Run, perfmon.  You should see it in the sys32 directory.

Thank you, @BradL, that works perfectly!

posted by RodAtWork

]]> http://channel9.msdn.com/(A(cSFyXJXzzAEkAAAANzEyZjRjOTAtYTMyMC00ZGEwLTliYjItOTg2NTIwMzI2MjVjgc-VZjdKOTJIVbCoVXIqp0D5hoQ1))/Series/-NET-Debugging-Stater-Kit-for-the-Production-Environment/Diagnosing-Application-Issues-01#c634744330653747220 Mon, 04 Jun 2012 18:57:45 GMT http://channel9.msdn.com/(A(cSFyXJXzzAEkAAAANzEyZjRjOTAtYTMyMC00ZGEwLTliYjItOTg2NTIwMzI2MjVjgc-VZjdKOTJIVbCoVXIqp0D5hoQ1))/Series/-NET-Debugging-Stater-Kit-for-the-Production-Environment/Diagnosing-Application-Issues-01#c634744330653747220 RodAtWork Re: Diagnosing Application Issues - 01 @BradL:  The MiniPlus dumps are between Mini and Full. e.g.  procdump -mp notepad.exe

If it is a managed application, ProcDump forces you to get a Full - as you can't debug a partial managed application dump file.

If it is a native application, the dumping starts by making a Mini, and then adds the MEM_PRIVATE pages of the process. That is, the IMAGE and MAPPED pages are not included - thus causing a large space saving (these pages are still available as they are mapped in to the dump by the debugger via the original EXE/DLL file on disk or symbol server - .exepath).

The additional magic kicks in when there is more than 512Mb in the process (e.g. Exchange, AD, SQL Server, etc.). The heuristic removes the cache that these allocate but keep any fragment (4Mb blocks) that is being accessed at the time of the dump.  For a 48Gb process, you usually get a 1-2Gb dump file (that captures in 45-60sec, instead of 30+min).

posted by windev

]]> http://channel9.msdn.com/(A(cSFyXJXzzAEkAAAANzEyZjRjOTAtYTMyMC00ZGEwLTliYjItOTg2NTIwMzI2MjVjgc-VZjdKOTJIVbCoVXIqp0D5hoQ1))/Series/-NET-Debugging-Stater-Kit-for-the-Production-Environment/Diagnosing-Application-Issues-01#c634756474970824275 Mon, 18 Jun 2012 20:18:17 GMT http://channel9.msdn.com/(A(cSFyXJXzzAEkAAAANzEyZjRjOTAtYTMyMC00ZGEwLTliYjItOTg2NTIwMzI2MjVjgc-VZjdKOTJIVbCoVXIqp0D5hoQ1))/Series/-NET-Debugging-Stater-Kit-for-the-Production-Environment/Diagnosing-Application-Issues-01#c634756474970824275 windev