diff options
| author | Michael Stahl <mstahl@redhat.com> | 2014-09-29 17:25:54 +0200 |
|---|---|---|
| committer | Michael Stahl <mstahl@redhat.com> | 2014-09-29 17:37:27 +0200 |
| commit | 09196ca6ca9347a214ca4e73d02eda0eb6385c29 (patch) | |
| tree | e70f199adea90ce6e80615d9ea9fd9fcc4eb6ab3 | |
| parent | 0597f3bb6b6066255b0ce50ea98d2dd7e2c6708b (diff) | |
vcl: use WT_EXECUTEINTIMERTHREAD for Timer Queue
Currently the timer callback is running on a separate thread, but that
is unnecessary since it just does a PostMessage().
Every thread stack stack mysteriously eats 10M of VM apparently despite
dumpbin -headers soffice.bin:
"989680 size of stack reserve, 1000 size of stack commit"
Change-Id: I6eac3f6fa45939cd5dbb3dfbec61f9a504bdaa8b
| -rw-r--r-- | vcl/win/source/app/saltimer.cxx | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/vcl/win/source/app/saltimer.cxx b/vcl/win/source/app/saltimer.cxx index e1ce31e7be76..9b545a121a37 100644 --- a/vcl/win/source/app/saltimer.cxx +++ b/vcl/win/source/app/saltimer.cxx @@ -58,7 +58,7 @@ void ImplSalStartTimer( sal_uLong nMS, bool bMutex ) if (pSalData->mnTimerId) ChangeTimerQueueTimer(NULL, pSalData->mnTimerId, nMS, nMS); else - CreateTimerQueueTimer(&pSalData->mnTimerId, NULL, SalTimerProc, NULL, nMS, nMS, WT_EXECUTEDEFAULT); + CreateTimerQueueTimer(&pSalData->mnTimerId, NULL, SalTimerProc, NULL, nMS, nMS, WT_EXECUTEINTIMERTHREAD); pSalData->mnNextTimerTime = pSalData->mnLastEventTime + nMS; } |