Skip to main content

Windows Client & Win Launcher

Windows player application, Document/View, launcher utilities, and hooks.

Subsystem Metrics​

  • Total Documented Functions: 499
  • Functions Exercised in Tests: 14
  • Platform-Divergent Implementations: 117
  • Component Source Files: 45

Source Files​

View all 45 source files in this subsystem
Source FilePath
AuthenticationMarshallar.cppWin/AuthenticationMarshallar.cpp
CheckDbg.cppWin/CheckDbg.cpp
DSVideoCaptureEngine.cppWin/DSVideoCaptureEngine.cpp
DSVideoCaptureEngine.hWin/DSVideoCaptureEngine.h
DumpErrorUploader.cppWin/DumpErrorUploader.cpp
ErrorUploader.cppWin/ErrorUploader.cpp
ErrorUploader.hWin/ErrorUploader.h
LogManager.cppWin/LogManager.cpp
LogManager.hWin/LogManager.h
ProcessInformation.hWin/ProcessInformation.h
ScriptErrorUploader.cppWin/ScriptErrorUploader.cpp
ScriptErrorUploader.hWin/ScriptErrorUploader.h
SharedLauncher.cppWin/SharedLauncher.cpp
UserInputUtil.cppWin/UserInputUtil.cpp
VersionInfo.cppWin/VersionInfo.cpp
VideoControl.cppWin/VideoControl.cpp
VideoControl.hWin/VideoControl.h
VistaTools.cppWin/VistaTools.cpp
VistaTools.hWin/VistaTools.h
sitelock.hWin/sitelock.h
Application.cppWindowsClient/Application.cpp
Application.hWindowsClient/Application.h
Crypt.cppWindowsClient/Crypt.cpp
Document.cppWindowsClient/Document.cpp
Document.hWindowsClient/Document.h
FunctionMarshaller.cppWindowsClient/FunctionMarshaller.cpp
GameVerbs.cppWindowsClient/GameVerbs.cpp
GameVerbs.hWindowsClient/GameVerbs.h
RandomPadding.cppWindowsClient/RandomPadding.cpp
RbxWebView.cppWindowsClient/RbxWebView.cpp
RbxWebView.hWindowsClient/RbxWebView.h
ReleasePatcher.cppWindowsClient/ReleasePatcher.cpp
RenderJob.cppWindowsClient/RenderJob.cpp
main.cppWindowsClient/RobloxGoldenHashPatcher/main.cpp
Teleporter.cppWindowsClient/Teleporter.cpp
Teleporter.hWindowsClient/Teleporter.h
UserInput.cppWindowsClient/UserInput.cpp
UserInput.hWindowsClient/UserInput.h
View.cppWindowsClient/View.cpp
View.hWindowsClient/View.h
WebBrowserAxDialog.cppWindowsClient/WebBrowserAxDialog.cpp
WebBrowserAxDialog.hWindowsClient/WebBrowserAxDialog.h
functionHooks.cppWindowsClient/functionHooks.cpp
main.cppWindowsClient/main.cpp
robloxHooks.cppWindowsClient/robloxHooks.cpp

Function Reference​

1. buildUrl​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

std::string buildUrl(const char* url, const char* ticket);
PropertyValue
Return Typestd::string
ModifiersNone
Source LocationWin/AuthenticationMarshallar.cpp:20
SubsystemWindows Client & Win Launcher

How it Works Internally​

Executes buildUrl within Windows Client & Win Launcher.

  • Control Flow & Execution: Conditional branching, Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on buildUrl.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


2. AuthenticationMarshallar::Authenticate​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

std::string AuthenticationMarshallar::Authenticate(const char* url, const char* ticket);
PropertyValue
Return Typestd::string
ModifiersNone
Source LocationWin/AuthenticationMarshallar.cpp:32
SubsystemWindows Client & Win Launcher

How it Works Internally​

Executes Authenticate within Windows Client & Win Launcher. Coordinates interactions with http, buildUrl, c_str, setAuthDomain. Employs dynamic heap allocation via c++ operator new.

  • Control Flow & Execution: Explicit result return.
  • Memory Management: Dynamic heap allocation via C++ operator new.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Exception handling block (try/catch recovery).
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: http, buildUrl, c_str, setAuthDomain, get.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on Authenticate.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


3. AuthenticationMarshallar::AuthenticateAsync​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

RBX::HttpFuture AuthenticationMarshallar::AuthenticateAsync(const char* url, const char* ticket);
PropertyValue
Return TypeRBX::HttpFuture
ModifiersNone
Source LocationWin/AuthenticationMarshallar.cpp:54
SubsystemWindows Client & Win Launcher

How it Works Internally​

Executes AuthenticateAsync within Windows Client & Win Launcher. Coordinates interactions with addHeader, get, buildUrl.

  • Control Flow & Execution: Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: addHeader, get, buildUrl.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on AuthenticateAsync.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


4. GetFS​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

DWORD GetFS();
PropertyValue
Return TypeDWORD
Modifiersstatic __forceinline
Source LocationWin/CheckDbg.cpp:6
SubsystemWindows Client & Win Launcher

How it Works Internally​

Executes GetFS within Windows Client & Win Launcher. Coordinates interactions with GetFlag, __declspec, isDbg1, hash_value.

  • Control Flow & Execution: Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: GetFlag, __declspec, isDbg1, hash_value, return, isDbg2, rand, isDbg3.
  • External Library Dependencies: Boost C++ Libraries.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on GetFS.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


5. GetFlag​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

DWORD GetFlag(DWORD f);
PropertyValue
Return TypeDWORD
Modifiersstatic __forceinline
Source LocationWin/CheckDbg.cpp:19
SubsystemWindows Client & Win Launcher

How it Works Internally​

Executes GetFlag within Windows Client & Win Launcher.

  • Control Flow & Execution: Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on GetFlag.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


6. GetTargetFrameRate​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

