HUD 3.0.003542 Crashes on Mac 10.6.2

cmazur
Posts: 2
Member Since:
2010-04-19

Launching HUD on the Mac works great...for about 15 seconds. Then it consistently crashes. I've tried on 2 Mac Book Pros (different generations), both running Snow Leopard. Any hints are greatly appreciated!

*******************************************
Process: HUD [972]
Path: /Applications/HUD3.0.app/Contents/MacOS/HUD
Identifier: com.fonality.hud.edition.hudqueues
Version: ??? (???)
Code Type: X86 (Native)
Parent Process: launchd [195]

Date/Time: 2010-04-19 09:42:00.828 -0700
OS Version: Mac OS X 10.6.2 (10C540)
Report Version: 6

Interval Since Last Report: 48182 sec
Crashes Since Last Report: 11
Per-App Interval Since Last Report: 65 sec
Per-App Crashes Since Last Report: 4
Anonymous UUID: EAE1E825-48D8-4772-A307-4F0E68B0486C

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x000000008b08708f
Crashed Thread: 2 Java: Exception Handler Thread

Application Specific Information:

Java information:
Exception type: Bus Error (0xa) at pc=0x1382d600

Java VM: Java HotSpot(TM) Client VM (14.3-b01-101 mixed mode macosx-x86)

Current thread (0x12000c00): JavaThread "main" [_thread_in_native, id=-1603230464, stack(0xbf800000,0xc0000000)]
Stack: [0xbf800000,0xc0000000]
Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
J org.eclipse.swt.internal.cocoa.Cocoa.objc_msgSend_stret(Lorg/eclipse/swt/internal/cocoa/NSRect;IILorg/eclipse/swt/internal/cocoa/NSRect;I)V
C 0xbfffed5c
C 0x14ef83fe

------ ETC -------------------



jrivero
Posts: 2
Member Since:
2010-04-24
Same problem on my macbook pro

I have the same problem. It would be great to get some help

Process: HUD [12594]
Path: /Applications/HUD3.0.app/Contents/MacOS/HUD
Identifier: com.fonality.hud.edition.hudqueues
Version: 3.0.003542 (3.0.003542)
Code Type: X86 (Native)
Parent Process: launchd [152]

Date/Time: 2010-04-24 12:54:21.158 -0300
OS Version: Mac OS X 10.6.3 (10D573)
Report Version: 6

Interval Since Last Report: 158490 sec
Crashes Since Last Report: 4
Per-App Interval Since Last Report: 458 sec
Per-App Crashes Since Last Report: 4
Anonymous UUID: A6C87855-37E9-412A-8EA0-940888F70EC8

Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000002, 0x0000000000000000
Crashed Thread: 3 Java: Gang worker#0 (Parallel GC Threads)

Application Specific Information:

Java information:
Exception type: Internal Error (/SourceCache/HotSpot16/HotSpot16-101/src/share/vm/runtime/frame.cpp, line 1210)

Error message: ShouldNotReachHere()
Java VM: Java HotSpot(TM) Client VM (14.3-b01-101 mixed mode macosx-x86)

Current thread (0x12802400): GCTaskThread [stack: 0x00000000,0x00000000] [id=-1339002880]
Stack: [0x00000000,0x00000000]

