![]() |
|
![]() |
#1 |
Junior Member
Join Date: Oct 2005
Posts: 23
|
![]()
Well I should start off by saying that I love the new vent, It's sooo nice that I can now talk to my rl friends and guildies while just hanging out and playing. My WoW guild switched to the speex codec right when this vent game out. I have no problems and it works great when I'm just talking to a few people even like 20 or so. When my guild did BWL, a 40 man raid instance in WoW though I assume most of you know that
![]() |
![]() |
![]() |
![]() |
#2 |
Junior Member
Join Date: Sep 2005
Location: LA, CA
Posts: 12
|
![]()
These random lockups happen absolutely randomly to me as well. While it might be more often with more people, I have done an entire MC clear with 45 people in vent, and not had it lock up once; and then I've been doing WSG with 10 and had it lock up more than twice
![]() |
![]() |
![]() |
![]() |
#3 |
Administrator
Join Date: May 2005
Location: Some insignifcant planet.
Posts: 8,058
|
![]()
Hmm. I have never had this problem. But it could be a latent bug that I just have not able to duplicate.
Are you running 10.3 or 10.4? I'm on 10.3 and won't have 10.4 until this coming week. I doubt it's OS related but it might be. |
![]() |
![]() |
![]() |
#4 |
Junior Member
Join Date: Oct 2005
Posts: 23
|
![]()
I'm running 10.3.9 using a cable connection.
|
![]() |
![]() |
![]() |
#5 |
Junior Member
Join Date: Nov 2005
Posts: 26
|
![]()
I have had my client lock up like this once or twice, but it doesn't seem to matter how many people are in or talking.
I have found, however, that clicking the 'close window' button (which i did accidentally instead of just tabbing back to the game or clicking in the game window) will cause the "thinking beach ball" and the client remains open - it just goes into limbo and will not respond. Maybe closing the window should quit the client, i'm not sure, but it doesn't - it hangs it and all communication ceases until I force-quit and relaunch it. This *might* have been what caused my other one or two hangups... I don't remember if I'd clicked the close window button or not... sometimes you don't think clearly in the heat of battle, lol. I'm using OSX 10.4.2 |
![]() |
![]() |
![]() |
#6 | |
Administrator
Join Date: May 2005
Location: Some insignifcant planet.
Posts: 8,058
|
![]() Quote:
|
|
![]() |
![]() |
![]() |
#7 |
Junior Member
Join Date: Nov 2005
Posts: 26
|
![]()
Yes. If the 'close window' button is indeed supposed to quit the client when it is clicked, then there are two different resultant crashes when quitting.
Choosing quit from the menu (or doing Cmd-Q) yields the "Unexpectedly Quit" dialog, but the client does actually quit. Clicking the window's close box does not give any dialog. The window closes but Vent remains an 'open' but unresponsive application that must be force-quit. (OSX 10.4.2) |
![]() |
![]() |
![]() |
#8 |
Administrator
Join Date: May 2005
Location: Some insignifcant planet.
Posts: 8,058
|
![]()
When does it lock up?
|
![]() |
![]() |
![]() |
#9 | |
Junior Member
Join Date: Dec 2005
Posts: 1
|
![]() Quote:
But I attributed it to some sort of resource leak because it's very consistent, it takes a long time to reproduce, and it's not an error that manifests any warnings, it just kinda, goes away and never comes back. Thank for finally making a beta client for macs, I wish it had some more features, but I know that macs have long been ignored by voice-comm and it's nice to see us get a little attn ![]() |
|
![]() |
![]() |
![]() |
#10 |
Senior Member
Join Date: Nov 2005
Posts: 2,934
|
![]()
It's strange - I've never experienced a lockup, so I'm not sure what the trigger could be. However, our sessions are rarely more than 10 people.
Wade |
![]() |
![]() |
![]() |
Thread Tools | |
Display Modes | |
|
|