Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Boot fail - win 10 x64 #1490

Closed
gl33mer opened this issue Nov 27, 2016 · 73 comments
Closed

Boot fail - win 10 x64 #1490

gl33mer opened this issue Nov 27, 2016 · 73 comments
Assignees
@llloret
Labels
boot Windows

Comments

@gl33mer
Copy link

gl33mer commented Nov 27, 2016

At some point a few weeks back Supercollider stopped working properly on my machine. I haven't managed to solve the issue. This is the issue (closed due to a patch I haven't tried applying) and has to do with Boost.

Since, Sonicpi has also failed to boot.

I install the latest sonic pi (2.11 - msi and protable) they just fail on startup.

I've trying clear the event log as suggested in that issue thread mentioned above.

Easy solve?
@llloret
Copy link
Collaborator

llloret commented Nov 27, 2016 via email

@gl33mer
Copy link
Author

gl33mer commented Nov 28, 2016

Ok. Thank you.

Here are the logs from the portable install:
debug - is empty

GuiLog-

[GUI] - Detecting port numbers...
[GUI] - GUI OSC listen port 4558
[GUI] - GUI OSC out port 4557
[GUI] - Server OSC listen port 4557
[GUI] - Server OSC out port 4558
[GUI] - Server incoming OSC cues port 4559
[GUI] - Scsynth port 4556
[GUI] - Scsynth send port 4556
[GUI] - Init script completed
[GUI] - using default editor colours
[GUI] - launching Sonic Pi Server:
[GUI] - starting UDP OSC Server on port 4558...
[GUI] - UDP OSC Server ready and listening
[GUI] - Ruby server pid registered: 976
[GUI] - waiting for Sonic Pi Server to boot...
..
[GUI] - Sonic Pi Server successfully booted.
[GUI] - waiting for Sonic Pi Server to respond...
..
[GUI] - Sonic Pi Server connection established
[GUI] - loading workspaces

processes log-

No pids store found here: C:/Users/Shva/AppData/Local/Temp/SonicPiPortableTemp/sonic-pi-pids
Exiting
Creating pids store: C:/Users/Shva/AppData/Local/Temp/SonicPiPortableTemp/sonic-pi-pids
Started [976] [-] "C:\Users\Shva\Desktop\SonicPi_Portable\SonicPiPortable\App\Sonic Pi\app\gui\qt\release........\app\server\native\win\ruby\bin\ruby.exe" -E utf-8 "C:\Users\Shva\Desktop\SonicPi_Portable\SonicPiPortable\App\Sonic Pi\app\gui\qt\release........\app\server\bin\sonic-pi-server.rb" -u 4557 4558 4556 4556 4559 [-] C:/Users/Shva/AppData/Local/Temp/SonicPiPortableTemp/sonic-pi-pids/976
Started [884] [-] "C:\Users\Shva\Desktop\SonicPi_Portable\SonicPiPortable\App\Sonic Pi\app\server\native\win\scsynth.exe" -u 4556 -a 1024 -m 131072 -D 0 -R 0 -l 1 -i 16 -o 16 -b 4096 -U "C:/Users/Shva/Desktop/SonicPi_Portable/SonicPiPortable/App/Sonic Pi/app/server/native/win/plugins/" -B 127.0.0.1 [-] C:/Users/Shva/AppData/Local/Temp/SonicPiPortableTemp/sonic-pi-pids/884

Scsynth Log-

Starting SuperCollider 2016-11-27 08:40:47

Device options:

Booting with:
In: MME : Line In (Scarlett 2i2 USB)
Out: MME : Line Out (Scarlett 2i2 USB)
Sample rate: 44100.000
Latency (in/out): 0.013 / 0.091 sec
SC_AudioDriver: sample rate = 44100.000000, driver's block size = 64
SuperCollider 3 server ready.

server errors - is empty

and server ouput log-

Sonic Pi server booting...
Detecting port numbers...
Send port: 4558
Listen port: 4557
Scsynth port: 4556
Scsynth send port: 4556
OSC cues port: 4559
Using protocol: udp
booting server...

Booting Sonic Pi

