Jump to content

Hello! 👋

These forums are now archived (read only).

Join us on Discord.

Recommended Posts

HI,

i used synergy only a few times, some times as client another times as server.

Today i change in my mac from client to server and it crashed. I reboot several times but it ever crash with no other message.

 

Link to post
Share on other sites

I have a similar problem. Running version 1.8.8 on a MacBook with newest OS version. just crashes upon start everytime. Below is an excerpt of the error that Apple produces: 

 

Process: Synergy [892]
Path: /Applications/Synergy.app/Contents/MacOS/Synergy
Identifier: synergy
Version: 1.8.8 (1.8.8)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: Synergy [892]
User ID: 501

Date/Time: 2017-05-29 10:02:24.190 -0700
OS Version: Mac OS X 10.12.5 (16F73)
Report Version: 12
Anonymous UUID: 231BD00A-A7C3-0ACB-0821-6E7171F6E78E

Time Awake Since Boot: 1700 seconds

System Integrity Protection: enabled

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000600000800000
Exception Note: EXC_CORPSE_NOTIFY

Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [0]

VM Regions Near 0x600000800000:
MALLOC_NANO 0000600000000000-0000600000800000 [ 8192K] rw-/rwx SM=PRV
-->
MALLOC_NANO 0000608000000000-0000608000800000 [ 8192K] rw-/rwx SM=PRV

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 QtCore 0x00000001064f2340 0x106287000 + 2536256
1 QtCore 0x000000010634a0d6 QString::toUtf8() const + 38
2 synergy 0x00000001053edd65 QString::toStdString() const + 21
3 synergy 0x0000000105403722 LicenseManager::refresh() + 130
4 synergy 0x00000001053b1289 MainWindow::MainWindow(QSettings&, AppConfig&, LicenseManager&) + 1337
5 synergy 0x00000001053b05cb main + 955
6 libdyld.dylib 0x00007fffcf32f235 start + 1

Thread 1:
0 libsystem_kernel.dylib 0x00007fffcf45e44e __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fffcf548621 _pthread_wqthread + 1426
2 libsystem_pthread.dylib 0x00007fffcf54807d start_wqthread + 13

Thread 2:: Qt bearer thread
0 libsystem_kernel.dylib 0x00007fffcf45deb6 __select + 10
1 QtCore 0x00000001064e87d3 qt_safe_select(int, fd_set*, fd_set*, fd_set*, timespec const*) + 547
2 QtCore 0x00000001064e9668 QEventDispatcherUNIXPrivate::doSelect(QFlags<QEventLoop::ProcessEventsFlag>, timespec*) + 680
3 QtCore 0x00000001064ea4eb QEventDispatcherUNIX::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 251
4 QtCore 0x000000010649764d QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 397
5 QtCore 0x00000001062ad6de QThread::exec() + 126
6 QtCore 0x00000001062b1392 0x106287000 + 172946
7 libsystem_pthread.dylib 0x00007fffcf54893b _pthread_body + 180
8 libsystem_pthread.dylib 0x00007fffcf548887 _pthread_start + 286
9 libsystem_pthread.dylib 0x00007fffcf54808d thread_start + 13

Thread 3:
0 libsystem_kernel.dylib 0x00007fffcf45e44e __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fffcf548621 _pthread_wqthread + 1426
2 libsystem_pthread.dylib 0x00007fffcf54807d start_wqthread + 13

Thread 4:
0 libsystem_kernel.dylib 0x00007fffcf45e44e __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fffcf54848e _pthread_wqthread + 1023
2 libsystem_pthread.dylib 0x00007fffcf54807d start_wqthread + 13

Thread 5:
0 libsystem_kernel.dylib 0x00007fffcf45e44e __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fffcf548621 _pthread_wqthread + 1426
2 libsystem_pthread.dylib 0x00007fffcf54807d start_wqthread + 13

Thread 0 crashed with X86 Thread State (64-bit):
rax: 0x000000028a3a50f0 rbx: 0x000000020ab54028 rcx: 0x0000000000000046 rdx: 0x0000000000000000
rdi: 0x00007fff5a853418 rsi: 0x0000600000800000 rbp: 0x00007fff5a8533e0 rsp: 0x00007fff5a8533a0
r8: 0x0000000000000000 r9: 0x0000608000236a40 r10: 0x0000000105de9110 r11: 0x00005ffef9e7caa0
r12: 0x00007fff5a853b3f r13: 0x00000000ffffffff r14: 0x0000000000000000 r15: 0x00007fff5a853418
rip: 0x00000001064f2340 rfl: 0x0000000000010293 cr2: 0x0000600000800000

Logical CPU: 0
Error Code: 0x00000006
Trap Number: 14

Link to post
Share on other sites
Paul Suarez
5 minutes ago, Joey said:

