<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title><![CDATA[James's Programming Page — SerialWatcherThread() taking too much CPU time? - Performance Profiler]]></title>
		<link>https://swforum.seekye.com/topic/10144/</link>
		<atom:link href="https://swforum.seekye.com/feed/rss/topic/10144/" rel="self" type="application/rss+xml" />
		<description><![CDATA[The most recent posts in SerialWatcherThread() taking too much CPU time? - Performance Profiler.]]></description>
		<lastBuildDate>Sat, 25 Jul 2020 17:22:19 +0000</lastBuildDate>
		<generator>PunBB</generator>
		<item>
			<title><![CDATA[SerialWatcherThread() taking too much CPU time? - Performance Profiler]]></title>
			<link>https://swforum.seekye.com/post/13119/#p13119</link>
			<description><![CDATA[<p>I&#039;ve been inspecting my app for performance issues, and I was surprised when I noticed an indication that the SerialWatcherThread() is taking a considerably high CPU time in Windows. I am not sure why the profiler is pointing to the call&nbsp; NativeMethods.CreateAutoResetEventOrThrow(). I understand that you have a lock inside the while() loop (WinHidManager.cs line 366) , and this thread is probably blocked. So, is that perhaps an incorrect measurement from the profiler? Also, would be nice to be able to disable those threads if I am not interested on these events.</p><p>Profiler screenshot image: ibb.co/GH6xmj0</p>]]></description>
			<author><![CDATA[null@example.com (giovaniluigi)]]></author>
			<pubDate>Sat, 25 Jul 2020 17:22:19 +0000</pubDate>
			<guid>https://swforum.seekye.com/post/13119/#p13119</guid>
		</item>
	</channel>
</rss>