int GetTargetFrameRate() const;
PropertyValue
Return Typeint
Modifiersconst
Source LocationWin/DSVideoCaptureEngine.cpp:108
SubsystemWindows Client & Win Launcher

How it Works Internally​

Executes GetTargetFrameRate within Windows Client & Win Launcher.

  • Control Flow & Execution: Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Immutable / read-only operation (const member method; does not alter object state).

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on GetTargetFrameRate.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


7. GetActualFrameRate​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

int GetActualFrameRate() const;
PropertyValue
Return Typeint
Modifiersconst
Source LocationWin/DSVideoCaptureEngine.cpp:109
SubsystemWindows Client & Win Launcher

How it Works Internally​

Executes GetActualFrameRate within Windows Client & Win Launcher.

  • Control Flow & Execution: Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Immutable / read-only operation (const member method; does not alter object state).

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on GetActualFrameRate.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


8. GetTime​

Status: 🧪 Tested  |  🌐 Cross-Platform Uniform

LONG GetTime();
PropertyValue
Return TypeLONG
Modifiersvirtual
Source LocationWin/DSVideoCaptureEngine.cpp:166
SubsystemWindows Client & Win Launcher

How it Works Internally​

Executes GetTime within Windows Client & Win Launcher. Coordinates interactions with Millisecs.

  • Control Flow & Execution: Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: Millisecs.

How it is Used in Tests​

This function is exercised in 1 test case(s):

  • PathfindingTest::PathfindingStress (App.UnitTest/PathfindingTest.cpp:48)
    • Usage Pattern: Direct Call
    • Callsite Snippet: RakNet::Time start_time = RakNet::GetTime();

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


9. CVideoStreamFilter::pushNextFrame​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

void CVideoStreamFilter::pushNextFrame(BYTE *data, int size, int cx, int cy, int bpp);
PropertyValue
Return Typevoid
ModifiersNone
Source LocationWin/DSVideoCaptureEngine.cpp:211
SubsystemWindows Client & Win Launcher

How it Works Internally​

Executes pushNextFrame within Windows Client & Win Launcher.

  • Control Flow & Execution: Direct sequential execution.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on pushNextFrame.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


10. CVideoStreamFilter::GetTargetFrameRate​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

int CVideoStreamFilter::GetTargetFrameRate() const;
PropertyValue
Return Typeint
Modifiersconst
Source LocationWin/DSVideoCaptureEngine.cpp:216
SubsystemWindows Client & Win Launcher

How it Works Internally​

Executes GetTargetFrameRate within Windows Client & Win Launcher. Coordinates interactions with return.

  • Control Flow & Execution: Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Immutable / read-only operation (const member method; does not alter object state).
  • Key Internal Calls: return.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on GetTargetFrameRate.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


11. CVideoStreamFilter::GetActualFrameRate​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

int CVideoStreamFilter::GetActualFrameRate() const;
PropertyValue
Return Typeint
Modifiersconst
Source LocationWin/DSVideoCaptureEngine.cpp:221
SubsystemWindows Client & Win Launcher

How it Works Internally​

Executes GetActualFrameRate within Windows Client & Win Launcher. Coordinates interactions with return.

  • Control Flow & Execution: Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Immutable / read-only operation (const member method; does not alter object state).
  • Key Internal Calls: return.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on GetActualFrameRate.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


12. CVideoStreamFilter::SetAudioClock​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

void CVideoStreamFilter::SetAudioClock(IAudioTime *clock);
PropertyValue
Return Typevoid
ModifiersNone
Source LocationWin/DSVideoCaptureEngine.cpp:226
SubsystemWindows Client & Win Launcher

How it Works Internally​

Executes SetAudioClock within Windows Client & Win Launcher. Coordinates interactions with return.

  • Control Flow & Execution: Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: return.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on SetAudioClock.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


13. CVideoStreamFilter::GetCaptureSize​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

void CVideoStreamFilter::GetCaptureSize(int &width, int &height);
PropertyValue
Return Typevoid
ModifiersNone
Source LocationWin/DSVideoCaptureEngine.cpp:231
SubsystemWindows Client & Win Launcher

How it Works Internally​

Executes GetCaptureSize within Windows Client & Win Launcher.

  • Control Flow & Execution: Direct sequential execution.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on GetCaptureSize.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


14. CVideoStreamFilter::GetQueueSize​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

int CVideoStreamFilter::GetQueueSize();
PropertyValue
Return Typeint
ModifiersNone
Source LocationWin/DSVideoCaptureEngine.cpp:236
SubsystemWindows Client & Win Launcher

How it Works Internally​

Executes GetQueueSize within Windows Client & Win Launcher. Coordinates interactions with return.

  • Control Flow & Execution: Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: return.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on GetQueueSize.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


15. CVideoStream::SetAudioClock​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

void CVideoStream::SetAudioClock(IAudioTime *clock);
PropertyValue
Return Typevoid
ModifiersNone
Source LocationWin/DSVideoCaptureEngine.cpp:267
SubsystemWindows Client & Win Launcher

How it Works Internally​

Executes SetAudioClock within Windows Client & Win Launcher.

  • Control Flow & Execution: Direct sequential execution.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on SetAudioClock.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


16. CVideoStream::pushNextFrame​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

void CVideoStream::pushNextFrame(BYTE *data, int size, int cx, int cy, int bpp);
PropertyValue
Return Typevoid
ModifiersNone
Source LocationWin/DSVideoCaptureEngine.cpp:272
SubsystemWindows Client & Win Launcher

How it Works Internally​

Executes pushNextFrame within Windows Client & Win Launcher. Coordinates interactions with lock, push, Set.

  • Control Flow & Execution: Direct sequential execution.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: lock, push, Set.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on pushNextFrame.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


17. CVideoStream::GetQueueSize​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

int CVideoStream::GetQueueSize();
PropertyValue
Return Typeint
ModifiersNone
Source LocationWin/DSVideoCaptureEngine.cpp:280
SubsystemWindows Client & Win Launcher

How it Works Internally​

