search

sonic-pi-net / sonic-pi

Code. Music. Live.
https://sonic-pi.net
Other
10.82k stars 922 forks source link

Boot fail - win 10 x64 #1490

Closed gl33mer closed 6 years ago

gl33mer commented 7 years ago

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 commented 7 years ago

Hi, can you post the sonic pi logs? That would help in spotting the issue.

But the issue is because something is not found in the event logs, iirc, so clearing the event logs should make the problem worse, not better. Normally a reboot should make it work, since the boot event is what is missing in the non working case...

On Sun, 27 Nov 2016, 06:45 gl33mer, notifications@github.com wrote:

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 https://github.com/supercollider/supercollider/issues/2409(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?

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/samaaron/sonic-pi/issues/1490, or mute the thread https://github.com/notifications/unsubscribe-auth/ABLl8xh7ksGJekkAiZk4R7LaR73-IdoNks5rCScZgaJpZM4K9FFs .

gl33mer commented 7 years ago

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 commented 7 years ago

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 commented 7 years ago

Hi, I don't think this has to do with the issue that you mention. That should work fine after a reboot.

Perhaps @samaaron has some ideas to try and see what the issue is... Luis

gl33mer commented 7 years ago

@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 commented 7 years ago

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.

samaaron commented 7 years ago

Do you see an error message on a failed boot?

gl33mer commented 7 years ago

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 commented 7 years ago

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 commented 7 years ago
screen shot 2016-12-01 at 13 36 35
gl33mer commented 7 years ago

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 commented 7 years ago

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 commented 7 years ago

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 commented 7 years ago

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 commented 7 years ago

Thanks for this - it's very useful :)

Does supercollider crash in an identical fashion?

gl33mer commented 7 years ago

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 commented 7 years ago

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

samaaron commented 7 years ago

That would be useful - yes please.

gl33mer commented 7 years ago

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 commented 7 years ago

interesting - that doesn't look too good.

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

samaaron commented 7 years ago

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

llloret commented 7 years ago

Yes, I think so.

Can you have a look in the windows event log, as described in the SC bug report, and see if the boot event is missing? Luis

gl33mer commented 7 years ago

@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 commented 7 years ago

@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 commented 7 years ago

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

llloret commented 7 years ago

Ok, interesting. And does your issue happen every time, or only sometimes?

On Fri, 2 Dec 2016, 18:30 gl33mer, notifications@github.com wrote:

Ok. Thanks @llloret https://github.com/llloret . There is an event 6005 (more than one)

— You are receiving this because you were mentioned.

Reply to this email directly, view it on GitHub https://github.com/samaaron/sonic-pi/issues/1490#issuecomment-264526622, or mute the thread https://github.com/notifications/unsubscribe-auth/ABLl81iXC2dZsUwJKqkbUalCvf0Xj4-Mks5rEGO9gaJpZM4K9FFs .

gl33mer commented 7 years ago

It seems to be every time.

gl33mer commented 7 years ago

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.

llloret commented 7 years ago

Might well be. So far I haven't found a clear root cause...

gl33mer commented 7 years ago

Any new ideas? Tried 2.11.1 to no avail. Splash screen. Wait. Click on splash screen. Silent crash. No report.

When I search the computer for 'supercollider' - there seem to be boost interprocess directories with files labeled 'suppercollider server' , etc.

I assume it should be safe to delete these?

It's a funny predicament this :-)

(Off to use Unity3d for some spacial sound stuff...)

gl33mer commented 7 years ago

Just read this @samaaron tweet : "The SuperCollider developers have been really great to work with recently - friendly, helpful & responsive."

Maybe they can help? I have a feeling it's a shared problem. Am I the only one encountering this bug?

samaaron commented 7 years ago

@gl33mer - actually @llloret is a SuperCollider dev and has been helping a lot :)

Some thing just take time because they're not super obvious and easy to reproduce. It's also the holiday period!

gl33mer commented 7 years ago

ok :-)

No rush from here. Happy holidays.

gl33mer commented 7 years ago

