# ReactOS Newsletter 63: Automated Test Fix and MSVC Compatibility Work

DevFeed: [ReactOS Newsletter 63: Automated Test Fix and MSVC Compatibility Work](<https://devfeed.tech/articles/newsletter-63-32929.md>)

Original publisher: [Read original article](<https://reactos.org/blogs/newsletter-63/>)

Published: 2009-08-01T00: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>), [Testing](<https://devfeed.tech/topics/testing.md>), [bug](<https://devfeed.tech/topics/bug.md>), [MSVC](<https://devfeed.tech/topics/msvc.md>), [gcc](<https://devfeed.tech/topics/gcc.md>)

Tags: [bug](<https://devfeed.tech/tags/bug.md>), [comes](<https://devfeed.tech/tags/comes.md>), [free](<https://devfeed.tech/tags/free.md>), [gcc](<https://devfeed.tech/tags/gcc.md>), [memory](<https://devfeed.tech/tags/memory.md>), [msvc](<https://devfeed.tech/tags/msvc.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [os](<https://devfeed.tech/tags/os.md>), [react](<https://devfeed.tech/tags/react.md>), [reactos](<https://devfeed.tech/tags/reactos.md>), [testing](<https://devfeed.tech/tags/testing.md>), [win32](<https://devfeed.tech/tags/win32.md>), [winapi](<https://devfeed.tech/tags/winapi.md>)

## AI overview

ReactOS Newsletter 63 reports a fix for an infinite loop in the automated test suite caused by memory corruption in LoadLibraryExW when handling an untrimmed library name. It also describes ongoing fixes for MSVC compilation and syntax issues.

## Source excerpt

Test Disruptions For several days the automated testing suite that runs every ReactOS revision got stuck in an infinite loop once it reached the msi_winetest. Several people following the testing noticed this issue and suggested possible causes but Jeffrey Morlan eventually committed a patch that seems to resolve it. The problem appeared to be in the LoadLibraryExW function, in a specific case where the LOAD_LIBRARY_AS_DATAFILE flag was set. The function received as one of its inputs DllName, the name of the library it was being asked to load.