Java Threads: ( => current thread )
0x1210a400 JavaThread "FileWriter" daemon [_thread_blocked, id=-1324552192, stack(0xb0fcf000,0xb10cf000)]
0x128f8400 JavaThread "DNS Lookup" daemon [_thread_blocked, id=-1325608960, stack(0xb0ecd000,0xb0fcd000)]
0x1212b400 JavaThread "NIOServer:plain" daemon [_thread_in_native, id=-1317081088, stack(0xb16ef000,0xb17ef000)]
0x1212a400 JavaThread "NIOServer:ssl" daemon [_thread_blocked, id=-1318137856, stack(0xb15ed000,0xb16ed000)]
0x128ea800 JavaThread "dataTransfer" daemon [_thread_blocked, id=-1319194624, stack(0xb14eb000,0xb15eb000)]
0x128e8800 JavaThread "timer service timer" daemon [_thread_blocked, id=-1320251392, stack(0xb13e9000,0xb14e9000)]
0x128e7c00 JavaThread "timer service timer main" daemon [_thread_blocked, id=-1321308160, stack(0xb12e7000,0xb13e7000)]
0x128e7400 JavaThread "Sound subsystem" daemon [_thread_blocked, id=-1322364928, stack(0xb11e5000,0xb12e5000)]
0x120fa000 JavaThread "VoicemailDownloader" daemon [_thread_blocked, id=-1323421696, stack(0xb10e3000,0xb11e3000)]
0x1205d400 JavaThread "HUDLog" daemon [_thread_blocked, id=-1326665728, stack(0xb0dcb000,0xb0ecb000)]
0x12859800 JavaThread "Low Memory Detector" daemon [_thread_blocked, id=-1328779264, stack(0xb0bc7000,0xb0cc7000)]
0x12858400 JavaThread "CompilerThread0" daemon [_thread_blocked, id=-1330548736, stack(0xb0a17000,0xb0b17000)]
0x12857400 JavaThread "Signal Dispatcher" daemon [_thread_blocked, id=-1331605504, stack(0xb0915000,0xb0a15000)]
0x12856400 JavaThread "Surrogate Locker Thread (CMS)" daemon [_thread_blocked, id=-1332662272, stack(0xb0813000,0xb0913000)]
0x12850c00 JavaThread "Finalizer" daemon [_thread_blocked, id=-1333719040, stack(0xb0711000,0xb0811000)]
0x1205b000 JavaThread "Reference Handler" daemon [_thread_blocked, id=-1334775808, stack(0xb060f000,0xb070f000)]
0x12800400 JavaThread "main" [_thread_in_native, id=-1598487328, stack(0xbf800000,0xc0000000)]
Other Threads:
0x1284e000 VMThread [stack: 0xb050d000,0xb060d000] [id=-1335832576]
0x1285a400 WatcherThread [stack: 0xb0cc9000,0xb0dc9000] [id=-1327722496]

=>0x12802400 (exited) GCTaskThread [stack: 0x00000000,0x00000000] [id=-1339002880]

VM state:at safepoint (normal execution)
VM Mutex/Monitor currently owned by a thread: ([mutex/lock_event])
[0x11e00cc0] Threads_lock - owner thread: 0x1284e000
[0x11e010e0] Heap_lock - owner thread: 0x128e7c00

Heap
par new generation total 14336K, used 12283K [0x15010000, 0x16010000, 0x163c0000)
eden space 12288K, 99% used [0x15010000, 0x15c0eda0, 0x15c10000)
from space 2048K, 0% used [0x15e10000, 0x15e10000, 0x16010000)
to space 2048K, 17% used [0x15c10000, 0x15c67360, 0x15e10000)
concurrent mark-sweep generation total 24576K, used 9513K [0x163c0000, 0x17bc0000, 0x25010000)
concurrent-mark-sweep perm gen total 20472K, used 14013K [0x25010000, 0x2640e000, 0x29010000)

Virtual Machine Arguments:
JVM Args: -Xdock:icon=../Resources/HUD.icns -XstartOnFirstThread -Xms40m -Xmx256m -Dorg.eclipse.swt.internal.carbon.smallFonts -Dorg.eclipse.swt.internal.carbon.noFocusRing -Dnetworkaddress.cache.ttl=30 -Dnetworkaddress.cache.negative.ttl=5
Java Command:
Launcher Type: generic
Physical Memory: Page Size = 4k, Total = 3840M, Free = 127M
etc etc etc



jrivero
Posts: 2
Member Since:
2010-04-24
Solution found for snow leopard incompatibility

Dear CMAZUR

This should solve your probems, it solved mine.

Just follow the instructions contained in the "WORK AROUND THE CONNECTION PROBLEM" section of this link

http://wiki.oneswarm.org/index.php/OS_X_10.6_Snow_Leopard

Regards,

Jose



marcuso
Posts: 8
Member Since:
2009-04-12
Extremely disappointing

Nearly one year after the release of Snow Leopard, and Fonality still hasn't released a HUD that works with the current version of the Mac OS - a version that is essential a bug-fix release that almost all users have moved to. I find the fix to be a poor option, and I am disappointed that I spent the $s on the Call Center edition of Trixbox.



gpubit
Posts: 2
Member Since:
2010-09-08
Also Disappointed

