http://bugs.winehq.org/show_bug.cgi?id=24044
Sergiy Zuban s.zuban@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |s.zuban@gmail.com
--- Comment #13 from Sergiy Zuban s.zuban@gmail.com 2011-02-22 03:41:29 CST --- (In reply to comment #11)
And BTW this problem mostly concerns only a custom plugin by SSS: http://sss.chaoslab.ru:81/tracker/icqjplus/
I've now reverted to a default ICQ plugin and CPU usage has vastly improved (was ~8%, now 2%).
I used miranda with ubuntu+wine for more than 3 years and CPU load wasn't a big problem for me. But I've just migrated from ext3 to ext4 and noticed that miranda cause continuous hard disk accesses (HDD led is always ON). I worry that my HDD will die in near future with such activity.
In WINEDEBUG=trace+all log (attached) I see continuous KERNEL32.FlushViewOfFile calls when miranda is idle. Could someone take a look on the log and confirm HDD activity caused by miranda itself but not wine?
I'm using the latest miranda 0.9.16 with standard plugins. Per what I see core of the problem not only in ICQ plugin - jabber cause the same activity. I believe problem in dbx_mmap.dll driver. In any case i'm going to file a but to miranda, but anyway I can't figure out why ext4 cause such problems. Could this be related to the way how Wine maps KERNEL32.FlushViewOfFile calls? I've tried different mounting options in fstab, even commit=10 option which per my understanding should avoid so frequent flushing to disk - all attempts with no luck.