Booting on Windows
Boot - Starting the SuperCollider server...
Boot - SuperCollider booted successfully.
Boot - Connecting to the SuperCollider server...
Boot - Sending /status to server: localhost:4556
Boot - Receiving ack from server on port 5998
Boot - Server connection established
This is Sonic Pi v2.11 running on windows with ruby api 2.3.0.
Sonic Pi Server successfully booted.

Seems all is working but SonicPi crashes before the gui is drawn (only the splash screen is seen).

Thanks again.

@samaaron
Copy link
Collaborator

This is very odd - these logs are telling me that everything is working just fine.

This is the first time I've ever seen an issue where the GUI doesn't start yet the logs all look good...

When Sonic Pi crashes - what do you see? How do you know it's crashed?

@llloret
Copy link
Collaborator

llloret commented Nov 28, 2016 via email

@gl33mer
Copy link
Author

gl33mer commented Nov 28, 2016

@llloret - reboot seemed to solve it for now. SonicPI just booted. (I rarely boot my machine)

(can't wait to get the guitar and mic wired up through sound_in*)

Thanks for your help and this most excellent project.

@gl33mer gl33mer closed this as completed Nov 28, 2016
@gl33mer
Copy link
Author

gl33mer commented Dec 1, 2016

Reopening this issue.
Started crashing again.
Reboot did not solve crash (though some gui window seems to try and open - so behavior is a little different than before reboot where I only get to the splash screen).

Let me know if there's something I can do to help debug this. ty.

@gl33mer gl33mer reopened this Dec 1, 2016
@samaaron
Copy link
Collaborator

samaaron commented Dec 1, 2016

Do you see an error message on a failed boot?

@gl33mer
Copy link
Author

gl33mer commented Dec 1, 2016

Not sure what you mean by error message.
Each time is a bit different. Basically - sonic pi has stopped responding, blah blah :-)
After reboot I also got an option to debug which gave a message about just-in-time debugger not installed or something along those lines (tried to screen capture it and fumbled - could try and generate it again if that helps)

@samaaron
Copy link
Collaborator

samaaron commented Dec 1, 2016

weird - you should get a little window popping up apologising that there was an error during the boot process with a description of what went wrong.

The fact you're not seeing that is very curious as I've never seen a report to date that suggests the error window didn't appear. It should take about 60s from initial boot to appear.

@samaaron
Copy link
Collaborator

samaaron commented Dec 1, 2016

screen shot 2016-12-01 at 13 36 35

@gl33mer
Copy link
Author

gl33mer commented Dec 1, 2016

Ok. I rebooted. This is the window is what I get:
https://snag.gy/Hr63V7.jpg
After splash screen. There is also what seems like the main GUI window before anything is actually drawn.
And this when I press debug.
https://snag.gy/VprdYE.jpg

@samaaron
Copy link
Collaborator

samaaron commented Dec 1, 2016 •
edited

How very odd - this is the first time I've seen an error like that. Looks like the c++ app has totally crashed.

Is there any chance you could delete your ~/.sonic-pi/log directory, then reboot and then paste the contents of the files from there into this conversation?

@gl33mer
Copy link
Author

gl33mer commented Dec 1, 2016

As instructed.

Debug: empty.

GUI:
[GUI] - Detecting port numbers...
[GUI] - GUI OSC listen port 4558
[GUI] - GUI OSC out port 4557
[GUI] - Server OSC listen port 4557
[GUI] - Server OSC out port 4558
[GUI] - Server incoming OSC cues port 4559
[GUI] - Scsynth port 4556
[GUI] - Scsynth send port 4556
[GUI] - Init script completed
[GUI] - using default editor colours
[GUI] - launching Sonic Pi Server:
[GUI] - starting UDP OSC Server on port 4558...
[GUI] - UDP OSC Server ready and listening
[GUI] - Ruby server pid registered: 8592
[GUI] - waiting for Sonic Pi Server to boot...
...
[GUI] - Sonic Pi Server successfully booted.
[GUI] - waiting for Sonic Pi Server to respond...
..
[GUI] - Sonic Pi Server connection established
[GUI] - loading workspaces

