Re: [Denemo-devel] denemo causing session crash

[Bric]

On April 23, 2018 at 4:24 AM Richard Shann  wrote:On Sun, 2018-04-22 at 19:30 -0400, Bric wrote:On April 21, 2018 at 8:53 PM Bric  wrote: [...]The following extra detail could be relevant to  your development andtweaking, though i'm not 100% sure it's a denemo "mis-behavioral":It crashed on me twice on lilypond syntax error, during Print Viewrefresh."It crashed"? what did? what were the symptoms?Hi. Started replying several days ago, then system froze and I didn't have time to try to reconstruct what I had written.At this point I don't remember, but it's mostly what i wrote earlier, plus some extra observations:Denemo has triggered session crash of my (apparently less than stable Ubuntu), in particular operations, though i'm not even sure if they can be put under some common umbrella (not knowing the nuts & bolts) :1) Refreshing Print View (and maybe Playback view as well... can't remember for sure).  Often when there are lilypond syntax errors, but not always.2) On first run of the application after a crash, and attempting to use or just to open the Print View (when it starts refreshing itself, i suppose).3) On saving a lilypond export, when I hit "Save" in the file dialogueI don't remember any crashes while using just the editor (inputing, editing, saving there).  I may not be remembering a few other potentially useful details; sorry - might update later.  So, I'm actually getting stuff done using Denemo, but with the occasional crash interruptions (I make sure to hit "Ctrl+S" a LOT)  There is a purple error message in the preview window, at the top,saying the cursor was probably placed where the error is, in theeditor.That means that the LilyPond process emitted some error or warningmessage with a line and column reference to the LilyPond syntax, whichDenemo then tried to tie back to the place in the Denemo Display("editor") which corresponded to that bit of syntax. This fails if theline/col reference is not to something inside the music but in theheaders etc.My particular syntax errors were tying two notes [...] which were notthe same pitches [...]This will not cause LilyPond any problem (it happens a lot whileediting), LilyPond will issue a warning (and hence Denemo will try toposition the cursor) and not draw a tie.i THINK i've seen it crash before on lilypond syntax...You can get LilyPond to crash on syntax, but it would not be able tocause Denemo to crash, they are completely different Unix processes -if your O/S or hardware is faulty it might cause a system crash...All that Denemo is doing is its usual cycling round waiting for the O/Sto signal that the LilyPond process has terminated (and, in that casewhat it said) or if you have pressed a key or clicked a mouse or playedon your MIDI controller. It's doing that all the time, so unless theLilyPond process blew the whole system up there is nothing specialgoing on.The worst that can happen is the LilyPond hangs and then Denemocontinues waiting for it to finish. You can kill the LilyPond off viathe progress bar and/or by starting another typeset.Richard___Denemo-devel mailing listDenemo-devel@gnu.orghttps://lists.gnu.org/mailman/listinfo/denemo-devel
 

___
Denemo-devel mailing list
Denemo-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/denemo-devel

Re: [Denemo-devel] denemo causing session crash

[Richard Shann]

On Sun, 2018-04-22 at 19:30 -0400, Bric wrote:
> > On April 21, 2018 at 8:53 PM Bric  wrote: 
> > 
> > [...]
> 
> The following extra detail could be relevant to  your development and
> tweaking, though i'm not 100% sure it's a denemo "mis-behavioral":
> 
> It crashed on me twice on lilypond syntax error, during Print View
> refresh.

"It crashed"? what did? what were the symptoms?

>   There is a purple error message in the preview window, at the top,
> saying the cursor was probably placed where the error is, in the
> editor.

That means that the LilyPond process emitted some error or warning
message with a line and column reference to the LilyPond syntax, which
Denemo then tried to tie back to the place in the Denemo Display
("editor") which corresponded to that bit of syntax. This fails if the
line/col reference is not to something inside the music but in the
headers etc.


> 
> My particular syntax errors were tying two notes [...] which were not
> the same pitches [...]


This will not cause LilyPond any problem (it happens a lot while
editing), LilyPond will issue a warning (and hence Denemo will try to
position the cursor) and not draw a tie.

> 
> i THINK i've seen it crash before on lilypond syntax... 

You can get LilyPond to crash on syntax, but it would not be able to
cause Denemo to crash, they are completely different Unix processes -
if your O/S or hardware is faulty it might cause a system crash...
All that Denemo is doing is its usual cycling round waiting for the O/S
to signal that the LilyPond process has terminated (and, in that case
what it said) or if you have pressed a key or clicked a mouse or played
on your MIDI controller. It's doing that all the time, so unless the
LilyPond process blew the whole system up there is nothing special
going on.
The worst that can happen is the LilyPond hangs and then Denemo
continues waiting for it to finish. You can kill the LilyPond off via
the progress bar and/or by starting another typeset.

Richard

___
Denemo-devel mailing list
Denemo-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/denemo-devel

Re: [Denemo-devel] denemo causing session crash

[Bric]

On April 21, 2018 at 12:46 PM Richard Shann wrote:Thanks for these updatesRichardOn Sat, 2018-04-21 at 12:34 -0400, Bric wrote:On April 8, 2018 at 12:47 PM Richard Shann wrote:On Sun, 2018-04-08 at 07:15 -0400, Bric wrote:On April 7, 2018 at 9:58 PM Bric wrote: I occasionally experience a denemo crash on my Ubuntu 16.04 LTSwhich crashes my entire session, ending with the Ubuntu userloginscreen.This has happened several times, when I am refreshing the"TypesetMusic" window, after some particular change. And today ithappenedagain after the pop-up dialog "Restart Subsystem?", to which Ianswered "OK" and then got the crash. And then another crashlogout when I changed settings - unchecked "Spill notes to nextmeasure" and (i believe) clicked to refresh the Typeset Window.After that it crashed again, when I (re)started denemo (after Ideleted the auto-saved document), before any user activity,After that I logged back in, and it has run without crashing.It might be tricky to capturing the crash/debug messages here(notsure), since I get totally logged out, immediately (I could bewrong)Just thought I'd report it finally. This has been rare, suchthatI kept ignoring it.I am using Gnome metacity classicLinux  4.4.0-112-generic #135-Ubuntu SMP Fri Jan 1911:48:36UTC 2018 x86_64 x86_64 x86_64 GNU/LinuxHmm... This install/build of Denemo is becoming unusable for me.Just crashed again, when I started it and then invoked theplaybackwindow. I was trying to fix my lack of audio playback - itsuddenlywent silent in all windows that should produce playback sound.WhenI press "play" in the editor there are no errors, and the cursorismoving, as it normally does during playback, but there is nosound.I am suspecting the crashes to be related to the audiocomponent... Iused to use jack audio on other Ubuntu setups, but have not beenlately - using pulse. I remember crashes years ago, related tothewrong audio configurationNeedless to say (but i'm saying it nonetheless): the x sessioncrashis devastatingly disruptive; i don't remember experiencinganythinglike that before... an app bringing down the whole sessiogit-pulled and built a more recent snapshot a few days ago; it's beenrunning without crashing so far. Still a bunch of theories on thecrashes:1) My audio/midi settings, which i had tinkered with prior to thecrashes, were causing the audio subsystem to crash (and bring downthe session). The new install ported over my settings - but maybeexcluded the bad stuff?2) It is/was a combination of my particular, flawed Ubuntu install,which cold-freezes on me every now and then (mostly during certainfirefox browser activity), and i'm using retro metacity GNOME...which isn't the default windowing for latest Ubuntu. The freezes areconsistently freezes, though, and the session crashes were alwaysjust that... the symptoms never crossed over.3) Bad RAM ... not excluding that... but then, again, the new installhasn't crashed denemo --version:GNU Denemo version 2.2.7Gtk versions runtime: 3.18.9, compiled against: 3.18.9And this might further shed light:  Since I wrote the above i experienced session crashing caused by something other than denemo (and denemo wasn't even running):  My default image viewer that is launched by clicking on a jpeg from nautilus.  I *think* it's "Image Viewer" but not sure, since it crashes (couldn't find that info in my system settings)So, one more dot.  I dread to see my latest denemo build crash... so far no.(have had stable ubuntu's for many years - this is REALLY upsetting)The only similar thing I have seen is some failure between Gtk andXwhen re-sizing the Print View - the program hangs with Gtk waitingforX to respond. I've also got the X-interaction stuck when tellingtheI've had a temporary pop-up "updating" window "hour-glass"indefinitely, during Print View updates/refresh. But it seemsharmless, because I can dismiss it, and everything seems ok afterthat. (This is with my most recent install)debugger to stop the program at a point where a menu has just beenpopped up - the menu has grabbed the interaction and the only thingthat works is Ctrl-Alt-Fn5 which gives a login prompt. I login andthenkill off the denemo process at the command line and then use Ctrl-Alt-Fn7 to go back to my X-session.You may find it a good practice to *always* run Denemo from the gdbprompt - it runs just as well but if it crashes gdb will be able totell you where the crash happened.Also: My gnome session gives me some errors when I first log intoUbuntu, but i haven't had any "fatalities" until this one, soi'vebeen ignoring those. Perhaps it's time to address these - couldbesome weird combination of that plus denemo specifics.The re-start of the Audio subsystem can certainly cause a crash,that'swhy the dialog asks you before trying it. I don't have any realsuspicion that the problem lies with Denemo, unknown MIDI hardwareisnotoriously difficult to interact with safely, the manufacturer mayormay not have got it right. Currently my machine 

Re: [Denemo-devel] denemo causing session crash

[Bric]

On April 8, 2018 at 12:47 PM Richard Shann wrote:On Sun, 2018-04-08 at 07:15 -0400, Bric wrote:On April 7, 2018 at 9:58 PM Bric wrote: I occasionally experience a denemo crash on my Ubuntu 16.04 LTSwhich crashes my entire session, ending with the Ubuntu user loginscreen.This has happened several times, when I am refreshing the "TypesetMusic" window, after some particular change. And today it happenedagain after the pop-up dialog "Restart Subsystem?", to which Ianswered "OK" and then got the crash. And then another crashlogout when I changed settings - unchecked "Spill notes to nextmeasure" and (i believe) clicked to refresh the Typeset Window.After that it crashed again, when I (re)started denemo (after Ideleted the auto-saved document), before any user activity,After that I logged back in, and it has run without crashing.It might be tricky to capturing the crash/debug messages here (notsure), since I get totally logged out, immediately (I could bewrong)Just thought I'd report it finally. This has been rare, such thatI kept ignoring it.I am using Gnome metacity classicLinux  4.4.0-112-generic #135-Ubuntu SMP Fri Jan 19 11:48:36UTC 2018 x86_64 x86_64 x86_64 GNU/LinuxHmm... This install/build of Denemo is becoming unusable for me.Just crashed again, when I started it and then invoked the playbackwindow. I was trying to fix my lack of audio playback - it suddenlywent silent in all windows that should produce playback sound. WhenI press "play" in the editor there are no errors, and the cursor ismoving, as it normally does during playback, but there is no sound.I am suspecting the crashes to be related to the audio component... Iused to use jack audio on other Ubuntu setups, but have not beenlately - using pulse. I remember crashes years ago, related to thewrong audio configurationNeedless to say (but i'm saying it nonetheless): the x session crashis devastatingly disruptive; i don't remember experiencing anythinglike that before... an app bringing down the whole sessiogit-pulled and built a more recent snapshot a few days ago; it's been running without crashing so far. Still a bunch of theories on the crashes:1) My audio/midi  settings, which i had tinkered with prior to the crashes, were causing the audio subsystem to crash (and bring down the session). The new install ported over my settings - but maybe excluded the bad stuff?2) It is/was a combination of my particular, flawed Ubuntu install, which cold-freezes on me every now and then (mostly during certain firefox browser activity), and i'm using retro metacity GNOME... which isn't the default windowing for latest Ubuntu. The freezes are consistently freezes, though, and the session crashes were always just that... the symptoms never crossed over.3) Bad RAM ... not excluding that... but then, again, the new install hasn't crashed denemo --version:GNU Denemo version 2.2.7Gtk versions runtime: 3.18.9, compiled against: 3.18.9The only similar thing I have seen is some failure between Gtk and Xwhen re-sizing the Print View - the program hangs with Gtk waiting forX to respond. I've also got the X-interaction stuck when telling theI've had a temporary pop-up "updating" window "hour-glass" indefinitely, during Print View updates/refresh. But it seems harmless, because I can dismiss it, and everything seems ok after that. (This is with my most recent install)debugger to stop the program at a point where a menu has just beenpopped up - the menu has grabbed the interaction and the only thingthat works is Ctrl-Alt-Fn5 which gives a login prompt. I login and then kill off the denemo process at the command line and then use Ctrl-Alt-Fn7 to go back to my X-session.You may find it a good practice to *always* run Denemo from the gdbprompt - it runs just as well but if it crashes gdb will be able totell you where the crash happened.Also: My gnome session gives me some errors when I first log intoUbuntu, but i haven't had any "fatalities" until this one, so i'vebeen ignoring those. Perhaps it's time to address these - could besome weird combination of that plus denemo specifics.The re-start of the Audio subsystem can certainly cause a crash, that'swhy the dialog asks you before trying it. I don't have any realsuspicion that the problem lies with Denemo, unknown MIDI hardware isnotoriously difficult to interact with safely, the manufacturer may ormay not have got it right. Currently my machine randomly switchesbetween line out and headphones, but I'm pretty sure that is a hardwarefault that has developed. It happens a lot after resuming a session,but settles down for long periods after a while.Richard
 

