# Investigating a Deleaker Crash During COM Registration in ReactOS

DevFeed: [Investigating a Deleaker Crash During COM Registration in ReactOS](<https://devfeed.tech/articles/spilling-the-wine-33023.md>)

Original publisher: [Read original article](<https://reactos.org/blogs/spilling-the-wine/>)

Published: 2014-06-23T00:00:00Z

Content type: article

Language: en

Sources: [Front Page on ReactOS Website](<https://devfeed.tech/sources/front-page-on-reactos-website.md>)

Topics: [ReactOS](<https://devfeed.tech/topics/reactos.md>), [opensource](<https://devfeed.tech/topics/opensource.md>), [Code](<https://devfeed.tech/topics/code.md>), [Windows](<https://devfeed.tech/topics/windows.md>)

Tags: [code](<https://devfeed.tech/tags/code.md>), [free](<https://devfeed.tech/tags/free.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [opensource](<https://devfeed.tech/tags/opensource.md>), [os](<https://devfeed.tech/tags/os.md>), [react](<https://devfeed.tech/tags/react.md>), [reactos](<https://devfeed.tech/tags/reactos.md>), [win32](<https://devfeed.tech/tags/win32.md>), [winapi](<https://devfeed.tech/tags/winapi.md>), [windows](<https://devfeed.tech/tags/windows.md>)

## AI overview

The article describes investigating why Deleaker crashes in ReactOS during COM registration. Obfuscated disassembly creates fragmented function paths that disassemblers struggle to follow.

## Source excerpt

After the frustration of last week, I decided to take one last look at Deleaker, and try to figure out why it crashes in ReactOS during COM registration. The problem is, looking at the disassembly made it clear that the code is obfuscated. The functions start in one address, and then they jump all over the place, creating a mesh of small function chunks that even the best disassemblers seem unable to follow.