Syylk wrote: > Roger, boss. > > I feared your answer, but it was the reason for this thread - whether I should start a regression and then a complete bug report, or if it was just my imagination playing tricks. > > Going to work on it, then. > > Thanks for everything. I'm sorry if I sounded negative. If you started having this problem in the last release or two (as you said yourself) this is something needs to be fixed ASAP before the code freeze (in less then a month). However only you have reported this problem so far. And the next best thing you can do (after fixing the problem yourself <g>) is to find the change that caused the problem for you. So developer who made that change can fix it while the memory is still fresh. If we wait for few more releases for more people to confirm the problem it would be too late and this issue might be present in wine-1.0.0
