<?xml version="1.0"?><?xml-stylesheet type="text/xsl" href="/rss.xsl"?><rss version="2.0"><channel><title>QPerfmon Issue Tracker Rss Feed</title><link>http://qperfmon.codeplex.com/WorkItem/List.aspx</link><description>QPerfmon Issue Tracker Rss Description</description><item><title>Closed Issue: your example is wrong [7339]</title><link>http://qperfmon.codeplex.com/workitem/7339</link><description>Hi,&lt;br /&gt;&amp;#160;&lt;br /&gt;The command line in your example &amp;#40;both on the homepage and the example.cmd&amp;#41; is bad. You forgot to escape the &amp;#37; character and wrote Total instead of _Total.&lt;br /&gt;Here&amp;#39;s the corrected line&amp;#58;&lt;br /&gt;QPerfMon.exe &amp;#34;.&amp;#92;Processor&amp;#92;&amp;#37;&amp;#37; Processor Time&amp;#92;_Total&amp;#34; &amp;#34;.&amp;#92;Memory&amp;#92;&amp;#37;&amp;#37; Committed Bytes In Use&amp;#92;&amp;#92;&amp;#34; &amp;#34;.&amp;#92;Memory&amp;#92;Pages&amp;#47;sec&amp;#92;&amp;#92;0.1&amp;#34; &amp;#34;.&amp;#92;PhysicalDisk&amp;#92;Avg. Disk Queue Length&amp;#92;_Total&amp;#92;100&amp;#34; -title&amp;#58;Test&lt;br /&gt;&amp;#160;&lt;br /&gt;Otherwise, nice tool.&lt;br /&gt;Thanks&lt;br /&gt;</description><author>RudolfHenning</author><pubDate>Thu, 16 May 2013 04:57:43 GMT</pubDate><guid isPermaLink="false">Closed Issue: your example is wrong [7339] 20130516045743A</guid></item><item><title>Closed Issue: crash when monitoring a process that doesn't exist [7340]</title><link>http://qperfmon.codeplex.com/workitem/7340</link><description>Hello,&lt;br /&gt;&amp;#160;&lt;br /&gt;The program crashes if launched with a counter on a process that doesn&amp;#39;t exist.&lt;br /&gt;Or if a counter disappears&lt;br /&gt;&amp;#160;&lt;br /&gt;QPerfMon.exe &amp;#34;.&amp;#92;Process&amp;#92;&amp;#37;&amp;#37; Processor Time&amp;#92;SomeProgramNotCurrentlyRunning&amp;#34;&lt;br /&gt;&amp;#160;&lt;br /&gt;or &lt;br /&gt;&amp;#160;&lt;br /&gt;QPerfMon.exe &amp;#34;.&amp;#92;Process&amp;#92;&amp;#37;&amp;#37; Processor Time&amp;#92;SomeProgramCurrentlyRunning&amp;#34;&lt;br /&gt;-&amp;#62; close the monitored program &lt;br /&gt;-&amp;#62; crash&lt;br /&gt;&amp;#160;&lt;br /&gt;It would be better to display the counters that are actually available and add a comment like &amp;#34;not available&amp;#34; on the counter.&lt;br /&gt;Or just unchecking the line into the list view, so it could be enabled later.&lt;br /&gt;Anything but a crash &amp;#58;&amp;#41;&lt;br /&gt;</description><author>RudolfHenning</author><pubDate>Thu, 16 May 2013 04:57:42 GMT</pubDate><guid isPermaLink="false">Closed Issue: crash when monitoring a process that doesn't exist [7340] 20130516045742A</guid></item><item><title>Closed Issue: Exception when using scale on computer with different culture [10022]</title><link>http://qperfmon.codeplex.com/workitem/10022</link><description>Hi,&lt;br /&gt;&amp;#160;&lt;br /&gt;There is a small bug on computer using different decimal separator, in the formating dialog boxes, when using a scale which is inferior to 1&amp;#58; an exception rise. I think the problem is in methods Formatting_Load, because you have hard-coded decimal value to fill the Scale combo-box. Such hard coded value are not culture-dependant. I suggest you use something like that to avoid this problem&amp;#58;&lt;br /&gt;cboScale.Items.Add&amp;#40; String.Format&amp;#40; &amp;#34;&amp;#123;0&amp;#58;F1&amp;#125;&amp;#34;, 0.1 &amp;#41; &amp;#41;&amp;#59;&lt;br /&gt;cboScale.Items.Add&amp;#40; String.Format&amp;#40; &amp;#34;&amp;#123;0&amp;#58;F2&amp;#125;&amp;#34;, 0.01 &amp;#41; &amp;#41;&amp;#59;&lt;br /&gt;cboScale.Items.Add&amp;#40; String.Format&amp;#40; &amp;#34;&amp;#123;0&amp;#58;F3&amp;#125;&amp;#34;, 0.001 &amp;#41; &amp;#41;&amp;#59;&lt;br /&gt;cboScale.Items.Add&amp;#40; String.Format&amp;#40; &amp;#34;&amp;#123;0&amp;#58;F4&amp;#125;&amp;#34;, 0.0001 &amp;#41; &amp;#41;&amp;#59;&lt;br /&gt;cboScale.Items.Add&amp;#40; String.Format&amp;#40; &amp;#34;&amp;#123;0&amp;#58;F5&amp;#125;&amp;#34;, 0.00001 &amp;#41; &amp;#41;&amp;#59;&lt;br /&gt;cboScale.Items.Add&amp;#40; String.Format&amp;#40; &amp;#34;&amp;#123;0&amp;#58;F6&amp;#125;&amp;#34;, 0.000001 &amp;#41; &amp;#41;&amp;#59;&lt;br /&gt;cboScale.Items.Add&amp;#40; String.Format&amp;#40; &amp;#34;&amp;#123;0&amp;#58;F7&amp;#125;&amp;#34;, 0.0000001 &amp;#41; &amp;#41;&amp;#59;&lt;br /&gt;Perhaps, there is a better way to do that&amp;#58; I&amp;#39;m not very friendly toward culture-related stuff.&lt;br /&gt;&amp;#160;&lt;br /&gt;By the way, this small application is really useful &amp;#58;&amp;#41;&lt;br /&gt;</description><author>RudolfHenning</author><pubDate>Thu, 16 May 2013 04:57:42 GMT</pubDate><guid isPermaLink="false">Closed Issue: Exception when using scale on computer with different culture [10022] 20130516045742A</guid></item><item><title>Closed Issue: Always on top [11903]</title><link>http://qperfmon.codeplex.com/workitem/11903</link><description>Hi,&lt;br /&gt;It could be interesting to the option to toggle the window always on top.&lt;br /&gt;Regards&lt;br /&gt;</description><author>andreone</author><pubDate>Thu, 16 May 2013 04:57:41 GMT</pubDate><guid isPermaLink="false">Closed Issue: Always on top [11903] 20130516045741A</guid></item><item><title>Commented Issue: "Portable" qpmset files / force localhost [12019]</title><link>http://qperfmon.codeplex.com/workitem/12019</link><description>Hello,&lt;br /&gt;&lt;br /&gt;I recently wanted to share some qpmset files I made with my coworkers. I faced the issue that you save the hostname into the qpmset files. Although this is totally makes senses as this is part of the perf counter path and allow to monitor processes on remote machines, this makes difficult to share qpmset files for monitoring local processes. I made a script that changes the hostname to the localhost before  starting QPerfMon but this is not ideal. It would be better if QPerfMon could do it itself &amp;#59;&amp;#41;&lt;br /&gt;So here&amp;#39;s my proposal&amp;#58; add the ability to indicate to QPerfMon that it should replace the machine name with the current machine name when loading a qpmset file.&lt;br /&gt;I thought about two ways to achieve this&amp;#58;&lt;br /&gt;- It could be done with a simple check box like &amp;#34;force local&amp;#34; in the performance counter selection dialog. The information would be saved in the qpmset file with each perf counter.&lt;br /&gt;- An other way would be to add a command line switch &amp;#40;in this case, this would be for all perf counter of a qpmset file&amp;#41;.&lt;br /&gt;&lt;br /&gt;I can try to hack the code and submit a patch if you want.&lt;br /&gt;Regards,&lt;br /&gt;Comments: ** Comment from web user: andreone ** &lt;p&gt;Well I I tested the dot trick and it didn&amp;#39;t work. I guess I corrupted the xml because I just retested it and that works.&lt;br /&gt;My proposal still makes sense but I can live with a little edition once in a while.&lt;br /&gt;Thanks&lt;/p&gt;</description><author>andreone</author><pubDate>Fri, 13 Apr 2012 16:20:49 GMT</pubDate><guid isPermaLink="false">Commented Issue: "Portable" qpmset files / force localhost [12019] 20120413042049P</guid></item><item><title>Commented Issue: "Portable" qpmset files / force localhost [12019]</title><link>http://qperfmon.codeplex.com/workitem/12019</link><description>Hello,&lt;br /&gt;&lt;br /&gt;I recently wanted to share some qpmset files I made with my coworkers. I faced the issue that you save the hostname into the qpmset files. Although this is totally makes senses as this is part of the perf counter path and allow to monitor processes on remote machines, this makes difficult to share qpmset files for monitoring local processes. I made a script that changes the hostname to the localhost before  starting QPerfMon but this is not ideal. It would be better if QPerfMon could do it itself &amp;#59;&amp;#41;&lt;br /&gt;So here&amp;#39;s my proposal&amp;#58; add the ability to indicate to QPerfMon that it should replace the machine name with the current machine name when loading a qpmset file.&lt;br /&gt;I thought about two ways to achieve this&amp;#58;&lt;br /&gt;- It could be done with a simple check box like &amp;#34;force local&amp;#34; in the performance counter selection dialog. The information would be saved in the qpmset file with each perf counter.&lt;br /&gt;- An other way would be to add a command line switch &amp;#40;in this case, this would be for all perf counter of a qpmset file&amp;#41;.&lt;br /&gt;&lt;br /&gt;I can try to hack the code and submit a patch if you want.&lt;br /&gt;Regards,&lt;br /&gt;Comments: ** Comment from web user: RudolfHenning ** &lt;p&gt;Interesting idea. One question though, you do know that the &amp;#39;.&amp;#39; &amp;#40;dot&amp;#41; as machine name automatically defaults to the local machine. e.g. .&amp;#92;Processor&amp;#92;&amp;#37; Processor Time&amp;#92;_Total would always run on the &amp;#39;local machine&amp;#39; no matter which machine you run it on&amp;#63;&lt;br /&gt;I know the dialog box in my tool defaults to change the &amp;#39;.&amp;#39; to the full machine name but you can edit the name out again and replace it with a &amp;#39;.&amp;#39; &amp;#40;dot&amp;#41;. Then when you save it and reload it again the &amp;#39;.&amp;#39; remains meaning that it will open on the &amp;#39;local&amp;#39; machine.&lt;br /&gt;Does this helps&amp;#63;&lt;/p&gt;</description><author>RudolfHenning</author><pubDate>Fri, 13 Apr 2012 12:19:33 GMT</pubDate><guid isPermaLink="false">Commented Issue: "Portable" qpmset files / force localhost [12019] 20120413121933P</guid></item><item><title>Created Issue: "Portable" qpmset files / force localhost [12019]</title><link>http://qperfmon.codeplex.com/workitem/12019</link><description>Hello,&lt;br /&gt;&lt;br /&gt;I recently wanted to share some qpmset files I made with my coworkers. I faced the issue that you save the hostname into the qpmset files. Although this is totally makes senses as this is part of the perf counter path and allow to monitor processes on remote machines, this makes difficult to share qpmset files for monitoring local processes. I made a script that changes the hostname to the localhost before  starting QPerfMon but this is not ideal. It would be better if QPerfMon could do it itself &amp;#59;&amp;#41;&lt;br /&gt;So here&amp;#39;s my proposal&amp;#58; add the ability to indicate to QPerfMon that it should replace the machine name with the current machine name when loading a qpmset file.&lt;br /&gt;I thought about two ways to achieve this&amp;#58;&lt;br /&gt;- It could be done with a simple check box like &amp;#34;force local&amp;#34; in the performance counter selection dialog. The information would be saved in the qpmset file with each perf counter.&lt;br /&gt;- An other way would be to add a command line switch &amp;#40;in this case, this would be for all perf counter of a qpmset file&amp;#41;.&lt;br /&gt;&lt;br /&gt;I can try to hack the code and submit a patch if you want.&lt;br /&gt;Regards,&lt;br /&gt;</description><author>andreone</author><pubDate>Thu, 12 Apr 2012 22:23:48 GMT</pubDate><guid isPermaLink="false">Created Issue: "Portable" qpmset files / force localhost [12019] 20120412102348P</guid></item><item><title>Commented Issue: Always on top [11903]</title><link>http://qperfmon.codeplex.com/workitem/11903</link><description>Hi,&lt;br /&gt;It could be interesting to the option to toggle the window always on top.&lt;br /&gt;Regards&lt;br /&gt;Comments: ** Comment from web user: andreone ** &lt;p&gt;Thank you&lt;/p&gt;</description><author>andreone</author><pubDate>Fri, 30 Mar 2012 19:15:12 GMT</pubDate><guid isPermaLink="false">Commented Issue: Always on top [11903] 20120330071512P</guid></item><item><title>Commented Issue: Always on top [11903]</title><link>http://qperfmon.codeplex.com/workitem/11903</link><description>Hi,&lt;br /&gt;It could be interesting to the option to toggle the window always on top.&lt;br /&gt;Regards&lt;br /&gt;Comments: ** Comment from web user: RudolfHenning ** &lt;p&gt;Good news. Finally managed to implement this feature - Version 1.8.1.&lt;/p&gt;</description><author>RudolfHenning</author><pubDate>Tue, 27 Mar 2012 05:51:14 GMT</pubDate><guid isPermaLink="false">Commented Issue: Always on top [11903] 20120327055114A</guid></item><item><title>Commented Issue: Always on top [11903]</title><link>http://qperfmon.codeplex.com/workitem/11903</link><description>Hi,&lt;br /&gt;It could be interesting to the option to toggle the window always on top.&lt;br /&gt;Regards&lt;br /&gt;Comments: ** Comment from web user: RudolfHenning ** &lt;p&gt;Good idea. I&amp;#39;ll look into it when I have time.&lt;/p&gt;</description><author>RudolfHenning</author><pubDate>Mon, 26 Mar 2012 12:28:08 GMT</pubDate><guid isPermaLink="false">Commented Issue: Always on top [11903] 20120326122808P</guid></item><item><title>Created Issue: Always on top [11903]</title><link>http://qperfmon.codeplex.com/workitem/11903</link><description>Hi,&lt;br /&gt;It could be interesting to the option to toggle the window always on top.&lt;br /&gt;Regards&lt;br /&gt;</description><author>andreone</author><pubDate>Fri, 23 Mar 2012 17:02:04 GMT</pubDate><guid isPermaLink="false">Created Issue: Always on top [11903] 20120323050204P</guid></item><item><title>Closed Issue: Error parsing at startup [10162]</title><link>http://qperfmon.codeplex.com/workitem/10162</link><description>Doesn&amp;#39;t appear to work for me on Win7 x64. Error parsing processor time at startup then I can&amp;#39;t add any memory counters. Lots of input string not in correct format.&lt;br /&gt;Comments: &lt;p&gt;Not reproducable&lt;/p&gt;</description><author>RudolfHenning</author><pubDate>Thu, 10 Nov 2011 05:19:09 GMT</pubDate><guid isPermaLink="false">Closed Issue: Error parsing at startup [10162] 20111110051909A</guid></item><item><title>Commented Issue: Error parsing at startup [10162]</title><link>http://qperfmon.codeplex.com/workitem/10162</link><description>Doesn&amp;#39;t appear to work for me on Win7 x64. Error parsing processor time at startup then I can&amp;#39;t add any memory counters. Lots of input string not in correct format.&lt;br /&gt;Comments: ** Comment from web user: thnk2wn ** &lt;p&gt;Sure&lt;/p&gt;</description><author>thnk2wn</author><pubDate>Wed, 09 Nov 2011 16:04:39 GMT</pubDate><guid isPermaLink="false">Commented Issue: Error parsing at startup [10162] 20111109040439P</guid></item><item><title>Commented Issue: Error parsing at startup [10162]</title><link>http://qperfmon.codeplex.com/workitem/10162</link><description>Doesn&amp;#39;t appear to work for me on Win7 x64. Error parsing processor time at startup then I can&amp;#39;t add any memory counters. Lots of input string not in correct format.&lt;br /&gt;Comments: ** Comment from web user: RudolfHenning ** &lt;p&gt;Can I mark this as closed&amp;#47;fixed&amp;#63; &lt;/p&gt;</description><author>RudolfHenning</author><pubDate>Wed, 09 Nov 2011 15:39:14 GMT</pubDate><guid isPermaLink="false">Commented Issue: Error parsing at startup [10162] 20111109033914P</guid></item><item><title>Commented Issue: Error parsing at startup [10162]</title><link>http://qperfmon.codeplex.com/workitem/10162</link><description>Doesn&amp;#39;t appear to work for me on Win7 x64. Error parsing processor time at startup then I can&amp;#39;t add any memory counters. Lots of input string not in correct format.&lt;br /&gt;Comments: ** Comment from web user: thnk2wn ** &lt;p&gt;Standard stuff there, English &amp;#40;United States&amp;#41;. I dug into the code and that lead me to http&amp;#58;&amp;#47;&amp;#47;stackoverflow.com&amp;#47;questions&amp;#47;3121688&amp;#47;performance-counter-input-string-was-not-in-a-correct-format-c which lead me to http&amp;#58;&amp;#47;&amp;#47;drayblog.gotdns.com&amp;#47;index.php&amp;#47;2010&amp;#47;02&amp;#47;04&amp;#47;diagnostics-performancecounter-input-string-was-not-in-a-correct-format&amp;#47; which fixed the issue. It appears that maybe if you monkey with perf mon counters that this can happen both in perfmon and this tool.&lt;/p&gt;</description><author>thnk2wn</author><pubDate>Thu, 24 Mar 2011 13:50:47 GMT</pubDate><guid isPermaLink="false">Commented Issue: Error parsing at startup [10162] 20110324015047P</guid></item><item><title>Commented Issue: Error parsing at startup [10162]</title><link>http://qperfmon.codeplex.com/workitem/10162</link><description>Doesn&amp;#39;t appear to work for me on Win7 x64. Error parsing processor time at startup then I can&amp;#39;t add any memory counters. Lots of input string not in correct format.&lt;br /&gt;Comments: ** Comment from web user: RudolfHenning ** &lt;p&gt;I&amp;#39;ve tested the download and run &amp;#40;as is&amp;#41; on a Win 7 x64 machine without issue. There must be something different in your environment - perhaps regional settings or so. What language&amp;#47;region settings are you using for your OS&amp;#63;&lt;/p&gt;</description><author>RudolfHenning</author><pubDate>Wed, 23 Mar 2011 15:49:09 GMT</pubDate><guid isPermaLink="false">Commented Issue: Error parsing at startup [10162] 20110323034909P</guid></item><item><title>Commented Issue: Error parsing at startup [10162]</title><link>http://qperfmon.codeplex.com/workitem/10162</link><description>Doesn&amp;#39;t appear to work for me on Win7 x64. Error parsing processor time at startup then I can&amp;#39;t add any memory counters. Lots of input string not in correct format.&lt;br /&gt;Comments: ** Comment from web user: thnk2wn ** &lt;p&gt;I still have the same issue after downloading the latest copy just now.&lt;/p&gt;</description><author>thnk2wn</author><pubDate>Wed, 23 Mar 2011 14:08:03 GMT</pubDate><guid isPermaLink="false">Commented Issue: Error parsing at startup [10162] 20110323020803P</guid></item><item><title>Commented Issue: Error parsing at startup [10162]</title><link>http://qperfmon.codeplex.com/workitem/10162</link><description>Doesn&amp;#39;t appear to work for me on Win7 x64. Error parsing processor time at startup then I can&amp;#39;t add any memory counters. Lots of input string not in correct format.&lt;br /&gt;Comments: ** Comment from web user: RudolfHenning ** &lt;p&gt;Do you still have the same issue and&amp;#47;or have you tried the latest version&amp;#63;&lt;/p&gt;</description><author>RudolfHenning</author><pubDate>Tue, 08 Mar 2011 09:20:42 GMT</pubDate><guid isPermaLink="false">Commented Issue: Error parsing at startup [10162] 20110308092042A</guid></item><item><title>Commented Issue: Error parsing at startup [10162]</title><link>http://qperfmon.codeplex.com/workitem/10162</link><description>Doesn&amp;#39;t appear to work for me on Win7 x64. Error parsing processor time at startup then I can&amp;#39;t add any memory counters. Lots of input string not in correct format.&lt;br /&gt;Comments: ** Comment from web user: thnk2wn ** &lt;p&gt;It was quite a while ago, I don&amp;#39;t remember. But I don&amp;#39;t think I specified any startup parameter. I just ran the exe directly.&lt;/p&gt;</description><author>thnk2wn</author><pubDate>Mon, 07 Mar 2011 13:35:45 GMT</pubDate><guid isPermaLink="false">Commented Issue: Error parsing at startup [10162] 20110307013545P</guid></item><item><title>Commented Issue: Error parsing at startup [10162]</title><link>http://qperfmon.codeplex.com/workitem/10162</link><description>Doesn&amp;#39;t appear to work for me on Win7 x64. Error parsing processor time at startup then I can&amp;#39;t add any memory counters. Lots of input string not in correct format.&lt;br /&gt;Comments: ** Comment from web user: RudolfHenning ** &lt;p&gt;I&amp;#39;m developing on a 64-bit platform so it is not that. How do you specify the startup parameter&amp;#63; Best is to use the qpmset type of files as it eliminate the need for escaping some reserved characters &amp;#40;but not all&amp;#41;. &lt;/p&gt;</description><author>RudolfHenning</author><pubDate>Mon, 07 Mar 2011 12:07:51 GMT</pubDate><guid isPermaLink="false">Commented Issue: Error parsing at startup [10162] 20110307120751P</guid></item></channel></rss>