I am having the same problem. The “froze” issue is resolved when I press another key when looting or channeling.
MacOS, top of the line 2017 MBP. I am also on ATT’s internet.
I’m thinking of downloading Windows and seeing if it works…
Downloaded Windows and booted via BootCamp. All channeling lag has resolved.
Blizzard is doing their best to ignore the issue.
It is not something a player can fix, either they need to check their client more closely or determine if any of their routers are treating packets from non windows machines differently; something they did long ago and fixed.
Seriously, 100+ FPS when not set to sync, no change in latency (35-36), even chat chokes. nothing else on the machine is affected, only your client; I tried it even with and without multiple twitch streams open
Windowed/Window mode, no effect
Sync Refresh, no effect
Resolution, no effect
1 to 10 graphics setting, no effect
reset UI, no effect
no addons, no effect
run using microsoft windows, works perfectly.
1 Like
Appreciate all the information provided so far, everyone! It’s odd that this isn’t happening in Windows or Bootcamp for those who have tested this so far. No new updates yet since we’re still gathering information, but the details provided so far has been helpful!
Your patience is appreciated since this is impacting your gameplay. Hopefully, we’ll have a workaround or fix here soon 
We’ll continue to update when more information is available.
1 Like
Oh, the joys of experiments.
Find the world of warcraft app in the classic folder, CMD-I
Set it to open in LOW RESOLUTION
edit : nope, problem resurfaced… was better for a bit but …
oh I give up for now
Update. It has resumed on Bootcamp. It was fine all day yesterday, but it’s back.
Sigh.
Edit: I do have ATT as well as ISP.
Edit: I reset the router and it is now back to normal. Let’s see how long this lasts…
So, I guess Blizzard hasn’t paid enough tribute to the almighty American monopoly AT&T this year? 
I logged on to my AT&T account and ran a network diagnostic. It told me my network was working. I downloaded and played Guild Wars 2 and it didn’t have any lag. (I really didn’t enjoy playing that game, but I was curious.)
Basically, my mage is unplayable. The longer the casting time, the harder it is to “time” the A or D key to break the freeze.
Yesterday and today (just now), the game froze up completely. The music played, but no movement for several minutes. I had to Force Quit … curiously, though, in the Force Quit window, it did NOT show WoW as “Not responding”. Just thought I’d update you with what’s happening now.
Thanks for working on this! I’ll try to keep putting up with it on my hunter until you guys find a fix.
Thank you all for trying so many different things and reporting it here! I compiled a list of what’s been reported thus far, like resetting the UI, adjusting resolution/window or bootcamp helping for a bit. 3 reported iMac/iMacPro and 1 report of this happening on MBP. The channeling issue seems to always point back to possibly a connection issue or maybe some issues related to the resolution/UI.
To help with what we’ve gathered so far, could the following be provided?
- Mac Model:
- Router/modem model.
- Pathping & Traceroute test.
If it gives you any trouble with the links, place the connection tests between two ~~~ like so should work. You can also place the URLs between two ` (~ key).
~~~~
Connection Test
~~~~
Thanks everyone for being so proactive and patient with this! It’s frustrating with it being so persistent and going on a long while now.
1 Like
I think I’ve answered all this in several posts above, but I’ll put it all together here.
I have an iMac Pro, Processor 3.2 GHz Intel Xeon W, Memory 64GB 2666 MHz DDR4, Graphics Radeon Pro Vega 64 16GB.
I have the AT&T Uverse Wireless Modem and WAP. There’s no specific name on those items, but there’s a number on the front of the modem: 5268AC. I also use a Netgear extender across the house. I tried turning it off, but there was no change from above.
Here’s a fresh new pathping and traceroute. Hope all this helps!
1 homeportal (192.168.1.254) 21.590 ms 4.408 ms 4.362 ms 4.507 ms 4.421 ms 4.566 ms * 34.384 ms 5.040 ms 4.689 ms 4.716 ms 5.817 ms * 24.001 ms 4.283 ms 4.718 ms 4.444 ms 4.504 ms * 9.615 ms (15% loss)
2 75-13-84-1.lightspeed.austtx.sbcglobal.net (75.13.84.1) 24.808 ms 29.165 ms 26.469 ms 25.552 ms 26.001 ms 28.687 ms 50.625 ms 29.273 ms 25.581 ms 33.159 ms 25.932 ms 33.335 ms 25.939 ms 24.585 ms 29.974 ms * 38.507 ms 25.822 ms 30.070 ms 32.859 ms (5% loss)
3 71.149.76.45 (71.149.76.45) 25.840 ms 25.996 ms 25.329 ms 26.959 ms 25.975 ms 26.278 ms 26.319 ms 27.854 ms 25.731 ms 26.934 ms 25.743 ms 27.164 ms 27.207 ms 26.692 ms 27.568 ms * 31.406 ms 24.991 ms 26.626 ms 24.775 ms (5% loss)
4 * * * * * 75.8.128.104 (75.8.128.104) 30.956 ms 26.165 ms 25.843 ms 33.122 ms 28.699 ms * * * * * * * * * * (75% loss)
5 12.81.225.241 (12.81.225.241) 33.064 ms 25.982 ms
12.81.225.237 (12.81.225.237) 27.115 ms 27.082 ms
12.81.225.241 (12.81.225.241) 28.589 ms 26.640 ms
12.81.225.237 (12.81.225.237) 28.524 ms 26.820 ms
12.81.225.241 (12.81.225.241) 28.937 ms 26.935 ms
12.81.225.237 (12.81.225.237) 28.334 ms 27.737 ms
12.81.225.241 (12.81.225.241) 27.774 ms
12.81.225.237 (12.81.225.237) 27.270 ms
12.81.225.241 (12.81.225.241) 28.118 ms 27.542 ms
12.81.225.237 (12.81.225.237) 27.527 ms 27.670 ms
12.81.225.241 (12.81.225.241) 27.685 ms 27.866 ms (0% loss)
6 dlstx409me9.ip.att.net (12.123.18.133) 31.472 ms 31.678 ms 31.867 ms 31.876 ms 31.850 ms 30.975 ms 31.696 ms 30.792 ms 32.345 ms 30.748 ms 31.457 ms 31.940 ms 31.420 ms 31.288 ms 34.005 ms * 33.375 ms 31.914 ms 31.182 ms 30.349 ms (5% loss)
7 * * * * * * * * * * * * * * * * * * * * (100% loss)
8 * * * * * * * * * * * * * * * * * * * * (100% loss)
1 homeportal (192.168.1.254) 8.222 ms 4.424 ms 4.693 ms
2 75-13-84-1.lightspeed.austtx.sbcglobal.net (75.13.84.1) 24.623 ms 24.919 ms 34.246 ms
3 71.149.76.45 (71.149.76.45) 24.850 ms 26.429 ms 24.756 ms
4 * * *
5 12.81.225.237 (12.81.225.237) 31.496 ms
12.81.225.241 (12.81.225.241) 27.235 ms
12.81.225.237 (12.81.225.237) 49.800 ms
6 dlstx409me9.ip.att.net (12.123.18.133) 31.898 ms 30.500 ms 31.731 ms
7 * * *
8 * * *
TRACEROUTE from Terminal requires -I to change packet type else that last AT&T router at your location blocks it.
LOOKING GLASS DOES NOT SUPPORT CLASSIC SERVERS!!! FIX IT
System, 2019 iMac, i9, 40G Ram Vega 48 8G Graphics.
AT&T 5268AC router 1G/1G internet. As before, if I use a Windows PC its fine but I prefer to not have WOW on it.
Traceroute via Network Utility
traceroute to 24.105.62.129 (24.105.62.129), 64 hops max, 72 byte packets
1 homeportal (192.168.1.254) 10.881 ms 5.280 ms 3.684 ms
2 107-128-92-1.lightspeed.tukrga.sbcglobal.net (107.128.92.1) 6.922 ms 5.867 ms 4.899 ms
3 107.212.168.126 (107.212.168.126) 7.886 ms 8.497 ms 8.060 ms
4 12.83.82.209 (12.83.82.209) 12.132 ms 11.287 ms 12.018 ms
5 gar18.attga.ip.att.net (12.122.96.89) 10.842 ms 10.798 ms 9.127 ms
6 12.247.68.74 (12.247.68.74) 10.884 ms 10.808 ms 29.633 ms
7 ae1-br01-eqat2.as57976.net (137.221.75.33) 31.455 ms 30.863 ms 31.529 ms
8 et-0-0-4-br02-eqch2.as57976.net (137.221.65.46) 31.112 ms 31.074 ms 40.476 ms
9 be2-pe01-eqch2.as57976.net (137.221.69.71) 31.120 ms 31.609 ms 31.276 ms
10 24.105.62.129 (24.105.62.129) 33.087 ms 31.599 ms 32.605 ms
PathPing -I
iMac:~ WhiteStar$ traceroute -S -I -q 20 24.105.62.129
traceroute to 24.105.62.129 (24.105.62.129), 64 hops max, 72 byte packets
1 homeportal (192.168.1.254) 16.547 ms 4.043 ms 4.691 ms 3.742 ms 3.526 ms 3.657 ms * 4.201 ms 3.441 ms 3.332 ms 3.384 ms 3.461 ms * 4.494 ms 3.397 ms 3.731 ms 3.298 ms 3.319 ms * 3.534 ms (15% loss)
2 107-128-92-1.lightspeed.tukrga.sbcglobal.net (107.128.92.1) 11.560 ms 7.016 ms 10.596 ms 4.830 ms 6.763 ms 5.176 ms 9.427 ms 6.410 ms 4.952 ms 13.786 ms 4.789 ms 11.618 ms 4.937 ms 5.055 ms 5.724 ms * 4.943 ms 11.154 ms 4.450 ms 15.545 ms (5% loss)
3 107.212.168.126 (107.212.168.126) 7.657 ms 8.638 ms 8.205 ms 7.589 ms 8.028 ms 8.560 ms 7.182 ms 8.324 ms 7.680 ms 8.573 ms 7.996 ms 7.379 ms 7.193 ms 8.006 ms 7.145 ms * 7.647 ms 7.154 ms 7.419 ms 7.219 ms (5% loss)
4 12.83.82.209 (12.83.82.209) 11.038 ms 11.517 ms 11.954 ms 12.062 ms 12.007 ms 11.952 ms 12.002 ms 11.981 ms 12.483 ms 11.455 ms 12.038 ms 11.983 ms 11.987 ms 11.890 ms 12.024 ms * 12.135 ms 11.966 ms 11.954 ms 11.995 ms (5% loss)
5 gar18.attga.ip.att.net (12.122.96.89) 8.988 ms 12.081 ms 8.772 ms 9.976 ms 8.574 ms 8.703 ms 8.662 ms 9.051 ms 8.964 ms 8.819 ms 8.786 ms 10.262 ms 9.468 ms 9.230 ms 9.809 ms * 10.336 ms 9.353 ms 10.347 ms 9.063 ms (5% loss)
6 12.247.68.74 (12.247.68.74) 14.153 ms 25.016 ms 10.577 ms 9.868 ms 9.260 ms 9.798 ms 10.424 ms 9.787 ms 9.735 ms 9.800 ms 9.846 ms 9.546 ms 9.439 ms 10.568 ms 9.194 ms * 9.230 ms 12.219 ms 10.014 ms 112.956 ms (5% loss)
7 ae1-br01-eqat2.as57976.net (137.221.75.33) 30.003 ms 29.840 ms 29.856 ms 29.982 ms 29.642 ms 29.997 ms 30.392 ms 30.026 ms 29.915 ms 30.214 ms 30.226 ms 30.177 ms 29.796 ms 30.468 ms 29.898 ms * 30.032 ms 30.035 ms 29.985 ms 29.985 ms (5% loss)
8 et-0-0-4-br02-eqch2.as57976.net (137.221.65.46) 29.935 ms 31.095 ms 30.024 ms 29.836 ms 29.763 ms 29.951 ms 30.009 ms 30.006 ms 30.042 ms 29.689 ms 29.596 ms 37.019 ms 30.026 ms 29.949 ms 30.031 ms * 30.644 ms 35.895 ms 30.273 ms 33.474 ms (5% loss)
9 be2-pe01-eqch2.as57976.net (137.221.69.71) 31.266 ms 30.856 ms 30.671 ms 30.182 ms 29.922 ms 30.659 ms 30.149 ms 30.025 ms 30.416 ms 31.767 ms 29.582 ms 30.791 ms 30.291 ms 29.917 ms 30.029 ms * 31.385 ms 29.782 ms 30.580 ms 30.616 ms (5% loss)
10 24.105.62.129 (24.105.62.129) 30.611 ms 33.805 ms 30.457 ms 32.014 ms 30.765 ms 32.594 ms 31.825 ms 32.565 ms 30.513 ms 30.316 ms 30.144 ms 30.020 ms 30.378 ms 31.363 ms 30.211 ms * 31.844 ms 30.439 ms 30.361 ms 30.613 ms (5% loss)
PATHPING NO -I - basically 6 and beyond are always * * * * * *
iMac:~ WhiteStar$ traceroute -S -q 20 24.105.62.129
traceroute to 24.105.62.129 (24.105.62.129), 64 hops max, 52 byte packets
1 homeportal (192.168.1.254) 10.691 ms 4.346 ms 3.332 ms 3.978 ms 3.306 ms 3.353 ms * 3.494 ms 3.410 ms 4.300 ms 4.478 ms 4.389 ms * 3.334 ms 3.669 ms 3.469 ms 3.278 ms 4.876 ms * 10.298 ms (15% loss)
2 107-128-92-1.lightspeed.tukrga.sbcglobal.net (107.128.92.1) 5.445 ms 10.669 ms 10.245 ms 10.376 ms 9.452 ms 10.212 ms 6.294 ms 7.699 ms 6.022 ms 6.408 ms 6.889 ms 5.413 ms 5.164 ms 8.148 ms 6.135 ms * 6.141 ms 6.329 ms 4.851 ms 17.340 ms (5% loss)
3 107.212.168.126 (107.212.168.126) 9.620 ms 8.919 ms 8.888 ms 7.666 ms 8.494 ms 8.755 ms 8.919 ms 8.883 ms 7.369 ms 8.565 ms 7.463 ms 7.166 ms 8.795 ms 7.378 ms 9.173 ms * 7.912 ms 9.013 ms 10.147 ms 9.581 ms (5% loss)
4 12.83.82.209 (12.83.82.209) 10.689 ms 10.901 ms 12.156 ms 11.830 ms 12.044 ms 11.831 ms 14.176 ms 13.756 ms 12.212 ms 11.872 ms 11.841 ms 11.891 ms 12.096 ms 11.942 ms 12.025 ms * 10.731 ms 11.840 ms 12.221 ms 11.816 ms (5% loss)
5 gar18.attga.ip.att.net (12.122.96.89) 11.171 ms 10.869 ms 9.243 ms 10.080 ms 10.429 ms 9.832 ms 10.196 ms 9.915 ms 9.711 ms 10.467 ms 9.397 ms 10.581 ms 9.187 ms 9.641 ms 10.383 ms * 10.908 ms 10.689 ms 10.451 ms 9.211 ms (5% loss)
6 * * *
Twice now, I’ve had to hard reboot my computer because the game froze everything. Not good for my computer.
And several more times, I’ve had to Force Quit WoW. I’m running windowed so I can at least try to access the desktop to Force Quit.
Everything else is still occurring: the channeling lag, the vendor, fishing, standing still lag is all still happening.
And, I was having such a lovely day on my hunter Araline! 
I’m getting the freeze every time I log into Classic now, so it’s completely unplayable for me until this gets fixed.
BTW, retail seems to run fine. Thanks!
It is frustrating because I just played a good hour on a PC laptop with nae a hint of lag … [on the same home network that I play with my Mac]
It is frustrating because playing WoW is becoming a pain in the behind…
It is frustrating because all indications are that problem is NOT on my end but on the Blizzard side… and yet Blizzard happily takes my monthly subscription…
Mac Pro (trashcan edition)
ISP: Frontier FIOS
Router: Arris (model:NVG468MQ) … Can’t see modem…
Tracer Test
1 gateway (192.168.254.254) 4.418 ms 3.160 ms 2.996 ms
2 * * *
3 172.102.111.184 (172.102.111.184) 8.114 ms 8.651 ms
172.102.104.46 (172.102.104.46) 7.279 ms
4 ae8---0.scr02.lsan.ca.frontiernet.net (74.40.3.49) 7.383 ms 7.121 ms 7.125 ms
5 ae1---0.cbr01.lsan.ca.frontiernet.net (74.40.3.214) 6.602 ms 6.643 ms
ae0---0.cbr01.lsan.ca.frontiernet.net (74.40.3.198) 6.208 ms
Ping Test
1 gateway (192.168.254.254) 5.273 ms 3.077 ms 3.196 ms 3.572 ms 2.950 ms 3.213 ms * 5.387 ms 3.178 ms 3.814 ms 3.360 ms 3.163 ms * 4.877 ms 3.388 ms 3.146 ms 4.084 ms 3.289 ms * 3.161 ms (15% loss)
2 * * * * * * * * * * * * * * * * * * * * (100% loss)
3 172.102.99.122 (172.102.99.122) 9.620 ms 8.996 ms 8.035 ms
172.102.111.184 (172.102.111.184) 7.707 ms 7.625 ms 8.041 ms
172.102.99.122 (172.102.99.122) 12.277 ms
172.102.111.186 (172.102.111.186) 8.684 ms
172.102.104.46 (172.102.104.46) 8.049 ms 7.449 ms
172.102.111.186 (172.102.111.186) 9.495 ms 7.517 ms
172.102.99.122 (172.102.99.122) 6.457 ms
172.102.111.186 (172.102.111.186) 9.073 ms
172.102.104.46 (172.102.104.46) 10.289 ms
172.102.99.122 (172.102.99.122) 7.298 ms
172.102.104.46 (172.102.104.46) 7.531 ms
172.102.111.184 (172.102.111.184) 7.423 ms
172.102.104.46 (172.102.104.46) 7.699 ms
172.102.111.184 (172.102.111.184) 7.525 ms (0% loss)
4 ae8---0.scr01.lsan.ca.frontiernet.net (74.40.3.37) 7.327 ms
ae8---0.scr02.lsan.ca.frontiernet.net (74.40.3.49) 8.393 ms
ae8---0.scr01.lsan.ca.frontiernet.net (74.40.3.37) 6.260 ms
ae8---0.scr02.lsan.ca.frontiernet.net (74.40.3.49) 8.033 ms 7.062 ms
ae8---0.scr01.lsan.ca.frontiernet.net (74.40.3.37) 6.511 ms 6.202 ms 7.459 ms
ae8---0.scr02.lsan.ca.frontiernet.net (74.40.3.49) 6.969 ms 7.167 ms
ae8---0.scr01.lsan.ca.frontiernet.net (74.40.3.37) 7.651 ms 6.030 ms 6.215 ms 9.766 ms
ae8---0.scr02.lsan.ca.frontiernet.net (74.40.3.49) 7.767 ms 7.171 ms
ae8---0.scr01.lsan.ca.frontiernet.net (74.40.3.37) 6.162 ms 6.656 ms
ae8---0.scr02.lsan.ca.frontiernet.net (74.40.3.49) 7.400 ms 6.949 ms (0% loss)
5 ae1---0.cbr01.lsan.ca.frontiernet.net (74.40.3.214) 6.451 ms 6.641 ms 6.626 ms
ae0---0.cbr01.lsan.ca.frontiernet.net (74.40.3.198) 6.417 ms 6.326 ms 5.925 ms 11.917 ms
ae1---0.cbr01.lsan.ca.frontiernet.net (74.40.3.214) 6.911 ms 6.625 ms 7.213 ms 6.471 ms
ae0---0.cbr01.lsan.ca.frontiernet.net (74.40.3.198) 11.265 ms 11.110 ms
ae1---0.cbr01.lsan.ca.frontiernet.net (74.40.3.214) 7.720 ms
ae0---0.cbr01.lsan.ca.frontiernet.net (74.40.3.198) 6.997 ms 7.093 ms 6.165 ms 6.157 ms 7.100 ms
ae1---0.cbr01.lsan.ca.frontiernet.net (74.40.3.214) 30.507 ms (0% loss)
Thanks for the “understanding”… now I am hoping for a solution…
1 Like
Just an FYI. The freeze event seemed to happen only when I went into the Darnassas AH. Got on the Windows laptop, moved her. Got back on the Mac and it worked fine.
Since this seemed to be a separate item, I made a post about on the Bug forum.
so my latest test will be to upjump the process priority for the WOW client.
- Open Activity Monitor - record the PID for WOW
- Open Terminal
- Set priority to max sudo renice -20 PID#
- Verify with ps -fl -C PID#
-20 is maximum priority, go figure. Now the reason for posting this now is I have the most issues when the server is crowded. If there is a means to force WOW to always run at highest priority I would like to know
UPDATE This had zero effect on the problem, so is not something in MacOS going to sleep
So I have deleted and reinstalled the client to no avail. I would delete and reinstall all blizzard products, including deleting all of what is in /user/library/blizzard if I thought it would amount to anything but it won’t
this is truly pathetic, retail works fine. In retail for example, say if I set my alchemist or tailoring to do 20 of something it just happens, one after the other, no input from me. In Classic I cannot even make a bandage and see it occur, hell it will suddenly at times catch up with three or four made. Even clicking complete quest will sometimes require many clicks or spinning A/D to get it to respond properly
WHEN ARE YOU GOING TO UPDATE LOOKING GLASS FOR CLASSIC REALMS?!?!?!?!
Since we’ve done lots of things for you, I’d like to ask you if we can try something.
Please put a button in System/Advanced for “Enable legacy system/spell batching” or something of that sort and put in a code that would give us the system/spell batching in place prior to the reinvisioned code. Is that possible?
Thanks!
I would be happy with more tools to diagnose this issue.
I’m having the same issue. MacBook Pro and AT&T. Makes the game mostly unplayable
the level of incompetence displayed by blizzard never ceases to amaze me… the game is fine in retail but the classic client is a lag fest. so which is it, the client or the routers along the line to the classic server?
plus when will you update looking glass to test against classic realms?
2 Likes
Same problem as well…started playing classic about 3 weeks ago on my mac with no problems until about the first week in. Having to A/D every time i do anything is getting pretty old. Thanks to everyone on here that took the time to run tests and bring attention to this issue.