{"action":"created","issue":{"url":"https://api.github.com/repos/Hurleyworks/JuceApp/issues/2","labels_url":"https://api.github.com/repos/Hurleyworks/JuceApp/issues/2/labels{/name}","comments_url":"https://api.github.com/repos/Hurleyworks/JuceApp/issues/2/comments","events_url":"https://api.github.com/repos/Hurleyworks/JuceApp/issues/2/events","html_url":"https://github.com/Hurleyworks/JuceApp/pull/2","id":56333515,"number":2,"title":"For some reason in juce it seems that all signals must be re-registred ","user":{"login":"KjellKod","id":331742,"avatar_url":"https://avatars.githubusercontent.com/u/331742?v=3","gravatar_id":"","url":"https://api.github.com/users/KjellKod","html_url":"https://github.com/KjellKod","followers_url":"https://api.github.com/users/KjellKod/followers","following_url":"https://api.github.com/users/KjellKod/following{/other_user}","gists_url":"https://api.github.com/users/KjellKod/gists{/gist_id}","starred_url":"https://api.github.com/users/KjellKod/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/KjellKod/subscriptions","organizations_url":"https://api.github.com/users/KjellKod/orgs","repos_url":"https://api.github.com/users/KjellKod/repos","events_url":"https://api.github.com/users/KjellKod/events{/privacy}","received_events_url":"https://api.github.com/users/KjellKod/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":7,"created_at":"2015-02-03T04:47:44Z","updated_at":"2015-02-03T15:20:56Z","closed_at":"2015-02-03T10:54:37Z","pull_request":{"url":"https://api.github.com/repos/Hurleyworks/JuceApp/pulls/2","html_url":"https://github.com/Hurleyworks/JuceApp/pull/2","diff_url":"https://github.com/Hurleyworks/JuceApp/pull/2.diff","patch_url":"https://github.com/Hurleyworks/JuceApp/pull/2.patch"},"body":"re-registration per thread doesn't hurt in either case.   Ive tested this with 50ms or shorter interval and it seems to work for SIGTERM, SIGABRT, AccessViolation \r\n\r\nHopefully this was the last issue. Please let me know if you find more. \r\n\r\n"},"comment":{"url":"https://api.github.com/repos/Hurleyworks/JuceApp/issues/comments/72668472","html_url":"https://github.com/Hurleyworks/JuceApp/pull/2#issuecomment-72668472","issue_url":"https://api.github.com/repos/Hurleyworks/JuceApp/issues/2","id":72668472,"user":{"login":"Hurleyworks","id":8120255,"avatar_url":"https://avatars.githubusercontent.com/u/8120255?v=3","gravatar_id":"","url":"https://api.github.com/users/Hurleyworks","html_url":"https://github.com/Hurleyworks","followers_url":"https://api.github.com/users/Hurleyworks/followers","following_url":"https://api.github.com/users/Hurleyworks/following{/other_user}","gists_url":"https://api.github.com/users/Hurleyworks/gists{/gist_id}","starred_url":"https://api.github.com/users/Hurleyworks/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Hurleyworks/subscriptions","organizations_url":"https://api.github.com/users/Hurleyworks/orgs","repos_url":"https://api.github.com/users/Hurleyworks/repos","events_url":"https://api.github.com/users/Hurleyworks/events{/privacy}","received_events_url":"https://api.github.com/users/Hurleyworks/received_events","type":"User","site_admin":false},"created_at":"2015-02-03T15:20:56Z","updated_at":"2015-02-03T15:20:56Z","body":">\r\n> Maybe an \"unknown\" exception should just be totally ignored by g3log?\r\n> (maybe adding a LOG(WARNING)).\r\n> That should have fixed this for both Juce and your current 3rdpart\r\n> library.\r\n\r\n\r\nThat sounds like a good plan to me.\r\n\r\nUnless I figure out a way to make this safe, which I thought I had, I will\r\n> make the vectored exception handling an option that is by default disabled.\r\n\r\n\r\nYes, I was going to suggest that too.\r\n\r\nOn Tue, Feb 3, 2015 at 10:06 AM, Kjell Hedstrom <notifications@github.com>\r\nwrote:\r\n\r\n>\r\n> > On Feb 3, 2015, at 7:52 AM, Steve Hurley <notifications@github.com>\r\n> wrote:\r\n> >\r\n> > Comment out the line to install\r\n> > > AddVectoredExceptionHandler\r\n> >\r\n> >\r\n> > That seems to fix everything Whew! :)\r\n>\r\n> I suspected as much. Glad to hear we have a short-cut fix.\r\n>\r\n> Unless I figure out a way to make this safe, which I thought I had, I will\r\n> make the vectored exception handling an option that is by default disabled.\r\n>\r\n> There are two really annoying things here:\r\n> 1) exceptions seems to be used in windows frameworks as a \"means of\r\n> communication\" rather than an \"exceptional and bad event\".\r\n> I can't do anything about this unfortunate practice except maybe curse\r\n> Java influence and some teeth gnashing.\r\n>\r\n> 2) I was sure that when I fixed it for Juce it actually took care of this.\r\n> So that an exception could propagate past g3log.\r\n> I will revise this code and see how it should be handled.\r\n>\r\n>\r\n> A potential fix\r\n> Maybe an \"unknown\" exception should just be totally ignored by g3log?\r\n> (maybe adding a LOG(WARNING)).\r\n>\r\n> That should have fixed this for both Juce and your current 3rdpart\r\n> library.\r\n>\r\n> Does that sound OK?=\r\n>\r\n> —\r\n> Reply to this email directly or view it on GitHub\r\n> <https://github.com/Hurleyworks/JuceApp/pull/2#issuecomment-72665979>.\r\n>\r\n\r\n\r\n\r\n-- \r\n-Steve\r\nhttp://www.hurleyworks.com"}}