Executes GetQueueSize within Windows Client & Win Launcher. Coordinates interactions with lock, size.

  • Control Flow & Execution: Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: lock, size.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on GetQueueSize.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


18. CVideoStream::GetCaptureSize​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

void CVideoStream::GetCaptureSize(int &width, int &height);
PropertyValue
Return Typevoid
ModifiersNone
Source LocationWin/DSVideoCaptureEngine.cpp:287
SubsystemWindows Client & Win Launcher

How it Works Internally​

Executes GetCaptureSize within Windows Client & Win Launcher.

  • Control Flow & Execution: Direct sequential execution.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on GetCaptureSize.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


19. CVideoStream::FillBuffer​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

HRESULT CVideoStream::FillBuffer(IMediaSample *pms);
PropertyValue
Return TypeHRESULT
ModifiersNone
Source LocationWin/DSVideoCaptureEngine.cpp:293
SubsystemWindows Client & Win Launcher

How it Works Internally​

Executes FillBuffer within Windows Client & Win Launcher. Coordinates interactions with CheckPointer, GetPointer, GetSize, cAutoLockShared. Employs dynamic heap allocation via c++ operator new.

  • Control Flow & Execution: Iterative loop processing, Conditional branching, Multi-case state dispatch, Explicit result return.
  • Memory Management: Dynamic heap allocation via C++ operator new; Heap memory deallocation via operator delete.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Engine invariant assertion check (RBXASSERT).
  • State Mutation: Mutates internal member state or instance properties.
  • Key Internal Calls: CheckPointer, GetPointer, GetSize, cAutoLockShared, Lock, size, Unlock, Wait, Reset, empty, front, GetAbsoluteTime.
  • External Library Dependencies: Boost C++ Libraries, OpenGL / GLES Graphics API, FMOD Audio Engine.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on FillBuffer.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


20. CVideoStream::Notify​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

STDMETHODIMP CVideoStream::Notify(IBaseFilter * pSender, Quality q);
PropertyValue
Return TypeSTDMETHODIMP
ModifiersNone
Source LocationWin/DSVideoCaptureEngine.cpp:355
SubsystemWindows Client & Win Launcher

How it Works Internally​

Notify Alter the repeat rate according to quality management messages sent from the downstream filter (often the renderer). Wind it up or down according to the flooding level - also skip forward if we are notified of Late-ness

  • Control Flow & Execution: Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on Notify.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


21. CVideoStream::GetMediaType​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

HRESULT CVideoStream::GetMediaType(int iPosition, CMediaType *pmt);
PropertyValue
Return TypeHRESULT
ModifiersNone
Source LocationWin/DSVideoCaptureEngine.cpp:359
SubsystemWindows Client & Win Launcher

How it Works Internally​

Executes GetMediaType within Windows Client & Win Launcher. Coordinates interactions with CheckPointer, cAutoLock, pStateLock, AllocFormatBuffer.

  • Control Flow & Execution: Conditional branching, Multi-case state dispatch, Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: CheckPointer, cAutoLock, pStateLock, AllocFormatBuffer, return, ZeroMemory, GetBitmapSize, SetRectEmpty, SetType, SetFormatType, SetTemporalCompression, GetBitmapSubtype.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on GetMediaType.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


22. CVideoStream::CheckMediaType​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

HRESULT CVideoStream::CheckMediaType(const CMediaType *pMediaType);
PropertyValue
Return TypeHRESULT
ModifiersNone
Source LocationWin/DSVideoCaptureEngine.cpp:411
SubsystemWindows Client & Win Launcher

How it Works Internally​

Executes CheckMediaType within Windows Client & Win Launcher. Coordinates interactions with CheckPointer, Type, IsFixedSize, Subtype.

  • Control Flow & Execution: Conditional branching, Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: CheckPointer, Type, IsFixedSize, Subtype, Format, abs.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on CheckMediaType.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


23. CVideoStream::DecideBufferSize​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

HRESULT CVideoStream::DecideBufferSize(IMemAllocator *pAlloc, ALLOCATOR_PROPERTIES *pProperties);
PropertyValue
Return TypeHRESULT
ModifiersNone
Source LocationWin/DSVideoCaptureEngine.cpp:453
SubsystemWindows Client & Win Launcher

How it Works Internally​

Executes DecideBufferSize within Windows Client & Win Launcher. Coordinates interactions with CheckPointer, cAutoLock, pStateLock, Format.

  • Control Flow & Execution: Conditional branching, Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: CheckPointer, cAutoLock, pStateLock, Format, ASSERT, succeed, SetProperties, FAILED, buffer.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on DecideBufferSize.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


24. CVideoStream::SetMediaType​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

HRESULT CVideoStream::SetMediaType(const CMediaType *pMediaType);
PropertyValue
Return TypeHRESULT
ModifiersNone
Source LocationWin/DSVideoCaptureEngine.cpp:492
SubsystemWindows Client & Win Launcher

How it Works Internally​

Executes SetMediaType within Windows Client & Win Launcher. Coordinates interactions with cAutoLock, pStateLock, SUCCEEDED, Format.

  • Control Flow & Execution: Conditional branching, Multi-case state dispatch, Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Engine invariant assertion check (RBXASSERT).
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: cAutoLock, pStateLock, SUCCEEDED, Format, RBXASSERT.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on SetMediaType.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


25. CVideoStream::OnThreadCreate​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

HRESULT CVideoStream::OnThreadCreate();
PropertyValue
Return TypeHRESULT
ModifiersNone
Source LocationWin/DSVideoCaptureEngine.cpp:525
SubsystemWindows Client & Win Launcher

How it Works Internally​

OnThreadCreate As we go active reset the stream time to zero

  • Control Flow & Execution: Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Mutates internal member state or instance properties.
  • Key Internal Calls: cAutoLockShared.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on OnThreadCreate.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


26. CAudioStreamFilter::GetExpectedFramesCount​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

int CAudioStreamFilter::GetExpectedFramesCount(int frameDelay) const;
PropertyValue
Return Typeint
Modifiersconst
Source LocationWin/DSVideoCaptureEngine.cpp:557
SubsystemWindows Client & Win Launcher

