Opened 9 years ago

Closed 8 years ago

#49699 closed defect (duplicate)

sshfs @2.5: GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed

Reported by: bnilsson11 Owned by: drkp (Dan Ports)
Priority: Normal Milestone:
Component: ports Version: 2.3.4
Keywords: Cc: kangshiyin@…, ramundsen85, nilstec_inc@…
Port: sshfs

Description (last modified by ryandesign (Ryan Carsten Schmidt))

Whenever I use sshfs, I get:

(process:478): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed

sshfs works, but it is disturbing.

I am using OS X 10.11.1 on a MacPro6,1

Attachments (2)

Portfile.diff (414 bytes) - added by ramundsen85 9 years ago.
patch-semaphore-implementation.diff (9.9 KB) - added by ramundsen85 9 years ago.
semaphore implementation adopted from osxfuse sshfs

Download all attachments as: .zip

Change History (9)

comment:1 Changed 9 years ago by ryandesign (Ryan Carsten Schmidt)

Description: modified (diff)
Owner: changed from macports-tickets@… to dports@…
Summary: sshfs gives glib error messagesshfs @2.5: GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed

You should probably report this problem to the developers of sshfs so that they can fix it.

comment:2 Changed 9 years ago by kangshiyin@…

Cc: kangshiyin@… added

Cc Me!

comment:3 Changed 9 years ago by ramundsen85

Cc: framic5@… added

Cc Me!

comment:4 Changed 9 years ago by ramundsen85

I'm not sure if this is a problem of sshfs itself. I compiled sshfs version 2.5 manually and the error message vanishes:

$ ./sshfs -V
SSHFS version 2.5
OSXFUSE library version: FUSE 2.7.3 / OSXFUSE 2.8.2
no mount point
$
$ /opt/local/bin/sshfs -V

(process:84273): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed
SSHFS version 2.5
OSXFUSE library version: FUSE 2.7.3 / OSXFUSE 2.8.2
no mount point

comment:5 Changed 9 years ago by ramundsen85

I realized that the message arises from an old semaphore implementation adopted from fuse4x. I think the corresponding ticket was #30440. I still don't know what causes the mesasge.

Anyhow, since fuse4x is not supported anymore, I tried a similar implementation from osxfuse as workaround: https://github.com/osxfuse/sshfs/commit/14581937282486ab7ce057ec79f226181ef1d45d

I'll attach a patch file to switch from the fuse4x to the osxfuse semaphore implementation.

Changed 9 years ago by ramundsen85

Attachment: Portfile.diff added

Changed 9 years ago by ramundsen85

semaphore implementation adopted from osxfuse sshfs

comment:6 Changed 9 years ago by nilstec_inc@…

Cc: nilstec_inc@… added

Cc Me!

comment:7 Changed 8 years ago by lpsinger (Leo Singer)

Resolution: duplicate
Status: newclosed

Duplicate of #49494.

Note: See TracTickets for help on using tickets.