[#99115] [Ruby master Bug#17023] How to prevent String memory to be relocated in ruby-ffi — larskanis@...
Issue #17023 has been reported by larskanis (Lars Kanis).
22 messages
2020/07/10
[#99375] [Ruby master Feature#17055] Allow suppressing uninitialized instance variable and method redefined verbose mode warnings — merch-redmine@...
Issue #17055 has been reported by jeremyevans0 (Jeremy Evans).
29 messages
2020/07/28
[#101207] [Ruby master Feature#17055] Allow suppressing uninitialized instance variable and method redefined verbose mode warnings
— merch-redmine@...
2020/12/02
Issue #17055 has been updated by jeremyevans0 (Jeremy Evans).
[#101231] Re: [Ruby master Feature#17055] Allow suppressing uninitialized instance variable and method redefined verbose mode warnings
— Austin Ziegler <halostatue@...>
2020/12/03
What does this mean?
[ruby-core:99047] [Ruby master Bug#17008] JIT enabled on Windows can cause constant conhost pop-ups
From:
takashikkbn@...
Date:
2020-07-03 19:58:04 UTC
List:
ruby-core #99047
Issue #17008 has been updated by k0kubun (Takashi Kokubun). Assignee set to k0kubun (Takashi Kokubun) Status changed from Open to Feedback I have my own MinGW environment, but I've never observed such a behavior. Could you provide at least one way to reproduce the issue? I don't know of any GUI mingw32 application embedding Ruby 2.6+. ---------------------------------------- Bug #17008: JIT enabled on Windows can cause constant conhost pop-ups https://bugs.ruby-lang.org/issues/17008#change-86422 * Author: AWiederin (Aubrey Wiederin) * Status: Feedback * Priority: Normal * Assignee: k0kubun (Takashi Kokubun) * Backport: 2.5: UNKNOWN, 2.6: UNKNOWN, 2.7: UNKNOWN ---------------------------------------- I'm unsure of the min requirements for it to happen, but at least for ruby embedded in a gui mingw32 application, enabling JIT causes a conhost.exe popup for every gcc call, repeatedly stealing focus. The easy fix is to add the CREATE_NO_WINDOW flag to CreateChild calls in win32.c, line 1326 in particular. (Only somewhat related: It'd probably help performance if a single conhost could be shared among gcc calls, instead of letting Windows make a new one for each.) -- https://bugs.ruby-lang.org/ Unsubscribe: <mailto:[email protected]?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>