How it Works Internally​

Executes GetExpectedFramesCount within Windows Client & Win Launcher. Coordinates interactions with return.

  • Control Flow & Execution: Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Immutable / read-only operation (const member method; does not alter object state).
  • Key Internal Calls: return.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on GetExpectedFramesCount.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


27. CAudioStreamFilter::StopSoundCapture​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

void CAudioStreamFilter::StopSoundCapture();
PropertyValue
Return Typevoid
ModifiersNone
Source LocationWin/DSVideoCaptureEngine.cpp:567
SubsystemWindows Client & Win Launcher

How it Works Internally​

Executes StopSoundCapture within Windows Client & Win Launcher. Coordinates interactions with return.

  • Control Flow & Execution: Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: return.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on StopSoundCapture.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


28. CAudioStream::GetAbsoluteTime​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

LONG CAudioStream::GetAbsoluteTime();
PropertyValue
Return TypeLONG
ModifiersNone
Source LocationWin/DSVideoCaptureEngine.cpp:614
SubsystemWindows Client & Win Launcher

How it Works Internally​

Executes GetAbsoluteTime within Windows Client & Win Launcher.

  • Control Flow & Execution: Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on GetAbsoluteTime.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


29. CAudioStream::GetExpectedFramesCount​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

int CAudioStream::GetExpectedFramesCount(int frameDelay) const;
PropertyValue
Return Typeint
Modifiersconst
Source LocationWin/DSVideoCaptureEngine.cpp:619
SubsystemWindows Client & Win Launcher

How it Works Internally​

Executes GetExpectedFramesCount within Windows Client & Win Launcher. Coordinates interactions with return, Millisecs.

  • Control Flow & Execution: Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Immutable / read-only operation (const member method; does not alter object state).
  • Key Internal Calls: return, Millisecs.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on GetExpectedFramesCount.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


30. CAudioStream::StopSoundCapture​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

void CAudioStream::StopSoundCapture();
PropertyValue
Return Typevoid
ModifiersNone
Source LocationWin/DSVideoCaptureEngine.cpp:624
SubsystemWindows Client & Win Launcher

How it Works Internally​

Executes StopSoundCapture within Windows Client & Win Launcher. Coordinates interactions with setBypass, release, Set.

  • Control Flow & Execution: Conditional branching.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: setBypass, release, Set.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on StopSoundCapture.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


31. CAudioStream::audioGrabber​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

FMOD_RESULT F_CALLBACK CAudioStream::audioGrabber(FMOD_DSP_STATE *dsp_state, float *inbuffer, float *outbuffer, unsigned int length, int inchannels, int *outchannels);
PropertyValue
Return TypeFMOD_RESULT F_CALLBACK
ModifiersNone
Source LocationWin/DSVideoCaptureEngine.cpp:635
SubsystemWindows Client & Win Launcher

How it Works Internally​

Executes audioGrabber within Windows Client & Win Launcher. Coordinates interactions with getUserData, RBXASSERT, lock, push. Employs dynamic heap allocation via c++ operator new.

  • Control Flow & Execution: Iterative loop processing, Conditional branching, Explicit result return.
  • Memory Management: Dynamic heap allocation via C++ operator new.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Engine invariant assertion check (RBXASSERT).
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: getUserData, RBXASSERT, lock, push, Set.
  • External Library Dependencies: FMOD Audio Engine.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on audioGrabber.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


32. CAudioStream::FillBuffer​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

HRESULT CAudioStream::FillBuffer(IMediaSample *pms);
PropertyValue
Return TypeHRESULT
ModifiersNone
Source LocationWin/DSVideoCaptureEngine.cpp:671
SubsystemWindows Client & Win Launcher

How it Works Internally​

Executes FillBuffer within Windows Client & Win Launcher. Coordinates interactions with CheckPointer, GetPointer, FAILED, lShared. Employs heap memory deallocation via operator delete.

  • Control Flow & Execution: Conditional branching, Explicit result return.
  • Memory Management: Heap memory deallocation via operator delete.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Engine invariant assertion check (RBXASSERT).
  • State Mutation: Mutates internal member state or instance properties.
  • Key Internal Calls: CheckPointer, GetPointer, FAILED, lShared, Format, RBXASSERT, Lock, size, Unlock, Wait, Reset, empty.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on FillBuffer.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


33. CAudioStream::DecideBufferSize​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

HRESULT CAudioStream::DecideBufferSize(IMemAllocator *pIMemAlloc, ALLOCATOR_PROPERTIES *pProperties);
PropertyValue
Return TypeHRESULT
ModifiersNone
Source LocationWin/DSVideoCaptureEngine.cpp:773
SubsystemWindows Client & Win Launcher

How it Works Internally​

Executes DecideBufferSize within Windows Client & Win Launcher. Coordinates interactions with CheckPointer, Format, RBXASSERT, SetProperties.

  • Control Flow & Execution: Conditional branching, Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Engine invariant assertion check (RBXASSERT).
  • State Mutation: Mutates internal member state or instance properties.
  • Key Internal Calls: CheckPointer, Format, RBXASSERT, SetProperties, FAILED.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on DecideBufferSize.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


34. CAudioStream::SetMediaType​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

HRESULT CAudioStream::SetMediaType(const CMediaType *pMediaType);
PropertyValue
Return TypeHRESULT
ModifiersNone
Source LocationWin/DSVideoCaptureEngine.cpp:814
SubsystemWindows Client & Win Launcher

How it Works Internally​

Executes SetMediaType within Windows Client & Win Launcher. Coordinates interactions with cAutoLock, pStateLock, CheckMediaType.

  • Control Flow & Execution: Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: cAutoLock, pStateLock, CheckMediaType.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on SetMediaType.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


35. CAudioStream::CheckMediaType​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