Hello @llloret & @samaaron Hope the holidays were good to you :-)

I'd like to offer the SonicPi dev community a small bounty (of sorts): The new feature Sam has been working on (& the new found Erlang connection) - namely the live audio buffers, etc has tickled my creative bell.

If we can solve this bug - I'll set off to create a musical piece (album, ep, not sure) engineered to be performed live. I'll probably have a guitar and a microphone , though, who knows.

From this experience I hope to be able to create a short video tutorial series explaining what it takes to accomplish this with SonicPi.

I can already hear @llloret saying "why not just format the computer and create whatever you like?" And he's right. Also, to make things clear. This isn't a binding legal document but I'll do my best to achieve this goal (taking into account that it can and probably will change over time).

With much love for your hard work and this beautiful piece of software and paradigm.

gl33mer commented 7 years ago

Regarding the bug itself. I'm willing to work. Give me instructions and I'll do my best to follow. My hunch is that one of my installs of Supercollider at the time left something behind. Not sure what or which directory might hold it.

llloret commented 7 years ago

Hi, @gl33mer, that's a generous offer, indeed.

I was planning to continue debugging this issue next week, but we can start now... it would help a lot if you could post the current server logs that you are getting when it is not working. We can (re-)start working from there.

Let's see if we can get to the bottom of this. Thank you, Luis

samaaron commented 7 years ago

@gl33mer @llloret thank-you both so much for looking into this :-)

gl33mer commented 7 years ago

@llloret We do have time. No rush. As far as I know we're waiting for next release with that feature and I'm very rusty. I don't mean to put pressure here. Thanks for enabling this.

As for this bug: As far as I know I don't have a working version of either SonicPi or Supercollider on the computer at the moment.

So - next step. Install superCollider or sonicPi? (As far as I know both won't work) Which file exactly am I looking to post and where will I find it. (thanks for being patient)

As for the "piece" - KidBeyond started doing this with Live way back. I'll hopefully have two inputs going (one for guitar and one for vocals.) I'm thinking of something more Singer/Songwriter with an experimentalish tinge. We'll see where that goes. I'm open to any input. It will probably end up something completely different. But, who knows.

And truly. No rush. Just keeping this afloat :-)

@samaaron - I'm glad you approve.

llloret commented 7 years ago

@gl33mer, please install latest Sonic PI 2.11.1, and try with that.

gl33mer commented 7 years ago

@llloret Done.

I assume you mean server-output (log)?

Here it is (server-error is empty):

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

Booting Sonic Pi
----------------