Processes:
No pids store found here: C:/Users/Shva/AppData/Local/Temp/SonicPiPortableTemp/sonic-pi-pids
Exiting
Creating pids store: C:/Users/Shva/AppData/Local/Temp/SonicPiPortableTemp/sonic-pi-pids
Started [8592] [-] "C:\Users\Shva\Desktop\SonicPi_Portable\SonicPiPortable\App\Sonic Pi\app\gui\qt\release........\app\server\native\win\ruby\bin\ruby.exe" -E utf-8 "C:\Users\Shva\Desktop\SonicPi_Portable\SonicPiPortable\App\Sonic Pi\app\gui\qt\release........\app\server\bin\sonic-pi-server.rb" -u 4557 4558 4556 4556 4559 [-] C:/Users/Shva/AppData/Local/Temp/SonicPiPortableTemp/sonic-pi-pids/8592
Started [3608] [-] "C:\Users\Shva\Desktop\SonicPi_Portable\SonicPiPortable\App\Sonic Pi\app\server\native\win\scsynth.exe" -u 4556 -a 1024 -m 131072 -D 0 -R 0 -l 1 -i 16 -o 16 -b 4096 -U "C:/Users/Shva/Desktop/SonicPi_Portable/SonicPiPortable/App/Sonic Pi/app/server/native/win/plugins/" -B 127.0.0.1 [-] C:/Users/Shva/AppData/Local/Temp/SonicPiPortableTemp/sonic-pi-pids/3608

Scsynth:

Starting SuperCollider 2016-12-01 18:05:58

Device options:

Booting with:
In: MME : Line In (Scarlett 2i2 USB)
Out: MME : Line Out (Scarlett 2i2 USB)
Sample rate: 44100.000
Latency (in/out): 0.013 / 0.091 sec
SC_AudioDriver: sample rate = 44100.000000, driver's block size = 64
SuperCollider 3 server ready.

Server-Errors: Empty.

Server-Output:
Sonic Pi server booting...
Detecting port numbers...
Send port: 4558
Listen port: 4557
Scsynth port: 4556
Scsynth send port: 4556
OSC cues port: 4559
Using protocol: udp
booting server...

Booting Sonic Pi

Booting on Windows
Boot - Starting the SuperCollider server...
Boot - SuperCollider booted successfully.
Boot - Connecting to the SuperCollider server...
Boot - Sending /status to server: localhost:4556
Boot - Receiving ack from server on port 5998
Boot - Server connection established
This is Sonic Pi v2.11 running on windows with ruby api 2.3.0.
Sonic Pi Server successfully booted.

To get back to the beginning of this thread.
I was working with Supercollider for a few weeks. Assumed I managed to mess up some config file somewhere in the filesystem that causes Supercollider to fail. To this day haven't managed to get Supercollider to work again. (no matter what version I tried including the betas, though haven't tried for a few weeks)

Could this possibly have an effect on this SonicPi behavior? Even though it's a portable version (and probably shouldn't rely on the Supercollider config files even if it wasn't) maybe it still reads from these config files, somewhere by mistake?

Probably isn't it, but thought I'd bring it up again.

@gl33mer
Copy link
Author

gl33mer commented Dec 1, 2016

I can't seem to retrace what Supercollider stuff I installed (and where it was installed) that seemed to cause the orignal SC crash to begin with.

@samaaron
Copy link
Collaborator

samaaron commented Dec 1, 2016

Thanks for this - it's very useful :)

Does supercollider crash in an identical fashion?

@gl33mer
Copy link
Author

gl33mer commented Dec 1, 2016

No worries. It's my pleasure. I love this project. <3

(The funny thing is I'm trying to use SonicPi for a realtime guitar/electro setup for a professional guitarist friend. Even though it currently looks unusable - my experience with SonicPi has been extremely stable and I still think we'll eventually be able to use it. At the very least for a test run)

I actually haven't used SC for quite a while. Not even sure what version/s is currently installed. I'll be checking the SC end of things again and get back to you.

@gl33mer
Copy link
Author

gl33mer commented Dec 1, 2016

