WOL client stuck!

[Maihem]

Important information for combat log uploaders

It has come to our attention that the WOL client often gets stuck while uploading a report after the 5.2 patch. After looking into the issue, it turns out that the 5.2 combat log changes cause the client to use much more memory than before. This can result in it running out of memory and getting "stuck" while uploading.

We are working on updating the client to more efficiently handle the new combat log format. This requires us to change the way the combat log is parsed and compressed for uploading. In turn, this requires changes to how our servers read the uploaded data. Due to the complexity of these changes, this is taking a little longer than we'd like. We hope to have a patch ready for you by tonight.

[Maihem]

Oops, forgot to post an update here. The WOL client has been updated to more efficiently handle the new fields.

At the time of writing, v5203 is the latest client version. This version is shown in the Help > About dialog since v5202, like this: http://snag.gy/ujuq9.jpg

If your client is not showing a v520X version number or shows v5202, you can force Java WS to update by clearing the JWS cache: viewtopic.php?p=9199#p9199