HRESULT CAudioStream::CheckMediaType(const CMediaType *pMediaType);
PropertyValue
Return TypeHRESULT
ModifiersNone
Source LocationWin/DSVideoCaptureEngine.cpp:823
SubsystemWindows Client & Win Launcher

How it Works Internally​

Executes CheckMediaType within Windows Client & Win Launcher. Coordinates interactions with CheckPointer, lock, pStateLock, GetMediaType.

  • Control Flow & Execution: Conditional branching, Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: CheckPointer, lock, pStateLock, GetMediaType.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on CheckMediaType.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


36. CAudioStream::GetMediaType​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

HRESULT CAudioStream::GetMediaType(int iPosition, CMediaType *pmt);
PropertyValue
Return TypeHRESULT
ModifiersNone
Source LocationWin/DSVideoCaptureEngine.cpp:839
SubsystemWindows Client & Win Launcher

How it Works Internally​

Executes GetMediaType within Windows Client & Win Launcher. Coordinates interactions with CheckPointer, cAutoLock, pStateLock, AllocFormatBuffer.

  • Control Flow & Execution: Conditional branching, Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: CheckPointer, cAutoLock, pStateLock, AllocFormatBuffer, return, ZeroMemory, CreateAudioMediaType.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on GetMediaType.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


37. CAudioStream::OnThreadCreate​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

HRESULT CAudioStream::OnThreadCreate(void);
PropertyValue
Return TypeHRESULT
ModifiersNone
Source LocationWin/DSVideoCaptureEngine.cpp:869
SubsystemWindows Client & Win Launcher

How it Works Internally​

Executes OnThreadCreate within Windows Client & Win Launcher. Coordinates interactions with cAutoLockShared.

  • Control Flow & Execution: Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Mutates internal member state or instance properties.
  • Key Internal Calls: cAutoLockShared.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on OnThreadCreate.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


38. CAudioStream::Notify​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

STDMETHODIMP CAudioStream::Notify(IBaseFilter * pSender, Quality q);
PropertyValue
Return TypeSTDMETHODIMP
ModifiersNone
Source LocationWin/DSVideoCaptureEngine.cpp:876
SubsystemWindows Client & Win Launcher

How it Works Internally​

Executes Notify within Windows Client & Win Launcher.

  • Control Flow & Execution: Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on Notify.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


39. DSVideoCaptureEngine::BuildCaptureGraphNoThrow​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

HRESULT DSVideoCaptureEngine::BuildCaptureGraphNoThrow(int cx, int cy, bool forceNoAudio);
PropertyValue
Return TypeHRESULT
ModifiersNone
Source LocationWin/DSVideoCaptureEngine.cpp:915
SubsystemWindows Client & Win Launcher

How it Works Internally​

Executes BuildCaptureGraphNoThrow within Windows Client & Win Launcher. Coordinates interactions with BuildCaptureGraph, __except.

  • Control Flow & Execution: Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: BuildCaptureGraph, __except.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on BuildCaptureGraphNoThrow.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


40. DSVideoCaptureEngine::start​

Status: 🧪 Tested  |  🌐 Cross-Platform Uniform

bool DSVideoCaptureEngine::start(int cx, int cy, SoundState *s);
PropertyValue
Return Typebool
ModifiersNone
Source LocationWin/DSVideoCaptureEngine.cpp:927
SubsystemWindows Client & Win Launcher

How it Works Internally​

Executes start within Windows Client & Win Launcher. Coordinates interactions with isRunning, GetSquareSizes, enabledFunction, getSampleRateFunction. Employs dynamic heap allocation via c++ operator new.

  • Control Flow & Execution: Conditional branching, Explicit result return.
  • Memory Management: Dynamic heap allocation via C++ operator new.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Engine invariant assertion check (RBXASSERT).
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: isRunning, GetSquareSizes, enabledFunction, getSampleRateFunction, BuildCaptureGraphNoThrow, FAILED, ReportStatisticWithMessage, GetBaseURL, format, DestroyCaptureGgaph, BuildCaptureGraph, RBXASSERT.

How it is Used in Tests​

This function is exercised in 2 test case(s):

  • RaycastTest::RayInvovlesThreeChunks (App.UnitTest/RaycastTest.cpp:461)
    • Usage Pattern: Direct Call
    • Callsite Snippet: Vector3 start(0, 15, 15);
  • RaycastTest::TerrainLoopRepro (App.UnitTest/RaycastTest.cpp:486)
    • Usage Pattern: Direct Call
    • Callsite Snippet: Vector3 start(-5.8e-22f, 253.4f, -.5f);

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


41. DSVideoCaptureEngine::stop​

Status: 🧪 Tested  |  ⚠️ Platform Divergent

bool DSVideoCaptureEngine::stop();
PropertyValue
Return Typebool
ModifiersNone
Source LocationWin/DSVideoCaptureEngine.cpp:971
SubsystemWindows Client & Win Launcher

How it Works Internally​

Executes stop within Windows Client & Win Launcher. Coordinates interactions with isRunning, FASTLOG1, RBXASSERT, StopSoundCapture. Employs heap memory deallocation via operator delete.

  • Control Flow & Execution: Conditional branching, Explicit result return.
  • Memory Management: Heap memory deallocation via operator delete.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Engine invariant assertion check (RBXASSERT).
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: isRunning, FASTLOG1, RBXASSERT, StopSoundCapture, Stop, FAILED, Sleep, SUCCEEDED, singleton, printf, DestroyCaptureGgaph.
  • External Library Dependencies: OpenGL / GLES Graphics API.

How it is Used in Tests​

This function is exercised in 1 test case(s):

  • SoundEffectTests::DistortionDSPUpdatesAndDetach (App.UnitTest/SoundEffectTest.cpp:53)
    • Usage Pattern: Direct Call
    • Assertions Checked: BOOST_REQUIRE_EQUAL(FMOD::System_Create(&system), FMOD_OK), BOOST_REQUIRE_EQUAL(system->setOutput(FMOD_OUTPUTTYPE_NOSOUND), FMOD_OK)
    • Callsite Snippet: channel->stop();

