-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Possible race condition between Batcher and BatchTranslator #41
Comments
Fresh SIGSEGV
|
Through inheritance, a non-threaded and multithreaded Service are created, both derived of the same ServiceBase class which holds the common elements. In preparation to solve SIGSEGV in #41. First inspections gave aborts in thread part, and repeated SIGSEGV's in lock-policy's of shared_pointers even in non-threaded paths. Solving this first, to avoid ifdef or tricky paths. The non-threaded implementation is not included in WASM builds at all, by separating out the single-threaded logic. DRY is achieved through inheritance and operator overloading.
Unable to reproduce since thread adjustments, marking as closed. |
Sus on |
The presently existing bergamot-translator/src/translator/batcher.cpp Lines 33 to 59 in ad30829
The following code in jp/translate-perftest has been running for about 3 hours now without segfault. It takes batch address from outside and tries to bergamot-translator/src/translator/batcher.cpp Lines 61 to 119 in ad30829
If such unexpected batches are created, this is what is possibly leading segfaults in certain WNGT20 runs as well. |
We no longer have pcqueue, so this shouldn't be happening again. |
SIGSEGV: gdb backtrace
bergamot-translator/src/translator/request.cpp
Line 39 in c2b1c6e
bergamot-translator/src/translator/request.cpp
Line 77 in c2b1c6e
bergamot-translator/src/translator/batch.cpp
Line 24 in c2b1c6e
bergamot-translator/src/translator/batch_translator.cpp
Line 96 in c2b1c6e
bergamot-translator/src/translator/batch_translator.cpp
Line 109 in c2b1c6e
Something amiss with a shared_ptr and copy/move. Unsure what is happening, opening issue to keep track.
The text was updated successfully, but these errors were encountered: