Bug#914999: [libc6] Locking problems into libc6

2018-12-04 Thread Roman Savochenko
On 11/29/18 9:13 PM, Aurelien Jarno wrote: 1. For my program, I was needed to create extra locking about the function getaddrinfo(), but that resolved the problem only for my calls but for the external libraries like to MySQL, MariaDB I yet have the crashes and it cannot be fixed at all. Can

Bug#914999: [libc6] Locking problems into libc6

2018-11-29 Thread Roman Savochenko
Package: libc6 Version: 2.24 Severity: critical --- Please enter the report below this line. --- I have got already more signs of a problem into locking access to functions like to getaddrinfo(), by the macro __libc_lock_lock, which reproduced in multithreaded environments! 1. For my

Bug#914999: [libc6] Locking problems into libc6

2019-01-10 Thread Roman Savochenko
Hello, Aurelien On 12/30/18 7:49 PM, Aurelien Jarno wrote: On 2018-12-12 17:11, Roman Savochenko wrote: On 12/4/18 1:24 PM, Roman Savochenko wrote: On 11/29/18 9:13 PM, Aurelien Jarno wrote: 1. For my program, I was needed to create extra locking about the function getaddrinfo

Bug#914999: [libc6] Locking problems into libc6

2019-05-01 Thread Roman Savochenko
12.12.18 17:11, Roman Savochenko wrote: There are thousands of packages in different versions between Debian 8 and Debian 9. You have found it's not related to the kernel, but I fail to see how that shows it's a libc6 issue. For example when you have tried the kernel from Debian 9 in Debian 8

Bug#934080: [libc6] Significant degradation in the memory effectivity of the memory allocator

2019-08-16 Thread Roman Savochenko
Hello, Florian 14.08.19 15:07, Florian Weimer пише: Is there a way to reproduce your results easily? Upstream, we're looking for workloads which are difficult to handle for glibc's malloc and its default settings, so that we hopefully can improve things eventually. This way of the ready

Bug#934080: [libc6] Significant degradation in the memory effectivity of the memory allocator

2019-08-11 Thread Roman Savochenko
scada.org/wiki/Special:MyLanguage/Documents/How_to/Live_disk> of the automation Linux distributive <http://oscada.org/wiki/Special:MyLanguage/Sub-projects/Automation_Linux_distributive>. 07.08.19 09:09, Roman Savochenko wrote: I have a real-task environment on Debian 9 which consum

Bug#934080: [libc6] Significant degradation in the memory effectivity of the memory allocator

2019-08-07 Thread Roman Savochenko
Hello, Aurelien Jarno 06.08.19 23:57, Aurelien Jarno wrote: The live disks were started under VirtualBox 5.2, where the got data was measured by *top*. Can you details more precisely on you measure the memory used? Do you just get the line corresponding to the process you want to monitor?

Bug#934080: [libc6] Significant degradation in the memory effectivity of the memory allocator

2019-08-07 Thread Roman Savochenko
Hello, Florian 07.08.19 17:04, Florian Weimer wrote: * Roman Savochenko: Initial condition of the problem representing is a program in the single source code, built on-and for Debian 7, 8, 9, 10 with a result in the Live disks. I think glibc 2.13 as shipped by Debian was not built

Bug#934080: [libc6] Significant degradation in the memory effectivity of the memory allocator

2019-08-07 Thread Roman Savochenko
Hello, Carlos 07.08.19 16:54, Carlos O'Donell wrote: On Wed, Aug 7, 2019 at 2:12 AM Roman Savochenko mailto:romansavoche...@gmail.com>> wrote: So, we have got such regression, and I have to think about back-using Debian 7 on such sort dynamic environments and forget all ne

Bug#934080: [libc6] Significant degradation in the memory effectivity of the memory allocator

2019-08-06 Thread Roman Savochenko
Package: libc6 Version: 2.19, 2.24, 2.28 Severity: normal --- Please enter the report below this line. --- Initial condition of the problem representing is a program in the single source code, built on-and for Debian 7, 8, 9, 10 with a result in the Live disks. The program represents a