Behavioral Differences Across Code Files​

Divergence Analysis: Alternative platform-specific implementations exist in: WindowsClient/RenderJob.cpp, XboxClient/renderJob.cpp.

  • Alternative Implementation Files: WindowsClient/RenderJob.cpp, XboxClient/renderJob.cpp

42. DSVideoCaptureEngine::setVideoQuality​

Status: ⚪ Untested in Suites  |  ⚠️ Platform Divergent

void DSVideoCaptureEngine::setVideoQuality(int vq);
PropertyValue
Return Typevoid
ModifiersNone
Source LocationWin/DSVideoCaptureEngine.cpp:1007
SubsystemWindows Client & Win Launcher

How it Works Internally​

Declaration or inline method for setVideoQuality.

  • Control Flow & Execution: Linear execution flow.
  • Memory Management: Standard stack allocation.
  • Concurrency & Thread Safety: Unsynchronized / single-threaded context.
  • Error Handling & Invariants: Standard return value verification.
  • State Mutation: Stateless or local modification.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on setVideoQuality.

Behavioral Differences Across Code Files​

Divergence Analysis: Alternative platform-specific implementations exist in: Win/VideoControl.cpp.

  • Alternative Implementation Files: Win/VideoControl.cpp

43. DSVideoCaptureEngine::isRunning​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

bool DSVideoCaptureEngine::isRunning();
PropertyValue
Return Typebool
ModifiersNone
Source LocationWin/DSVideoCaptureEngine.cpp:1010
SubsystemWindows Client & Win Launcher

How it Works Internally​

Executes isRunning within Windows Client & Win Launcher. Coordinates interactions with GetState, RBXASSERT, SUCCEEDED, FAILED.

  • Control Flow & Execution: Conditional branching, Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Engine invariant assertion check (RBXASSERT).
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: GetState, RBXASSERT, SUCCEEDED, FAILED, FASTLOG, return.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on isRunning.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


44. DSVideoCaptureEngine::GetSquareSizes​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

void DSVideoCaptureEngine::GetSquareSizes(int cx, int cy, int &ncx, int &ncy);
PropertyValue
Return Typevoid
ModifiersNone
Source LocationWin/DSVideoCaptureEngine.cpp:1029
SubsystemWindows Client & Win Launcher

How it Works Internally​

Executes GetSquareSizes within Windows Client & Win Launcher.

  • Control Flow & Execution: Conditional branching.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on GetSquareSizes.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


45. doNothingCallbackContinuation​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

void doNothingCallbackContinuation();
PropertyValue
Return Typevoid
Modifiersstatic
Source LocationWin/DSVideoCaptureEngine.cpp:1049
SubsystemWindows Client & Win Launcher

How it Works Internally​

Declaration or inline method for doNothingCallbackContinuation.

  • Control Flow & Execution: Linear execution flow.
  • Memory Management: Standard stack allocation.
  • Concurrency & Thread Safety: Unsynchronized / single-threaded context.
  • Error Handling & Invariants: Standard return value verification.
  • State Mutation: Stateless or local modification.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on doNothingCallbackContinuation.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


46. cancelRecording​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

void cancelRecording(DataModel* dm, Verb* cancelAction);
PropertyValue
Return Typevoid
Modifiersstatic
Source LocationWin/DSVideoCaptureEngine.cpp:1051
SubsystemWindows Client & Win Launcher

How it Works Internally​

Executes cancelRecording within Windows Client & Win Launcher. Coordinates interactions with empty, notificationCallback, bind, doIt.

  • Control Flow & Execution: Conditional branching.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: empty, notificationCallback, bind, doIt.
  • External Library Dependencies: Boost C++ Libraries.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on cancelRecording.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


47. DSVideoCaptureEngine::pushNextFrame​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

void DSVideoCaptureEngine::pushNextFrame(void* device, Verb *cancelAction);
PropertyValue
Return Typevoid
ModifiersNone
Source LocationWin/DSVideoCaptureEngine.cpp:1064
SubsystemWindows Client & Win Launcher

How it Works Internally​

Executes pushNextFrame within Windows Client & Win Launcher. Coordinates interactions with FASTLOG, RBXASSERT, isRunning, GetAbsoluteTime. Employs dynamic heap allocation via c++ operator new.

  • Control Flow & Execution: Iterative loop processing, Conditional branching, Explicit result return.
  • Memory Management: Dynamic heap allocation via C++ operator new; Heap memory deallocation via operator delete.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Engine invariant assertion check (RBXASSERT).
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: FASTLOG, RBXASSERT, isRunning, GetAbsoluteTime, doIt, getMainFramebuffer, getWidth, getHeight, GetSquareSizes, GetCaptureSize, getContainer, submitTask.
  • External Library Dependencies: Boost C++ Libraries.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on pushNextFrame.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


48. DSVideoCaptureEngine::GetTime​

Status: 🧪 Tested  |  🌐 Cross-Platform Uniform

LONG DSVideoCaptureEngine::GetTime();
PropertyValue
Return TypeLONG
ModifiersNone
Source LocationWin/DSVideoCaptureEngine.cpp:1155
SubsystemWindows Client & Win Launcher

How it Works Internally​

Executes GetTime within Windows Client & Win Launcher. Coordinates interactions with GetAudioTime.

  • Control Flow & Execution: Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: GetAudioTime.

How it is Used in Tests​

This function is exercised in 1 test case(s):

  • PathfindingTest::PathfindingStress (App.UnitTest/PathfindingTest.cpp:48)
    • Usage Pattern: Direct Call
    • Callsite Snippet: RakNet::Time start_time = RakNet::GetTime();

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


49. DSVideoCaptureEngine::GetAbsoluteTime​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

LONG DSVideoCaptureEngine::GetAbsoluteTime();
PropertyValue
Return TypeLONG
ModifiersNone
Source LocationWin/DSVideoCaptureEngine.cpp:1160
SubsystemWindows Client & Win Launcher

How it Works Internally​

