#1

Been having some stability issues with serialosc. I frequently see 2 or 3 instances of serialoscd running in Activity Monitor. This morning I woke to my MBP fan wooshing loudly. Checked the console and found:

11/29/15 7:26:36.266 AM ReportCrash[3255]: Saved crash report for serialoscd[644] version ??? to /Users/jasonwehmhoener/Library/Logs/DiagnosticReports/serialoscd_2015-11-29-072636_Jasons-MacBook-Pro.crash

11/29/15 7:28:05.000 AM kernel[0]: process serialoscd[633] thread 5681 caught burning CPU!; EXC_RESOURCE supressed due to audio playback

Here’s that crash report. There are a total of 11 crash reports for serialoscd stretching back to the beginning of November. 4 of them are divide by zero errors like this one:
serialoscd_2015-11-29-072636_Jasons-MacBook-Pro.crash (10.8 KB)

The other 7 are bad access/invalid address errors like this one:
serialoscd_2015-11-24-193441_Jasons-MacBook-Pro.crash (10.9 KB)

There doesn’t appear to be any way to determine which version of serialosc I’m running? I’ll also mention that I wasn’t using the monome at the time of this most recent crash.

Please let me know if there’s anything I can do to help further debug. I’m greatly interesting in developing a more thorough understanding of the inner workings of serialosc.

#2

I was having lot’s of crashes going on running osc 1.4
I installed 1.2 right over it and haven’t had any crashes since.

serialosc-1.2a.mpkg.zip (235.5 KB)

#3

@jasonw22 was this 1.4 crashing? what other hardware was plugged in?

#5

Here’s what the system profiler has to say about my USB environment.
usb.rtf (54.4 KB)

That list makes it look complicated, but it’s just the internal keyboard/trackpad, the internal bluetooth host, and the two internal USB hubs, to which are attached a monitor which has an internal hub and media reader. Attached to the monitor is a KVM switch which has a mouse and keyboard attached. There is also a new Anker USB hub attached directly to the Macbook. This has the Monome, Scarlett 18i8 attached. Finally, my silly large Manhattan hub is also attached to the Anker hub, but since I’m only using that to charge things at the moment, I’ll remove that to simplify things.

Here’s what it looks like with the Manhattan hub removed:
usb_v2.rtf (12.8 KB)

#6

How do I determine the version number for serialosc? It was installed with monome_sum, but all I can find about that is “2014”.

#7

Since I never heard an answer about how to determine which version of serialosc I’m using, I went to look at dates in Github. It looks like the monome installer v1.1 was released in June 2014. It looks like serialosc 1.2 was released in October 2012 and 1.4 was released in August 2015. So I guess I probably have serialosc 1.2 installed.

I’m assuming it makes sense to download and install serialosc 1.4? Do I need to uninstall 1.2 first?

Edit: just noticed that the serialosc 1.3 release date makes it a candidate for what I already have installed as well. Which version was included with the monome 1.1 installer? That Github repository doesn’t appear to have any files in it, so I can’t verify for myself.

#8

apologies for the delay. yes-- try 1.4

#9

It’s working perfectly for now.

I learned that a restart is required before the new version will start.

I also learned that while serialosc 1.2 just has three indistinguishable serialoscd processes visible in activity monitor, 1.4 shows serialoscd, serialosc-devic, and serialosc-detector. So that’s one way to tell the difference.

Feature request for version 1.5: a version flag that would be visible in crash reports and from the command line.

#10

Bumping since I’m now asking the same question:

@jasonw22: did you ever figure out how to do this?

#11

If we’re talking about a Mac, searching for serialosc in Activity Monitor should look like the image in this post:

Older versions of serialosc didn’t distinguish between daemon, device, and detector, so you just saw “serialoscd” three times (if memory serves correctly).

#12

Interesting!

This might explain why I’m seeing problems.

Screen Shot 2016-09-16 at 8.52.53 AM.png742×158 13.1 KB

Interestingly, I was sure I had 1.4. Hmmm…

Anyway (and aside), since this comes up somewhat often maybe another community effort could be maintenance of an FAQ for serialosc. For example, I noticed that there’s a stale link on the OSC docs and filed a bug but I’m not sure where that source lives or I’d just submit a PR! :smile:

1 Like
#13

@jasonw22: while I have you… Is there any way to manually start serialosc? IOW, I killed it via the activity monitor but would like to start it again without a full restart.

Thanks in advance!

#14

In an old thread, I found this advice from @tehn:

launchctl stop org.monome.serialosc
launchctl start org.monome.serialosc

but it doesn’t work for me. (Perhaps it’s out of date? That thread is old!)

Also, interestingly, I don’t see serialoscd in /usr/local/bin. Anyone know where the installer puts it? (Yes, Mac.)

#15

If you haven’t installed serialosc v1.4 yet, I recommend going ahead and doing it.

#16

Thanks! I did. Now I’m just trying to kick it off / verify that it installed. Any way short of a restart? Where does it live on your system?

#17

serialoscd (608) 2016-09-16 09-41-31.png1546×1226 127 KB

1 Like
#18

Thanks a million!

After a restart, I appear to be golden.

(and my process details look similar to yours.)

Aside: I opened an issue to track the idea of a serialosc FAQ on the serialosc repo (#25). I wonder though if this wouldn’t be better hosted more centrally and encourage community input. Maybe a new repo in monome-community to host user maintained docs?

1 Like
#19

@tehn, @ppqq needs some monome-community github permissions!

1 Like