It seems SuperCollider is not currently installed. Should I install the latest version and try it out? (v. 3.8.0)

@samaaron
Copy link
Collaborator

samaaron commented Dec 1, 2016

That would be useful - yes please.

@gl33mer
Copy link
Author

gl33mer commented Dec 1, 2016

Ok. 3.8.0 seems to run fine (not crashing, etc.)
I'm a little rusty with SC. Tried to change device in server options by doing the following:

o = Server.local.options;
o.device ="ASIO";  
s.reboot;

This gave the following errors. Not sure if this is related. (That's all I can do for now, busy for the next few hours):

Booting with:
  In: ASIO : Focusrite USB 2.0 Audio Driver
  Out: ASIO : Focusrite USB 2.0 Audio Driver
  Sample rate: 44100.000
  Latency (in/out): 0.023 / 0.034 sec
SC_AudioDriver: sample rate = 44100.000000, driver's block size = 64
SuperCollider 3 server ready.
Receiving notification messages from server localhost
Cannot connect to shared memory: The system cannot find the file specified.
ERROR: Primitive '_ServerShmInterface_connectSharedMem' failed.
Failed.
RECEIVER:
Instance of ServerShmInterface {    (000001EA06854408, gc=DC, fmt=00, flg=00, set=02)
  instance variables [2]
    ptr : nil
    finalizer : nil
}

PROTECTED CALL STACK:
	Meta_MethodError:new	000001EA03688C40
		arg this = PrimitiveFailedError
		arg what = Failed.
		arg receiver = a ServerShmInterface
	Meta_PrimitiveFailedError:new	000001EA0368F200
		arg this = PrimitiveFailedError
		arg receiver = a ServerShmInterface
	Object:primitiveFailed	000001E9C3278280
		arg this = a ServerShmInterface
	a FunctionDef	000001EA04236040
		sourceCode = "<an open Function>"
	Routine:prStart	000001EA03CEE600
		arg this = a Routine
		arg inval = 394.6485828

CALL STACK:
	MethodError:reportError   000001EA04C24938
		arg this = <instance of PrimitiveFailedError>
	< closed FunctionDef >   000001EA04B700E8
		arg error = <instance of PrimitiveFailedError>
	Integer:forBy   000001EA045A5F98
		arg this = 0
		arg endval = 0
		arg stepval = 2
		arg function = <instance of Function>
		var i = 0
		var j = 0
	SequenceableCollection:pairsDo   000001EA04C76998
		arg this = [*2]
		arg function = <instance of Function>
	Scheduler:seconds_   000001EA047B59A8
		arg this = <instance of Scheduler>
		arg newSeconds = 395.4721892
	Meta_AppClock:tick   000001EA0473EAF8
		arg this = <instance of Meta_AppClock>
		var saveClock = <instance of Meta_SystemClock>
	Process:tick   000001EA0472F788
		arg this = <instance of Main>
^^ The preceding error dump is for ERROR: Primitive '_ServerShmInterface_connectSharedMem' failed.
Failed.
RECEIVER: a ServerShmInterface

This might be due to some simple oversight of mine. Hope it helps.

@samaaron
Copy link
Collaborator

samaaron commented Dec 1, 2016

interesting - that doesn't look too good.

Which files do you have in ~/.sonic-pi/log ?

@samaaron
Copy link
Collaborator

samaaron commented Dec 1, 2016 •
edited

@llloret - does this look like the windows error you're already aware of?

@llloret
Copy link
Collaborator

llloret commented Dec 1, 2016 via email

@gl33mer
Copy link
Author

gl33mer commented Dec 2, 2016

@llloret Could you guide me through it?
Right click on the windows menu --> event viewer --> Windows logs -->system and then right click ---> find
Not sure what I'm searching for though.

@llloret
Copy link
Collaborator

llloret commented Dec 2, 2016

@gl33mer Ok, I have checked my notes, and the problem that you are having is actually something that is being uncovered by the patch I submitted to SuperCollider to fix the original issue.

I have not been able to reproduce it on my set up, but @bagong reported it. It seems to happen intermittently. I see that you were in the thread on the SuperCollider github.

Anyway as far as we know, it should not happen if the necessary event (eventID 6005) is found in the Event log. So launch the "Event viewer" (just type that on the start menu, and should appear), and then once in there, Windows Logs->System. There, see if you can see eventId 6005 (you can sort and filter on column). Let us know if there is such an event when it is failing to start as you report.

@gl33mer
Copy link
Author

gl33mer commented Dec 2, 2016

Ok. Thanks @llloret . There is an event 6005 (more than one)

@llloret
Copy link
Collaborator

llloret commented Dec 3, 2016 via email

@gl33mer
Copy link
Author

gl33mer commented Dec 3, 2016

It seems to be every time.

@gl33mer
Copy link
Author

gl33mer commented Dec 4, 2016

I just did the following.
Uninstalled previous version of SuperCollider or SonicPi (except the portable one)
Erased eventlog
Restarted computer
Installed SonicPi (MSI)
(If I'm not mistaken event id 6005 was already present again)
Ran SonciPi. Seemed to run fine.
After a while SonicPi behaves the same way.

Could Windows sleep mode be the cause of this crash? That's the only thing I can think of.

@gl33mer
Copy link
Author

gl33mer commented Feb 2, 2017

@llloret do work me :-)

@gl33mer
Copy link
Author

gl33mer commented Feb 2, 2017

Still. Crashing silently. No error notice. Splash screen. Then nothing.

@llloret
Copy link
Collaborator

llloret commented Feb 2, 2017 via email

@samaaron
Copy link
Collaborator

samaaron commented Feb 2, 2017

Possibly related: https://svn.boost.org/trac/boost/ticket/12137

@samaaron
Copy link
Collaborator

samaaron commented Feb 2, 2017

@llloret which version of Boost are we using for the Windows build?

@llloret
Copy link
Collaborator

llloret commented Feb 2, 2017 via email

@gl33mer
Copy link
Author

gl33mer commented Feb 2, 2017

@llloret Thank you.

@samaaron This is a bit deeper than my normal depth but it seems that issue relates (If I understood correctly) to the event log size maxing out. Mine also seems to have a limit of 20mb but is currently only ~3mb (I think). I also seem to have quite a few events with id 6005. But then again I've never used boost, etc.

@gl33mer
Copy link
Author

gl33mer commented Apr 17, 2017

I would assume not many people encounter this one.

:-(

May end up ordering a raspbPI

@samaaron
Copy link
Collaborator

Cc @bagong

@bagong
Copy link

bagong commented Apr 17, 2017 •
edited

@samaaron, I am following. The tragic thing is that we haven't had a case yet that allowed to reproduce the problem. It's either there on a certain system, or not... Once someobdy turns up who says: I had it, but after I did this and that it disappeared (or the other way round), we are back in the game. But worse: SC has moved on to boost 1.63 now, where the code in question is different, so even less chance that we find out what triggers this problem in certain environments.
To Sonic Pi users who bump into this: the same thing has been observed with vanilla SuperCollider, but it is exceedingly rare. If somebody feels up to trying a current pre-release SuperCollider build on their machine, we could try to see a) if the problem disappears with the boost update, or b) if a different version reveals a bit more about the reasons behind the problem.
And more generally: the first thing is always to delete the system log and reboot the machine. If somebody is willing to invest some time, I am happy to take her hand in trying to go through the steps. But no promise, unfortunately, that we can easily solve the problem.