Executes GetAbsoluteTime within Windows Client & Win Launcher. Coordinates interactions with timeGetTime.

  • Control Flow & Execution: Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: timeGetTime.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on GetAbsoluteTime.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


50. DSVideoCaptureEngine::BuildCaptureGraph​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

HRESULT DSVideoCaptureEngine::BuildCaptureGraph(int cx, int cy, bool forceNoAudio);
PropertyValue
Return TypeHRESULT
ModifiersNone
Source LocationWin/DSVideoCaptureEngine.cpp:1175
SubsystemWindows Client & Win Launcher

How it Works Internally​

Executes BuildCaptureGraph within Windows Client & Win Launcher. Coordinates interactions with GetVersionEx, ERROR_ON_FAIL, CoCreateInstance, QueryInterface. Employs dynamic heap allocation via c++ operator new.

  • Control Flow & Execution: Conditional branching, Explicit result return.
  • Memory Management: Dynamic heap allocation via C++ operator new.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: GetVersionEx, ERROR_ON_FAIL, CoCreateInstance, QueryInterface, CVideoStreamFilter, FAILED, AddFilter, GenerateFileName, SetFileName, WMCreateProfileManager, enabledFunction, LoadProfileByData.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on BuildCaptureGraph.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


51. DSVideoCaptureEngine::DestroyCaptureGgaph​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

void DSVideoCaptureEngine::DestroyCaptureGgaph();
PropertyValue
Return Typevoid
ModifiersNone
Source LocationWin/DSVideoCaptureEngine.cpp:1266
SubsystemWindows Client & Win Launcher

How it Works Internally​

Executes DestroyCaptureGgaph within Windows Client & Win Launcher. Coordinates interactions with SAFE_RELEASE.

  • Control Flow & Execution: Direct sequential execution.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: SAFE_RELEASE.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on DestroyCaptureGgaph.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


52. DSVideoCaptureEngine::GenerateFileName​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

int DSVideoCaptureEngine::GenerateFileName(LPWSTR fileName);
PropertyValue
Return Typeint
ModifiersNone
Source LocationWin/DSVideoCaptureEngine.cpp:1276
SubsystemWindows Client & Win Launcher

How it Works Internally​

Executes GenerateFileName within Windows Client & Win Launcher. Coordinates interactions with GetLocalTime, getUserDirectory, _snwprintf_s, wcsncpy_s.

  • Control Flow & Execution: Iterative loop processing, Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: GetLocalTime, getUserDirectory, _snwprintf_s, wcsncpy_s, native, c_str, clear, push_back.
  • External Library Dependencies: Boost C++ Libraries.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on GenerateFileName.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


53. getFileName​

Status: ⚪ Untested in Suites  |  ⚠️ Platform Divergent

std::string & getFileName();
PropertyValue
Return Typestd::string &
Modifiersvirtual
Source LocationWin/DSVideoCaptureEngine.h:41
SubsystemWindows Client & Win Launcher

How it Works Internally​

Executes getFileName within Windows Client & Win Launcher.

  • Control Flow & Execution: Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on getFileName.

Behavioral Differences Across Code Files​

Divergence Analysis: Alternative platform-specific implementations exist in: WindowsClient/RobloxGoldenHashPatcher/main.cpp.

  • Alternative Implementation Files: WindowsClient/RobloxGoldenHashPatcher/main.cpp

54. DumpErrorUploader::InitCrashEvent​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

void DumpErrorUploader::InitCrashEvent(const std::string& url, const std::string& crashEventFileName);
PropertyValue
Return Typevoid
ModifiersNone
Source LocationWin/DumpErrorUploader.cpp:35
SubsystemWindows Client & Win Launcher

How it Works Internally​

Executes InitCrashEvent within Windows Client & Win Launcher. Coordinates interactions with urlEncode, current, writeEntry, format. Employs dynamic heap allocation via c++ operator new.

  • Control Flow & Execution: Conditional branching.
  • Memory Management: Dynamic heap allocation via C++ operator new.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: urlEncode, current, writeEntry, format, c_str, reset, Http, reserve.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on InitCrashEvent.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


55. DumpErrorUploader::Upload​

Status: ⚪ Untested in Suites  |  ⚠️ Platform Divergent

void DumpErrorUploader::Upload(const std::string& url);
PropertyValue
Return Typevoid
ModifiersNone
Source LocationWin/DumpErrorUploader.cpp:47
SubsystemWindows Client & Win Launcher

How it Works Internally​

Executes Upload within Windows Client & Win Launcher. Coordinates interactions with CreateMutex, TEXT, singleton, printf.

  • Control Flow & Execution: Iterative loop processing, Conditional branching, Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: RAII mutex lock acquisition (scoped_lock); Thread mutual exclusion locking (boost::mutex).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: CreateMutex, TEXT, singleton, printf, GetLastError, getMainLogManager, gatherCrashLogs, lock, size, push, wake, run.
  • External Library Dependencies: Boost C++ Libraries, OpenGL / GLES Graphics API.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on Upload.

Behavioral Differences Across Code Files​

Divergence Analysis: Alternative platform-specific implementations exist in: Win/ScriptErrorUploader.cpp.

  • Alternative Implementation Files: Win/ScriptErrorUploader.cpp

56. LogFilter​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

int LogFilter(unsigned int code, struct _EXCEPTION_POINTERS *ep);
PropertyValue
Return Typeint
ModifiersNone
Source LocationWin/DumpErrorUploader.cpp:91
SubsystemWindows Client & Win Launcher

How it Works Internally​

Executes LogFilter within Windows Client & Win Launcher. Coordinates interactions with singleton, printf.

  • Control Flow & Execution: Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: singleton, printf.
  • External Library Dependencies: OpenGL / GLES Graphics API.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on LogFilter.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


57. DumpErrorUploader::UploadCrashEventFile​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

