strepsirrhini/office-gobmx
9
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

vcl: use WT_EXECUTEINTIMERTHREAD for Timer Queue

Browse source 
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
This commit is contained in:
Michael Stahl 2014-09-29 17:25:54 +02:00
parent 0597f3bb6b
commit 09196ca6ca
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
vcl/win/source/app/saltimer.cxx
View file

@ -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;
}