@samaaron
Copy link
Collaborator

@bagong - thanks for this - is the sc with boost 1.63 released at this point it still in dev?

@bagong
Copy link

bagong commented Apr 17, 2017

Still in dev, and not clear yet when we will release. Some push for a quick release, others are sceptical...

@samaaron
Copy link
Collaborator

@gl33mer - could you try booting a vanilla version of supercollider? If that doesn't work - perhaps @bagong could let you have a pre-release of the new win supercollider to try out?

@llloret
Copy link
Collaborator

llloret commented Apr 17, 2017

As @bagong said, the trouble is finding his to reproduce it.

I agree that next step would be to test the 1.63, when possible.

@gl33mer
Copy link
Author

gl33mer commented Apr 18, 2017

@samaaron which version are you referring to as vanilla, 64bit 3.8 (no supernova)?

@bagong ty. I should erase the system log before trying? (you mean the event log? more instructions welcome.)

@bagong I'm willing to invest time in solving this. Will do my best to follow your instructions.

@gl33mer
Copy link
Author

gl33mer commented Apr 29, 2017

hmm...

@gl33mer
Copy link
Author

gl33mer commented May 11, 2017 

# Starting SuperCollider 2017-05-11 08:10:36
SC FFT global init: cosTable initialised.
Exception in World_New: boost::interprocess::intermodule_singleton initialization failed