void DumpErrorUploader::UploadCrashEventFile(struct _EXCEPTION_POINTERS *excInfo);
PropertyValue
Return Typevoid
ModifiersNone
Source LocationWin/DumpErrorUploader.cpp:97
SubsystemWindows Client & Win Launcher

How it Works Internally​

Executes UploadCrashEventFile within Windows Client & Win Launcher. Coordinates interactions with singleton, printf, post, c_str.

  • Control Flow & Execution: Iterative loop processing, Conditional branching.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Exception handling block (try/catch recovery).
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: singleton, printf, post, c_str, reportCounter, addPoint, nowFastSec, usedMemoryBytes, getMainLogManager, getGameState, str, getSessionId.
  • External Library Dependencies: OpenGL / GLES Graphics API, InfluxDB Metrics Ingestion Client.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on UploadCrashEventFile.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


58. DumpErrorUploader::run​

Status: 🧪 Tested  |  ⚠️ Platform Divergent

RBX::worker_thread::work_result DumpErrorUploader::run(shared_ptr<data> _data);
PropertyValue
Return TypeRBX::worker_thread::work_result
ModifiersNone
Source LocationWin/DumpErrorUploader.cpp:151
SubsystemWindows Client & Win Launcher

How it Works Internally​

Executes run within Windows Client & Win Launcher. Coordinates interactions with lock, empty, CloseHandle, reportCounter.

  • Control Flow & Execution: Conditional branching, Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: RAII mutex lock acquisition (scoped_lock); Thread mutual exclusion locking (boost::mutex).
  • Error Handling & Invariants: Exception handling block (try/catch recovery).
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: lock, empty, CloseHandle, reportCounter, front, printf, c_str, substr, size, find, urlEncode, data.
  • External Library Dependencies: Boost C++ Libraries, OpenGL / GLES Graphics API.

How it is Used in Tests​

This function is exercised in 30 test case(s):

  • Instance::WaitForChildReturnsImmediatelyIfChildPresent (App.UnitTest/Instance.cpp:264)
    • Usage Pattern: Direct Call
    • Assertions Checked: BOOST_CHECK_EQUAL(part-&gt;getName(), "Renamed")
    • Callsite Snippet: ServiceProvider::create&lt;RunService&gt;(&dm)-&gt;run();
  • Instance::WaitForSameChildAfterInitialWaitForChild (App.UnitTest/Instance.cpp:289)
    • Usage Pattern: Direct Call
    • Assertions Checked: BOOST_CHECK_EQUAL(part-&gt;getName(), "Renamed")
    • Callsite Snippet: ServiceProvider::create&lt;RunService&gt;(&dm)-&gt;run();
  • Instance::TwoScriptsWaitingForSameChild (App.UnitTest/Instance.cpp:314)
    • Usage Pattern: Direct Call
    • Assertions Checked: BOOST_CHECK(dm-&gt;getWorkspace()-&gt;findFirstChildByName("Alice") != NULL), BOOST_CHECK(dm-&gt;getWorkspace()-&gt;findFirstChildByName("Bob") != NULL)
    • Callsite Snippet: ServiceProvider::create&lt;RunService&gt;(&dm)-&gt;run();
  • Instance::TwoScriptsWaitingForSameChildRenameOnResume (App.UnitTest/Instance.cpp:356)
    • Usage Pattern: Direct Call
    • Assertions Checked: BOOST_CHECK_EQUAL("PartBx", part-&gt;getName()), BOOST_CHECK_EQUAL("PartA", part2-&gt;getName())
    • Callsite Snippet: ServiceProvider::create&lt;RunService&gt;(&dm)-&gt;run();

Behavioral Differences Across Code Files​

Divergence Analysis: Alternative platform-specific implementations exist in: Win/ScriptErrorUploader.cpp.

  • Alternative Implementation Files: Win/ScriptErrorUploader.cpp

59. ErrorUploader::MoveRelative​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

std::string ErrorUploader::MoveRelative(LPCTSTR fileName, std::string path);
PropertyValue
Return Typestd::string
ModifiersNone
Source LocationWin/ErrorUploader.cpp:28
SubsystemWindows Client & Win Launcher

How it Works Internally​

Executes MoveRelative within Windows Client & Win Launcher. Coordinates interactions with RemoveFileSpec, Append, c_str, FileExists.

  • Control Flow & Execution: Conditional branching, Explicit result return.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: Unsynchronized execution (caller must ensure thread-safety if shared).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: RemoveFileSpec, Append, c_str, FileExists, _mkdir, StripPath, MoveFile, DeleteFile, return.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on MoveRelative.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


60. Cancel​

Status: ⚪ Untested in Suites  |  🌐 Cross-Platform Uniform

void Cancel();
PropertyValue
Return Typevoid
ModifiersNone
Source LocationWin/ErrorUploader.h:43
SubsystemWindows Client & Win Launcher

How it Works Internally​

Executes Cancel within Windows Client & Win Launcher. Coordinates interactions with lock, empty, pop.

  • Control Flow & Execution: Iterative loop processing.
  • Memory Management: Stack-based automatic variable allocation.
  • Concurrency & Thread Safety: RAII mutex lock acquisition (scoped_lock); Thread mutual exclusion locking (boost::mutex).
  • Error Handling & Invariants: Relies on standard return codes and caller validation.
  • State Mutation: Pure computational logic or modifies passed-in parameters/references.
  • Key Internal Calls: lock, empty, pop.
  • External Library Dependencies: Boost C++ Libraries.

How it is Used in Tests​

No dedicated unit test case directly exercises this function by name.

Verification Note

This function is invoked indirectly through higher-level simulation or integration workloads. To add direct test coverage, introduce a test case in App.UnitTest or Base.UnitTest asserting state changes on Cancel.

Behavioral Differences Across Code Files​

This function maintains identical behavior across all target platforms (_WIN32, macOS, iOS, Android, and Xbox Durango). It compiles into the same binary instructions without conditional preprocessor branching.


Additional Functions

There are 439 additional internal and inline functions in this subsystem. All functions are indexed and cross-referenced in the Complete Function Catalog.