google / google/filament

Question about possible delay

Open
#9,346 7 comments 0 reactions 1 assignee Claimed by @pixelflinger View on GitHub
Dominant language
C++
Stars
20.5k
Forks
2.3k
Avg merge
2d 14h
Merged PRs (30d)
83

Description

Hi, we encountered a deadlock/severe delay. the stack is

__psynch_cvwait (in libsystem_kernel.dylib) + 8
_pthread_cond_wait (in libsystem_pthread.dylib) + 984
std::__1::condition_variable::wait(std::__1::unique_lock&) (in libc++.1.dylib) + 32
filament::FFence::FenceSignal::wait(unsigned long long)
filament::FFence::waitAndDestroy(filament::FFence*, filament::Fence::Mode)
filament::FRenderer::terminate(filament::FEngine&)
filament::FEngine::destroy(filament::FRenderer const*)

is there any possibility that the below condition is also waiting, so that the new created Fence would never signal. Besides, we did not call Engine::setPaused.
https://github.com/google/filament/blob/8d6e8b8b3cc741bfa9bcf01174208cc7199cb694/filament/backend/src/CommandBufferQueue.cpp#L151

Any other possibility of this wait?

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.