Event log was cleared before attempting to boot sonic-pi.

current version still not working.

@gl33mer
Copy link
Author

gl33mer commented May 11, 2017

This from Stackoverflow -

"It's a bit weird, but here boost relies on Windows Event Logger. And if there is no event with ID = 6005. It throws an exception....
...The solution was just to add the event 6005 and all work again fine."

I did have more than one 6005 event before I erased the eventlog completely and a 6005 event has to be created.

This method using PowerShell for adding an event with id 6005 worked for me (eventcreate.exe can only create an event with id 0-1000 and LogEvent.exe that is mentioned elsewhere can't be found)

Sonic-Pi just booted.

I shall update.

@gl33mer
Copy link
Author

gl33mer commented May 11, 2017

Rebooted computer. Sonic Pi still boots.

@gl33mer
Copy link
Author

gl33mer commented May 12, 2017

After System event log has been erased - add a event with id 6005 like this:
In powershell:

$evt=new-object System.Diagnostics.Eventlog(“System”)
$evt.Source=”EventLog”
$evtNumber=6005
$evtDescription=”For SC boot”
$infoevent=[System.Diagnostics.EventLogEntryType]::Information
$evt.WriteEntry($evtDescription,$infoevent,$evtNumber)

now SonicPi should boot.

@gl33mer
Copy link
Author

gl33mer commented May 12, 2017

Is this closing?

@gl33mer
Copy link
Author

gl33mer commented May 16, 2017

@samaaron
Sonic-Pi has been stable with no problems since the above fix.
(Sonic Pi 2.11.1)
Not sure if this issue should be closed or kept open (for upstream Boost fix, etc.?).
Thanks.

@llloret
Copy link
Collaborator

llloret commented May 16, 2017 via email

@Rainer
Copy link

Rainer commented Jun 1, 2017

Hello everyone,

I had the same boot problem until 15 minutes ago. After installing SuperCollider separately, one of it's logfiles told me that it had a problem with my Focusrite Scarlett Solo Device. I deactivated the device, restarted Sonic Pi, and voilà: I am a happy listener to the db_haus drum sample now. ;-)

Hope this helps anyone!

Kind regards,

Rainer

@gl33mer
Copy link
Author

gl33mer commented Sep 15, 2017

Hey @Rainer

Sonic Pi is working consistently for you now?

I'm also using a Focusrite interface (2i2) . Disconnecting it got SonicPi running. But only once and then it's back to splash screen and crash.

This still in the SonicPi (scsynth) logs:

# Starting SuperCollider 2017-09-15 09:12:04
SC FFT global init: cosTable initialised.
Exception in World_New: boost::interprocess::intermodule_singleton initialization failed

@gl33mer
Copy link
Author

gl33mer commented Sep 15, 2017

This isn't a workable solution for me because I need the audio device for inputs/outputs etc.

I couldn't get it to work consistently and couldn't actually hear any sound off the on board audio.

@gl33mer
Copy link
Author

gl33mer commented Sep 15, 2017

I'm looking into possible upgrade on the Focusrite drivers.

@gl33mer
Copy link
Author

gl33mer commented Sep 15, 2017

No luck with updated drivers.

@samaaron
Copy link
Collaborator

Closing this here as it appears to be a duplicate of #959

Please update to v3.1 and see if that fixes your issues and if not, please do continue the conversation over at #959

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@llloret llloret

Labels
boot Windows
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@samaaron @Rainer @gl33mer @llloret @bagong