On Sat, 2023-07-15 at 13:19 +0000, c.buhtz@posteo.jp wrote:
On 2023-07-11 01:34 BiT dev <python@altfeld-im.de> wrote
Impact: - Lower Performance (GUI startup time, diagnostics creation, systray icon creation)
Don't we use this approach only when using "--diagnostics"? Or are there other scenarios where we need this?
Currently the only other scenario is when loading the systray icon plugin at BiT Qt startup (so it would "only" prolong the startup duration of Bit Qt). This plugin needs to check if Qt5 is available and recognizes a system tray... I have a working solution now and do just a lot of testing in my different VMs by spawning a processs that reduces the soft limit for coredump file sizes via rlimit (basically a kernel system call) to zero: # To suppress the creation of coredump file on Linux # use resource.setrlimit() to set resource.RLIMIT_CORE’s soft limit to 0 # to prevent coredump file creation. # https://docs.python.org/3.10/library/resource.html#resource.RLIMIT_CORE # https://docs.python.org/3.10/library/resource.html#resource.setrlimit # See also the source code of the test.support.SuppressCrashReport() context manager: # if self.resource is not None: # try: # self.old_value = self.resource.getrlimit(self.resource.RLIMIT_CORE) # self.resource.setrlimit(self.resource.RLIMIT_CORE, # (0, self.old_value[1])) # except (ValueError, OSError): # pass # See "man 2 getrlimit" for more details