___
Denemo-devel mailing list
Denemo-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/denemo-devel

Re: [Denemo-devel] denemo causing session crash

[Richard Shann]

On Sun, 2018-04-08 at 07:15 -0400, Bric wrote:
> > On April 7, 2018 at 9:58 PM Bric  wrote: 
> > 
> > I occasionally experience a denemo crash on my Ubuntu 16.04 LTS
> > which crashes my entire session, ending with the Ubuntu user login
> > screen.
> > This has happened several times, when I am refreshing the "Typeset
> > Music" window, after some particular change. And today it happened
> > again after the pop-up dialog "Restart Subsystem?", to which I
> > answered "OK" and then got the crash.  And then another crash
> > logout when I changed settings - unchecked "Spill notes to next
> > measure" and (i believe) clicked to refresh the Typeset Window.
> > After that it crashed again, when I (re)started denemo (after I
> > deleted the auto-saved document), before any user activity,
> > 
> > After that I logged back in, and it has run without crashing.
> > 
> > It might be tricky to capturing the crash/debug messages here (not
> > sure), since I get totally logged out, immediately (I could be
> > wrong)
> > 
> > Just thought I'd report it finally.  This has been rare, such that
> > I kept ignoring it.
> > 
> > I am using Gnome metacity classic
> > 
> > Linux  4.4.0-112-generic #135-Ubuntu SMP Fri Jan 19 11:48:36
> > UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
> 
>  Hmm... This install/build of Denemo is becoming unusable for me.
> 
> Just crashed again, when I started it and then invoked the playback
> window.   I was trying to fix my lack of audio playback - it suddenly
> went silent in all windows that should produce playback sound.   When
> I press "play" in the editor there are no errors, and the cursor is
> moving, as it normally does during playback, but there is no sound.
> 
> I am suspecting the crashes to be related to the audio component... I
> used to use jack audio on other Ubuntu setups, but have not been
> lately - using pulse.  I remember crashes years ago, related to the
> wrong audio configuration
> 
> Needless to say (but i'm saying it nonetheless):  the x session crash
> is devastatingly disruptive; i don't remember experiencing anything
> like that before... an app bringing down the whole session.

The only similar thing I have seen is some failure between Gtk and X
when re-sizing the Print View - the program hangs with Gtk waiting for
X to respond. I've also got the X-interaction stuck when telling the
debugger to stop the program at a point where a menu has just been
popped up - the menu has grabbed the interaction and the only thing
that works is Ctrl-Alt-Fn5 which gives a login prompt. I login and then
 kill off the denemo process at the command line and then use Ctrl-Alt-
Fn7 to go back to my X-session.

You may find it a good practice to *always* run Denemo from the gdb
prompt - it runs just as well but if it crashes gdb will be able to
tell you where the crash happened.
> 
> Also:  My gnome session gives me some errors when I first log into
> Ubuntu, but i haven't had any "fatalities" until this one, so i've
> been ignoring those.  Perhaps it's time to address these - could be
> some weird combination of that plus denemo specifics.

The re-start of the Audio subsystem can certainly cause a crash, that's
why the dialog asks you before trying it. I don't have any real
suspicion that the problem lies with Denemo, unknown MIDI hardware is
notoriously difficult to interact with safely, the manufacturer may or
may not have got it right. Currently my machine randomly switches
between line out and headphones, but I'm pretty sure that is a hardware
fault that has developed. It happens a lot after resuming a session,
but settles down for long periods after a while.

Richard



___
Denemo-devel mailing list
Denemo-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/denemo-devel

Re: [Denemo-devel] denemo causing session crash

[Bric]

On April 7, 2018 at 9:58 PM Bric  wrote:  I occasionally experience a denemo crash on my Ubuntu 16.04 LTS which crashes my entire session, ending with the Ubuntu user login screen.This has happened several times, when I am refreshing the "Typeset Music" window, after some particular change. And today it happened again after the pop-up dialog "Restart Subsystem?", to which I answered "OK" and then got the crash.  And then another crash logout when I changed settings - unchecked "Spill notes to next measure" and (i believe) clicked to refresh the Typeset Window. After that it crashed again, when I (re)started denemo (after I deleted the auto-saved document), before any user activity,After that I logged back in, and it has run without crashing.It might be tricky to capturing the crash/debug messages here (not sure), since I get totally logged out, immediately (I could be wrong)Just thought I'd report it finally.  This has been rare, such that I kept ignoring it.I am using Gnome metacity classicLinux  4.4.0-112-generic #135-Ubuntu SMP Fri Jan 19 11:48:36 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Hmm... This install/build of Denemo is becoming unusable for me. Just crashed again, when I started it and then invoked the playback window.   I was trying to fix my lack of audio playback - it suddenly went silent in all windows that should produce playback sound.   When I press "play" in the editor there are no errors, and the cursor is moving, as it normally does during playback, but there is no sound.I am suspecting the crashes to be related to the audio component... I used to use jack audio on other Ubuntu setups, but have not been lately - using pulse.  I remember crashes years ago, related to the wrong audio configurationNeedless to say (but i'm saying it nonetheless):  the x session crash is devastatingly disruptive; i don't remember experiencing anything like that before... an app bringing down the whole session.Also:  My gnome session gives me some errors when I first log into Ubuntu, but i haven't had any "fatalities" until this one, so i've been ignoring those.  Perhaps it's time to address these - could be some weird combination of that plus denemo specifics.___ Denemo-devel mailing list Denemo-devel@gnu.org https://lists.gnu.org/mailman/listinfo/denemo-devel 
 

___
Denemo-devel mailing list
Denemo-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/denemo-devel

[Denemo-devel] denemo causing session crash

[Bric]

I occasionally experience a denemo crash on my Ubuntu 16.04 LTS which crashes my entire session, ending with the Ubuntu user login screen.This has happened several times, when I am refreshing the "Typeset Music" window, after some particular change. And today it happened again after the pop-up dialog "Restart Subsystem?", to which I answered "OK" and then got the crash.  And then another crash logout when I changed settings - unchecked "Spill notes to next measure" and (i believe) clicked to refresh the Typeset Window. After that it crashed again, when I (re)started denemo (after I deleted the auto-saved document), before any user activity, After that I logged back in, and it has run without crashing.It might be tricky to capturing the crash/debug messages here (not sure), since I get totally logged out, immediately (I could be wrong)Just thought I'd report it finally.  This has been rare, such that I kept ignoring it.I am using Gnome metacity classicLinux  4.4.0-112-generic #135-Ubuntu SMP Fri Jan 19 11:48:36 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
 

___
Denemo-devel mailing list
Denemo-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/denemo-devel