Interface frequently becoming unresponsive - Windows 8.1

[q009]

It happens randomly, but very frequently. Mostly after the client has been running for a few hours or so.
The interface simply stops responding for a few seconds.
It makes chatting a total pain, especially whilst typing a message.
The CPU usage didn't seem to jump in the task manager,
so I'm not sure what's happening under the hood.
Using Windows 8.1 x64 build, version 2.10.2
Also happened on older versions

Update:
I've got the call stack when the interface stopped responding http://pastebin.com/Wk6ZbqqJ
and it turns out it happens whenever it tries to write the logs.
My whole log folder had compression enabled so I imagine that's what's been causing the whole thing.
I disabled it for now and it seems like it has fixed the problem.

Update 2:
Scratch that. No, it has not fixed the problem.

[xnite]

Hello @q009 I am also running Windows 8.1 x64 w/ v2.10.2, but I'm not experiencing this problem at all. My logging is enabled, but I exclusively log stuff by using chanopts. A bit of a pain considering #1134 though, but maybe worth a shot for a work-around if logging is causing you so many issues?

[TingPing]

He has fairly large log files (100MB) on a slow drive (5400rpm) with a lot of channels (~70?). I asked him to try changing the mask for smaller files but I don't remember a response.

[xnite]

@TingPing am I the only one that changes the default log mask to something like Z:\irc-logs%n%Y%m%d%c.log (just a personal preference, but I find the folder by date schema to be more practical)? At this point it sounds more like an issue with the computer than an issue with the application.
Again I do not experience this problem, but as for my setup the Z drive is my FreeNAS (FreeBSD based NAS device) which has 2x7200RPM Seagate Barracuda drives in a RAID 1 array. I have a full Gigabit network, but can't be too certain the actual network/disk overhead when writing files, typically it's going to be slower (and possibly more bottlenecked depending on what I'm doing) than when writing to local disk though (I would imagine) I do not believe that this is a standard or practical setup, maybe it's possible that because I'm not writing to my local disk I'm not experiencing issues? I honestly can't remember the last time I stored logs to the local disk as oppose to a network share but I simply do not remember this ever having been a problem for me.

@q009 just a thought here, but maybe you could try breaking down your log files to be smaller in size, such as a format similar to mine, or log less channels as I suggested above and see if any of that helps you for now.

[TingPing]

@xnite I think the default log mask is pretty bad and I'll maybe change it before release to something like that. If he proves that the file size is his issue there is not much hexchat can do about this other than make logging async.

[q009]

As @TingPing suggested, changing the log mask to split the files more often worked.
Cheers