I have a similar problem. Running version 1.8.8 on a MacBook with newest OS version. just crashes upon start everytime. Below is an excerpt of the error that Apple produces: 

 

Process: Synergy [892]
Path: /Applications/Synergy.app/Contents/MacOS/Synergy
Identifier: synergy
Version: 1.8.8 (1.8.8)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: Synergy [892]
User ID: 501

Date/Time: 2017-05-29 10:02:24.190 -0700
OS Version: Mac OS X 10.12.5 (16F73)
Report Version: 12
Anonymous UUID: 231BD00A-A7C3-0ACB-0821-6E7171F6E78E

Time Awake Since Boot: 1700 seconds

System Integrity Protection: enabled

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000600000800000
Exception Note: EXC_CORPSE_NOTIFY

Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [0]

VM Regions Near 0x600000800000:
MALLOC_NANO 0000600000000000-0000600000800000 [ 8192K] rw-/rwx SM=PRV
-->
MALLOC_NANO 0000608000000000-0000608000800000 [ 8192K] rw-/rwx SM=PRV

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 QtCore 0x00000001064f2340 0x106287000 + 2536256
1 QtCore 0x000000010634a0d6 QString::toUtf8() const + 38
2 synergy 0x00000001053edd65 QString::toStdString() const + 21
3 synergy 0x0000000105403722 LicenseManager::refresh() + 130
4 synergy 0x00000001053b1289 MainWindow::MainWindow(QSettings&, AppConfig&, LicenseManager&) + 1337
5 synergy 0x00000001053b05cb main + 955
6 libdyld.dylib 0x00007fffcf32f235 start + 1

Thread 1:
0 libsystem_kernel.dylib 0x00007fffcf45e44e __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fffcf548621 _pthread_wqthread + 1426
2 libsystem_pthread.dylib 0x00007fffcf54807d start_wqthread + 13

Thread 2:: Qt bearer thread
0 libsystem_kernel.dylib 0x00007fffcf45deb6 __select + 10
1 QtCore 0x00000001064e87d3 qt_safe_select(int, fd_set*, fd_set*, fd_set*, timespec const*) + 547
2 QtCore 0x00000001064e9668 QEventDispatcherUNIXPrivate::doSelect(QFlags<QEventLoop::ProcessEventsFlag>, timespec*) + 680
3 QtCore 0x00000001064ea4eb QEventDispatcherUNIX::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 251
4 QtCore 0x000000010649764d QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 397
5 QtCore 0x00000001062ad6de QThread::exec() + 126
6 QtCore 0x00000001062b1392 0x106287000 + 172946
7 libsystem_pthread.dylib 0x00007fffcf54893b _pthread_body + 180
8 libsystem_pthread.dylib 0x00007fffcf548887 _pthread_start + 286
9 libsystem_pthread.dylib 0x00007fffcf54808d thread_start + 13

Thread 3:
0 libsystem_kernel.dylib 0x00007fffcf45e44e __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fffcf548621 _pthread_wqthread + 1426
2 libsystem_pthread.dylib 0x00007fffcf54807d start_wqthread + 13

Thread 4:
0 libsystem_kernel.dylib 0x00007fffcf45e44e __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fffcf54848e _pthread_wqthread + 1023
2 libsystem_pthread.dylib 0x00007fffcf54807d start_wqthread + 13

Thread 5:
0 libsystem_kernel.dylib 0x00007fffcf45e44e __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fffcf548621 _pthread_wqthread + 1426
2 libsystem_pthread.dylib 0x00007fffcf54807d start_wqthread + 13

Thread 0 crashed with X86 Thread State (64-bit):
rax: 0x000000028a3a50f0 rbx: 0x000000020ab54028 rcx: 0x0000000000000046 rdx: 0x0000000000000000
rdi: 0x00007fff5a853418 rsi: 0x0000600000800000 rbp: 0x00007fff5a8533e0 rsp: 0x00007fff5a8533a0
r8: 0x0000000000000000 r9: 0x0000608000236a40 r10: 0x0000000105de9110 r11: 0x00005ffef9e7caa0
r12: 0x00007fff5a853b3f r13: 0x00000000ffffffff r14: 0x0000000000000000 r15: 0x00007fff5a853418
rip: 0x00000001064f2340 rfl: 0x0000000000010293 cr2: 0x0000600000800000

Logical CPU: 0
Error Code: 0x00000006
Trap Number: 14

Please use v1.9 from Download Synergy 1.9.0 to fix the wifi macOS bug forums thread.

Link to post
Share on other sites
Paul Suarez
Just now, Joey said:

I tried. same problem.

 

Please create a different thread and post your crash info there.

Link to post
Share on other sites
Paul Suarez

@toran Our developers are now aware of this issue. They're currently working on crash handling to fix this. Please bear with us as we try to make Synergy better for everyone. We currently can't provide any ETAs but one thing I can assure you is that our developers are burning the midnight oil for this issue.

Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...