Unreleased Resource: Synchronization
Sneha0523 opened this issue · comments
usr/local/share/agentWork/app/App_iOS-2/Pods/FirebaseCrashlytics/Crashlytics/Crashlytics/Handlers/FIRCLSMachException.c : 109
The function FIRCLSMachExceptionThreadStart() in FIRCLSMachException.c fails to release a lock it acquires on line 109, which might lead to deadlock.The program fails to release a lock it holds, which might lead to deadlock.
Explanation -
The program can potentially fail to release a system resource.
In this case, there are program paths on which the resource allocated in FIRCLSMachException.c on line 109 is not always released.
Resource leaks have at least two common causes:
- Error conditions and other exceptional circumstances.
- Confusion over which part of the program is responsible for releasing the resource.
Most unreleased resource issues result in general software reliability problems. However, if an attacker can intentionally trigger a resource leak, the attacker may be able to launch a denial of service by depleting the resource pool.