I would agree. The problem with this fix is that it forces other applications to use an older version of Java which has caused issues in Firefox on multiple sites that use Java. The workaround has caused so many other issues that we have been forced to not use Hud on any of our Mac's running Snow Leopard. I have heard a new version of Trixbox 5 / Hud are about to be released. It's available on the Fonality PBxtra side of things from what I hear. Hopefully that fixes the problems. It amazes me how slow Fonality is at addressing problems and issues. They seem a lot more interested in their Fonality product that generates ongoing monthly revenue from subscription fees than their larger Corporate Trixbox clients who paid the outrageous license fee and a smaller annual support fee. I get the feeling we made the wrong decision to go with Fonality.



bigtoepdx
Posts: 1
Member Since:
2010-09-13
ditto

I just created an account in order to add a 'me too' to this thread. Why has the client not been updated to support the current OS/Java? The workaround is unsatisfactory for the reasons above, and must be repeated after major updates and/or migration of a user to a new workstation.

PLEASE UPDATE THE HUD CLIENT ASAP!!!



dannyn
Posts: 2
Member Since:
2010-08-31
Add me to that list. Mine

Add me to that list. Mine crashes within 30 seconds too.



MacUser
Posts: 1
Member Since:
2010-09-21
Very Disappointing

I purchased Fonality for our company after being reassured that the HUD supports Macs. Its now 3 years later and I have yet to have the HUD work on my Mac. Hud 2.0 did not and now 3.0 that I had been waiting for does not either. It is very disappointing that Fonality seems to not care about its Mac-based customers. Not a bit of help from them yet on this. I will never recommend this product to any company that uses Macs or is cross-platform based. I probably will not recommend it to any other company either due to the many many problems we have had getting the system to run properly.



viper1701
Posts: 1
Member Since:
2010-11-15
This is ridiculous

I just had to downgrade my Java environments yet again again because Fonality can't be bothered to fix their product. I wonder if submitting a complaint to Apple is worthwhile. Fonality claims that HUD is Snow Leopard compatible, when it really isn't.



cmazur
Posts: 2
Member Since:
2010-04-19
The upgrade works but...

Since upgrading our server to PBXtra 5.2, HUD server and clients are also upgraded. I've confirmed that HUD3.5 works on Snow Leopard w/o tweaking Java. Unfortunately HUD3.5 is not downward compatible with HUD3.0 server so you'll need to upgrade both.



wrc1045
Posts: 199
Member Since:
2008-04-20
any updates?

Pro box/call center edition

with OS 10.6.3 - shuts down in 20-30 seconds

any updates?



nzkef
Posts: 171
Member Since:
2007-12-11
As mentioned by cmazur, the

As mentioned by cmazur, the definite solution is to get your trixbox server upgraded to 5.2 and consequently your HUD server to 3.5.

I have a Macbook Pro on OS 10.6.7 working fine. (it was also working on earlier versions of Snow Leapord.

Why would fonality worry about an upgrade to HUD 3.0 when they have 3.5 working?



wrc1045
Posts: 199
Member Since:
2008-04-20
Upgrades?

well I don't want to update anything that is not broken (other than the Mac issues). Everytime in the past when we upgraded we had nothing but issues for months. Even the pay tech support we had was unable to undo the upgrade issues. So I again ask why will I upgrade when things work just fine.

Call Center Pro



nzkef
Posts: 171
Member Since:
2007-12-11
Your call......

Well I don't work for Fonality, so I can't speak for them. But I doubt you'll get much assistance on an old product that has been superseded by a new version. Just saying.

I've upgrade 85+ trixbox pro servers to date with another 65 to go. Sometimes things go smoothly, sometimes they don't. There are a lot of variables at play here that will determine the outcome. Admittedly the first few had issues and were definitely a learning experience. However as this upgrade updates Asterisk, there was always the possibility for issues.

So you can ask, why should you upgrade when everything is working just fine. My answer would be, the update to Asterisk 1.6 is worth the potential hassle alone. As someone who works on customers servers all day / everyday, I much prefer working on 1.6 than 1.2.

But hey..... your call. Play it safe and have no HUD for MAC. Or work through the upgrade and get HUD working for everyone.

Kevin.



Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.