summaryrefslogtreecommitdiff
path: root/leak-suppress.txt
diff options
context:
space:
mode:
authorJan-Marek Glogowski <glogow@fbihome.de>2018-08-24 09:14:47 +0200
committerChristian Lohmaier <lohmaier+LibreOffice@googlemail.com>2018-10-03 15:48:25 +0200
commitd546859719a7f0f6bb19a80a811c5e7724b25f3d (patch)
treea0c4b883678731e55fb11768211f13662b2c316e /leak-suppress.txt
parent316447dd0284d79516cc313636e5857f542d6417 (diff)
tdf#118786 WIN just assert in Yield
This reminds me - again - that Jenkins doesn't run make check. It turns out InSendMessage() also returns true, if you process a nested SendMessage in the same thread. Therefore we have to remove the SalComWndProc assert and just keep the one in the Yield call. Why? Because there seem to be no way to get the information ReplyMessage has access to, so we could detect the caller / origin of the send message and implement proper nested call checks. The alternative would be to change all call sites of SendMessage to: if ( !pSalData->mpInstance->IsMainThread() ) SendMessage(...) else SalComWndProc(...) which is the same SendMessage already does. Change-Id: I991d68a64952dc5d47ba51edd8635c9e8c46614c Reviewed-on: https://gerrit.libreoffice.org/59538 Tested-by: Jenkins Reviewed-by: Stephan Bergmann <sbergman@redhat.com> (cherry picked from commit bf0a63dc93a746a008fb1656457c77de8df693ba) Reviewed-on: https://gerrit.libreoffice.org/59565 (cherry picked from commit a42c65176f2791cf5e48578a8898bf03185adc89) Reviewed-on: https://gerrit.libreoffice.org/60726 Reviewed-by: Michael Stahl <Michael.Stahl@cib.de>
Diffstat (limited to 'leak-suppress.txt')
0 files changed, 0 insertions, 0 deletions