From: Florian J. <flo...@we...> - 2012-07-21 23:55:09
Attachments:
signature.asc
|
Hi jboogie noted on IRC (btw, someone still needs to set the topic, and add the MusE devs to chanserv's auto-OP-list) that MusE crashes, probably related to using simpledrums http://pastebin.com/X7mnPzfL i find this pretty strange; although no debug info was included, it turns out that MusE gets a SIGTERM in synti/libsynti/gui.cpp, line 69, (the ::read...). why a sigterm, and why there? can this happen, possible by some kind of paranoia-tool like SELinux etc? ("you're reading things you may read due to unix permissions, but you may NOT read due to my whitelist, so i'll kill you"?) or is this just a strange coincident, and just a random signal? if someone knows jboogie's email address, please tell me ;) greetings flo |
From: Tim E. R. <ter...@ro...> - 2012-07-22 00:54:20
|
On July 22, 2012 1:54:57 AM Florian Jung wrote: > Hi > > jboogie noted on IRC (btw, someone still needs to set the topic, and add > the MusE devs to chanserv's auto-OP-list) that MusE crashes, probably > related to using simpledrums > > http://pastebin.com/X7mnPzfL > > i find this pretty strange; although no debug info was included, it > turns out that MusE gets a SIGTERM in synti/libsynti/gui.cpp, line 69, > (the ::read...). > > why a sigterm, and why there? can this happen, possible by some kind of > paranoia-tool like SELinux etc? ("you're reading things you may read due > to unix permissions, but you may NOT read due to my whitelist, so i'll > kill you"?) or is this just a strange coincident, and just a random signal? > > if someone knows jboogie's email address, please tell me ;) > > greetings > flo Tried fresh Jack=128, simpledrums + midi track + standard audio out + save/reload. No problem here on this amd64 box. Also tried Reset Instr, Init Instr, and Local Off from Midi menu. I notice he's loading a song. It's got some sysex's in there unknown by MusE. They are "GM Reset" sysex's. I guess MusE recorded them at some point from external HW, or he added them. I don't think MusE sends them. Anyway it doesn't seem to be the problem. So we don't know exactly what's loading or playing. But it occurred to me that he may be running out of memory. It says "Program received signal SIGTERM, Terminated." I can testify that my OS regularly kicks apps out (terminate) when memory is close to full /especially/ when debugging, and that (I guess?) since MusE is usually the last thing run (esp when debugging), it usually kicks MusE out first. It's quite jarring sometimes, you don't expect it It took me a while to realize what was happening but I think that's what it was here. Tim. |
From: Tim E. R. <ter...@ro...> - 2012-07-22 02:01:23
|
On July 21, 2012 8:53:58 PM Tim E. Real wrote: > On July 22, 2012 1:54:57 AM Florian Jung wrote: > > Hi > > > > jboogie noted on IRC (btw, someone still needs to set the topic, and add > > the MusE devs to chanserv's auto-OP-list) that MusE crashes, probably > > related to using simpledrums > > > > http://pastebin.com/X7mnPzfL > > > > i find this pretty strange; although no debug info was included, it > > turns out that MusE gets a SIGTERM in synti/libsynti/gui.cpp, line 69, > > (the ::read...). > > > > why a sigterm, and why there? can this happen, possible by some kind of > > paranoia-tool like SELinux etc? ("you're reading things you may read due > > to unix permissions, but you may NOT read due to my whitelist, so i'll > > kill you"?) or is this just a strange coincident, and just a random > > signal? > > > > if someone knows jboogie's email address, please tell me ;) > > > > greetings > > flo > > Tried fresh Jack=128, simpledrums + midi track + standard audio out > + save/reload. > No problem here on this amd64 box. > Also tried Reset Instr, Init Instr, and Local Off from Midi menu. > > I notice he's loading a song. It's got some sysex's in there unknown by > MusE. They are "GM Reset" sysex's. I guess MusE recorded them at some point > from external HW, or he added them. I don't think MusE sends them. Anyway > it doesn't seem to be the problem. > So we don't know exactly what's loading or playing. > > But it occurred to me that he may be running out of memory. > It says "Program received signal SIGTERM, Terminated." > I can testify that my OS regularly kicks apps out (terminate) > when memory is close to full /especially/ when debugging, > and that (I guess?) since MusE is usually the last thing run > (esp when debugging), it usually kicks MusE out first. > It's quite jarring sometimes, you don't expect it > It took me a while to realize what was happening but I think > that's what it was here. My mistake, it just happened now. It's a kill not a term. The terminal just says 'killed'. > > Tim. > > |
From: Florian J. <flo...@we...> - 2012-07-22 12:06:07
Attachments:
signature.asc
|
Am 22.07.2012 02:53, schrieb Tim E. Real: > On July 22, 2012 1:54:57 AM Florian Jung wrote: >> Hi >> >> jboogie noted on IRC (btw, someone still needs to set the topic, and add >> the MusE devs to chanserv's auto-OP-list) that MusE crashes, probably >> related to using simpledrums >> >> http://pastebin.com/X7mnPzfL >> >> i find this pretty strange; although no debug info was included, it >> turns out that MusE gets a SIGTERM in synti/libsynti/gui.cpp, line 69, >> (the ::read...). >> >> why a sigterm, and why there? can this happen, possible by some kind of >> paranoia-tool like SELinux etc? ("you're reading things you may read due >> to unix permissions, but you may NOT read due to my whitelist, so i'll >> kill you"?) or is this just a strange coincident, and just a random signal? >> >> if someone knows jboogie's email address, please tell me ;) >> >> greetings >> flo > > Tried fresh Jack=128, simpledrums + midi track + standard audio out > + save/reload. > No problem here on this amd64 box. > Also tried Reset Instr, Init Instr, and Local Off from Midi menu. > > I notice he's loading a song. It's got some sysex's in there unknown by MusE. > They are "GM Reset" sysex's. I guess MusE recorded them at some point > from external HW, or he added them. I don't think MusE sends them. > Anyway it doesn't seem to be the problem. > So we don't know exactly what's loading or playing. > > But it occurred to me that he may be running out of memory. > It says "Program received signal SIGTERM, Terminated." > I can testify that my OS regularly kicks apps out (terminate) > when memory is close to full /especially/ when debugging, > and that (I guess?) since MusE is usually the last thing run > (esp when debugging), it usually kicks MusE out first. > It's quite jarring sometimes, you don't expect it > It took me a while to realize what was happening but I think > that's what it was here. > i don't think the OOM killer you're referring to sends out a SIGTERM (which is equivalent to kindly asking whether the process possibly wants to terminate in the near future). it sends a SIGKILL (and just deletes the process from the memory). anyway, adding MUCH more swap might clarify that. greetings flo > Tim. > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Lmuse-developer mailing list > Lmu...@li... > https://lists.sourceforge.net/lists/listinfo/lmuse-developer > |
From: Florian J. <flo...@we...> - 2012-07-22 12:06:15
Attachments:
signature.asc
|
Am 22.07.2012 02:53, schrieb Tim E. Real: > On July 22, 2012 1:54:57 AM Florian Jung wrote: >> Hi >> >> jboogie noted on IRC (btw, someone still needs to set the topic, and add >> the MusE devs to chanserv's auto-OP-list) that MusE crashes, probably >> related to using simpledrums >> >> http://pastebin.com/X7mnPzfL >> >> i find this pretty strange; although no debug info was included, it >> turns out that MusE gets a SIGTERM in synti/libsynti/gui.cpp, line 69, >> (the ::read...). >> >> why a sigterm, and why there? can this happen, possible by some kind of >> paranoia-tool like SELinux etc? ("you're reading things you may read due >> to unix permissions, but you may NOT read due to my whitelist, so i'll >> kill you"?) or is this just a strange coincident, and just a random signal? >> >> if someone knows jboogie's email address, please tell me ;) >> >> greetings >> flo > > Tried fresh Jack=128, simpledrums + midi track + standard audio out > + save/reload. > No problem here on this amd64 box. > Also tried Reset Instr, Init Instr, and Local Off from Midi menu. > > I notice he's loading a song. It's got some sysex's in there unknown by MusE. > They are "GM Reset" sysex's. I guess MusE recorded them at some point > from external HW, or he added them. I don't think MusE sends them. > Anyway it doesn't seem to be the problem. > So we don't know exactly what's loading or playing. > > But it occurred to me that he may be running out of memory. > It says "Program received signal SIGTERM, Terminated." > I can testify that my OS regularly kicks apps out (terminate) > when memory is close to full /especially/ when debugging, > and that (I guess?) since MusE is usually the last thing run > (esp when debugging), it usually kicks MusE out first. > It's quite jarring sometimes, you don't expect it > It took me a while to realize what was happening but I think > that's what it was here. > i don't think the OOM killer you're referring to sends out a SIGTERM (which is equivalent to kindly asking whether the process possibly wants to terminate in the near future). it sends a SIGKILL (and just deletes the process from the memory). anyway, adding MUCH more swap might clarify that. greetings flo > Tim. > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Lmuse-developer mailing list > Lmu...@li... > https://lists.sourceforge.net/lists/listinfo/lmuse-developer > |