Kevin Gosse's banner

Kevin Gosse

@KooKiz • 5,576 subscribers

Bluesky: @kevingosse.net Principal engineer @ JetBrains, passionate about .NET, performance, and debugging. MVP. Coauthor of Pro .NET Memory Management - 2nd ed

Shorts

If you missed this video, I strongly recommend watching it. It's a great introduction to 3D graphics, short and easy to understand. I had a lot of fun reimplementing it in Winforms and text mode.

If you missed this video, I strongly recommend watching it. It's a great introduction to 3D graphics, short and easy to understand. I had a lot of fun reimplementing it in Winforms and text mode.

204,317 views

I finally got so annoyed with ctrl+c randomly failing that I built a tool for it. It monitors the content of the clipboard, and highlights the active window when a change is detected. It acts as a visual confirmation that you properly copied stuff.

I finally got so annoyed with ctrl+c randomly failing that I built a tool for it. It monitors the content of the clipboard, and highlights the active window when a change is detected. It acts as a visual confirmation that you properly copied stuff.

59,254 views

Videos

Anya Rossi

sweetdream.ai

SweetDream.ai•Sponsored•Livecam

Watch Anya Live

Anya is streaming live right now! Join her private show and enjoy exclusive content.

Exclusive private shows

1.2k viewers online

Private Show

Join now for exclusive access

Free preview available • Premium content

The problem is that applications need to use the OpenClipboard API to access the clipboard, which gives exclusive access. In other words, if two applications read the clipboard simultaneously, one is going to fail. Quoting the official documentation: "OpenClipboard fails if another window has the clipboard open." There's no perfect fix, most applications try to work around by implementing a retry logic, but even that can fail if an application keeps the clipboard open for too long. This is the reason why I developed ClipPing. It displays a visual notification when the clipboard is updated, so you can know immediately if your ctrl+c failed.

The problem is that applications need to use the OpenClipboard API to access the clipboard, which gives exclusive access. In other words, if two applications read the clipboard simultaneously, one is going to fail. Quoting the official documentation: "OpenClipboard fails if another window has the clipboard open." There's no perfect fix, most applications try to work around by implementing a retry logic, but even that can fail if an application keeps the clipboard open for too long. This is the reason why I developed ClipPing. It displays a visual notification when the clipboard is updated, so you can know immediately if your ctrl+c failed.

12,675 views • 23 days ago

In preparation for my talk at Update Conference, I've prepared a tool to visualize the activity of the GC. It was initially meant as a gimmick, but it turns out to be a good way to understand some GC mechanisms. For instance, here you can see the effect of DOTNET_GCDynamicAdaptationMode=1 on the lower side, dynamically scaling up the number of heaps to absorb a spike of traffic, then scaling back down. The top application is running with default settings. Both are receiving the same traffic. #dotnet #progc2

In preparation for my talk at Update Conference, I've prepared a tool to visualize the activity of the GC. It was initially meant as a gimmick, but it turns out to be a good way to understand some GC mechanisms. For instance, here you can see the effect of DOTNET_GCDynamicAdaptationMode=1 on the lower side, dynamically scaling up the number of heaps to absorb a spike of traffic, then scaling back down. The top application is running with default settings. Both are receiving the same traffic. #dotnet #progc2

200,068 views • 2 years ago

Something I wish I learned earlier. On Windows, when trying to copy the path from the explorer, I used to click on the address bar then copy the selected text. It breaks in two scenarios: - In the Quick Access folders (like Downloads), when trying to copy the path from the address bar, it copies "Downloads" instead of the full path - When the path is too big, Windows randomly clears the path it I click where the "X" is going to appear (and I *have* to click there because it's the only blank area, clicking elsewhere triggers the navigation) It turns out that both can be avoided by simply using right click -> Copy Address.

Something I wish I learned earlier. On Windows, when trying to copy the path from the explorer, I used to click on the address bar then copy the selected text. It breaks in two scenarios: - In the Quick Access folders (like Downloads), when trying to copy the path from the address bar, it copies "Downloads" instead of the full path - When the path is too big, Windows randomly clears the path it I click where the "X" is going to appear (and I have to click there because it's the only blank area, clicking elsewhere triggers the navigation) It turns out that both can be avoided by simply using right click -> Copy Address.

12,479 views • 1 month ago

Still a very early prototype, but here is Windbgpt, a #chatgpt-powered AI assistant directly in #Windbg! It analyzes the output of the commands, and provides guidance to solve the stated problem. Here is an example of it investigating a deadlock in a .NET application.

Still a very early prototype, but here is Windbgpt, a #chatgpt-powered AI assistant directly in #Windbg! It analyzes the output of the commands, and provides guidance to solve the stated problem. Here is an example of it investigating a deadlock in a .NET application.

65,955 views • 3 years ago

To help reduce the number of UI freezes caused by Resharper, I built an internal tool to measure UI responsiveness. Here, you can see the improvement between the current 2025.1 version (on the left) and the upcoming 2025.2 version (on the right) with out-of-process enabled.

To help reduce the number of UI freezes caused by Resharper, I built an internal tool to measure UI responsiveness. Here, you can see the improvement between the current 2025.1 version (on the left) and the upcoming 2025.2 version (on the right) with out-of-process enabled.

19,012 views • 10 months ago

No more content to load