Booting on Windows
Boot - Starting the SuperCollider server...
Failed to start server: Input/output error - TerminateProcess
C:/Program Files (x86)/Sonic Pi/app/server/native/win/ruby/lib/ruby/gems/2.3.0/gems/win32-process-0.8.3/lib/win32/process.rb:850:in `block in kill'
C:/Program Files (x86)/Sonic Pi/app/server/native/win/ruby/lib/ruby/gems/2.3.0/gems/win32-process-0.8.3/lib/win32/process.rb:797:in `each'
C:/Program Files (x86)/Sonic Pi/app/server/native/win/ruby/lib/ruby/gems/2.3.0/gems/win32-process-0.8.3/lib/win32/process.rb:797:in `kill'
C:/Program Files (x86)/Sonic Pi/app/server/sonicpi/lib/sonicpi/scsynthexternal.rb:260:in `rescue in boot_and_wait'
C:/Program Files (x86)/Sonic Pi/app/server/sonicpi/lib/sonicpi/scsynthexternal.rb:256:in `boot_and_wait'
C:/Program Files (x86)/Sonic Pi/app/server/sonicpi/lib/sonicpi/scsynthexternal.rb:353:in `boot_server_windows'
C:/Program Files (x86)/Sonic Pi/app/server/sonicpi/lib/sonicpi/scsynthexternal.rb:191:in `boot'
C:/Program Files (x86)/Sonic Pi/app/server/sonicpi/lib/sonicpi/scsynthexternal.rb:30:in `initialize'
C:/Program Files (x86)/Sonic Pi/app/server/sonicpi/lib/sonicpi/server.rb:70:in `new'
C:/Program Files (x86)/Sonic Pi/app/server/sonicpi/lib/sonicpi/server.rb:70:in `initialize'
C:/Program Files (x86)/Sonic Pi/app/server/sonicpi/lib/sonicpi/studio.rb:51:in `new'
C:/Program Files (x86)/Sonic Pi/app/server/sonicpi/lib/sonicpi/studio.rb:51:in `init_studio'
C:/Program Files (x86)/Sonic Pi/app/server/sonicpi/lib/sonicpi/studio.rb:44:in `initialize'
C:/Program Files (x86)/Sonic Pi/app/server/sonicpi/lib/sonicpi/lang/sound.rb:117:in `new'
C:/Program Files (x86)/Sonic Pi/app/server/sonicpi/lib/sonicpi/lang/sound.rb:117:in `block (2 levels) in included'
C:/Program Files (x86)/Sonic Pi/app/gui/qt/release/../../../../app/server/bin/sonic-pi-server.rb:155:in `new'
C:/Program Files (x86)/Sonic Pi/app/gui/qt/release/../../../../app/server/bin/sonic-pi-server.rb:155:in `<main>'
Server is exiting.
Shutting down GUI...
Goodbye :-)
gl33mer commented 7 years ago

scsynth.log has this:

# Starting SuperCollider 2017-02-02 02:35:14
SC FFT global init: cosTable initialised.
Exception in World_New: boost::interprocess::intermodule_singleton initialization failed
gl33mer commented 7 years ago

processes.log:

Clearing pids: ["7104"]

Clearing [7104]
  -- command "C:\Program Files (x86)\Sonic Pi\app\gui\qt\release\..\..\..\..\app\server\native\win\ruby\bin\ruby.exe"  --enable-frozen-string-literal -E utf-8 "C:\Program Files (x86)\Sonic Pi\app\gui\qt\release\..\..\..\..\app\server\bin\sonic-pi-server.rb" -u 4557 4558 4556 4556 4559
  -- removing C:/Users/Shva/AppData/Local/Temp/sonic-pi-pids/7104
  -- unable to get ProcTable info for: 7104
  -- process: 7104 not running

Finished clearing pids

Started [6252] [-] "C:\Program Files (x86)\Sonic Pi\app\gui\qt\release\..\..\..\..\app\server\native\win\ruby\bin\ruby.exe"  --enable-frozen-string-literal -E utf-8 "C:\Program Files (x86)\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/sonic-pi-pids/6252
gl33mer commented 7 years ago

gui.log:

[GUI] - Detecting port numbers...
[GUI] - GUI OSC listen port 4558
[GUI] -    port: 4558 [OK]
[GUI] - Server OSC listen port 4557
[GUI] -    port: 4557 [OK]
[GUI] - Server incoming OSC cues port 4559
[GUI] -    port: 4559 [OK]
[GUI] - Scsynth port 4556
[GUI] -    port: 4556 [OK]
[GUI] - Server OSC out port 4558
[GUI] - GUI OSC out port 4557
[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: 6252
[GUI] - waiting for Sonic Pi Server to boot...
............................................................
[GUI] - Critical error! Could not boot Sonic Pi Server.

[GUI] - Sonic Pi Server failed to start with this error message: 
      > Server Exception:
 Input/output error - TerminateProcess
[GUI] - UDP OSC Server no longer listening
gl33mer commented 7 years ago

debug.log is empty.

gl33mer commented 7 years ago

@llloret do work me :-)

gl33mer commented 7 years ago

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

llloret commented 7 years ago

Thanks for the info, the revealing bit is in scsynth.log line: Exception in World_New: boost::interprocess::intermodule_singleton initialization failed.

This is the problem that we are aware of, but so far there is not a clear idea of why it is happening. Let me have a a think and see how best to proceed to find out what the issue is.

samaaron commented 7 years ago

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

samaaron commented 7 years ago

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

llloret commented 7 years ago

1.61