Displaying 20 results from an estimated 25271 matches for "allocated".
2010 Jun 23
2
"Hidden" memory leak
...file 'frame.c'
3308 bytes in 139 allocations in file 'pbx_config.c'
379223 bytes in 1940 allocations in file 'pbx.c'
434640 bytes in 36220 allocations in file 'astobj2.c'
392396 bytes in 6331 allocations in file 'event.c'
*3957027 *bytes allocated (23080 in caches) in 81858 allocations
Anoyone knows why the memory leak is not shown in the asterisk malloc
debug, and how can I figure what's causing it? The asterisk version is
1.6.2.9.
Thanks in advance.
Regards,
--
Ing. Miguel Molina
Grupo de Tecnolog?a
Millenium Phone Center
-----...
2006 Aug 12
1
Strategy pattern: comparing Context/Specify to Given/When/Then
...easier to use than
the CS terminology.
Using CS and GWT certainly helped me to understand the
inter-relationships between classes.
For example:
given "A cost allocation with a gross override amount of $5000 to cost
allocation 1 and the remainder to cost allocation 2"
when "the allocated amount is $5000"
then "the amount is allocated by cost allocation 1"
when "the allocated amount is $5001"
then "$5000 is allocated by cost allocation 1"
then "$1 is allocated by cost allocation 2"
*** Compared to ***
context "A cost all...
2017 Nov 14
2
RTCP + Stasis causing high memory consumption
...whole time
and can be stopped/started.
After compiling Asterisk with the MALLOC_DEBUG flag, when the problem
happened we could see this output with the most consuming files, using
"memory show summary" command:
# cat memory_show_summary_201711101144.log | sort -nr | head
3060904798 bytes allocated (431496 in caches) in 16185877 allocations
1467180225 bytes in 1647238 allocations in file stasis_channels.c
1217035109 bytes in 10229320 allocations in file json.c
240064732 bytes in 1765287 allocations in file stasis_message.c
56402000 bytes in 1762250 allocations in file taskproces...
2018 Jan 29
1
Panic: data stack: Out of memory when allocating bytes
Any idea what the problem could be? Is there anything more i could do
to encircle the problem? Or perhaps is the information i provided
uncomplete?
Am 25.01.2018 um 16:24 schrieb Thomas Robers:
> Hi,
>
> Am 24.01.2018 um 23:39 schrieb Josef 'Jeff' Sipek:
>> It looks like the binaries are stripped.? There should be a "debug"
>> package
>> you can
2018 Jan 24
2
Panic: data stack: Out of memory when allocating bytes
On Wed, Jan 24, 2018 at 18:55:47 +0100, Thomas Robers wrote:
> Am 23.01.2018 um 20:07 schrieb Josef 'Jeff' Sipek:
> > On Tue, Jan 23, 2018 at 14:03:27 -0500, Josef 'Jeff' Sipek wrote:
> > > On Tue, Jan 23, 2018 at 18:21:38 +0100, Thomas Robers wrote:
...
> > > 1. Do you have any idea what the imap process was doing at the time of the
> > >
2018 Jan 25
0
Panic: data stack: Out of memory when allocating bytes
Hi,
Am 24.01.2018 um 23:39 schrieb Josef 'Jeff' Sipek:
> It looks like the binaries are stripped. There should be a "debug" package
> you can install with symbol information. Then, the backtrace should be much
> more helpful.
I installed the debug package and the backtrace now is:
--- snip ---
(gdb) bt full
#0 0x00007f73f1386495 in raise () from /lib64/libc.so.6
No
2010 Nov 23
1
Sims 3 Color & Graphics Issues
I've been trying to install The Sims 3 for the last couple of days, and it hasn't been opening. Now that I've finally figured out what i've been doing wrong there's still a major problem. I've installed using playonlinux, and when i open (I use the launcher made by playonlinux, not the actual sims 3 launcher)The screen might turn white, but it always turns black before the
2016 Mar 23
4
UBSan, StringRef and Allocator.h
...I have the correct audience. Please CC more people as needed).
I have an UBSan failure in BumpPtrAllocatorImpl.Allocate.
The problem is that lld requests that we StringRef::copy an empty string. This passes a length of 0 to a BumpPtrAllocator. The BumpPtrAllocator happened to not have anything allocated yet so the CurPtr is nullptr, but given that we need 0 space we think we have enough space and return an allocation of size 0 at address nullptr. This therefore returns nullptr from Allocate, but that method is marked with LLVM_ATTRIBUTE_RETURNS_NONNULL and LLVM_ATTRIBUTE_RETURNS_NOALIAS, both of...
2019 Sep 03
2
SourceMgr vs EXPENSIVE_CHECKS
Hi,
I'm trying to build llvm (git monorepo) on Ubuntu 18.04 with
EXPENSIVE_CHECKS enabled and running into various errors compiling
SourceMgr.cpp, depending on which host compiler I use.
For example with GCC:
$ CC=gcc-8 CXX=g++-8 cmake -GNinja -DCMAKE_BUILD_TYPE=Debug
-DLLVM_ENABLE_EXPENSIVE_CHECKS=ON ~/git/llvm-project/llvm/ && ninja
...
[89/2690] Building CXX object
2019 Sep 03
2
SourceMgr vs EXPENSIVE_CHECKS
Hmm. What about the errors I quoted from using clang-7 (starting about
a third of the way down my email, sorry if they got kinda lost in all
the noise)?
Thanks,
Jay.
On Tue, 3 Sep 2019 at 20:00, David Blaikie <dblaikie at gmail.com> wrote:
>
> Looks to me like a bug in GCC's constexpr+_GLIBCXX_CONCEPT_CHECKS support. Small test case:
>
> $ g++-8 test.cpp -std=c++2a
2019 Oct 02
2
SourceMgr vs EXPENSIVE_CHECKS
I just ran into this today. Do we need to update our requirements on
libstdc++ version?
Jay, did you figure out a way around this?
On Wed, Sep 4, 2019 at 5:29 AM David Blaikie via llvm-dev
<llvm-dev at lists.llvm.org> wrote:
>
> It's a bug in libstdc++ - so if you have clang using libstdc++ (which it will by default, I think) then it's the same thing. You could try with
2016 Mar 23
3
UBSan, StringRef and Allocator.h
...udience. Please CC more people as needed).
>
> I have an UBSan failure in BumpPtrAllocatorImpl.Allocate.
>
> The problem is that lld requests that we StringRef::copy an empty string. This passes a length of 0 to a BumpPtrAllocator. The BumpPtrAllocator happened to not have anything allocated yet so the CurPtr is nullptr, but given that we need 0 space we think we have enough space and return an allocation of size 0 at address nullptr. This therefore returns nullptr from Allocate, but that method is marked with LLVM_ATTRIBUTE_RETURNS_NONNULL and LLVM_ATTRIBUTE_RETURNS_NOALIAS, both of...
2018 Dec 11
2
Using LLD to link against third-party libraries? How?
In my code here https://github.com/DragonOsman/currency_converter , I used C++17 and managed to get it to work (though I'm only using std::map::insert_or_assign() from C++17). And I'm using Windows, so I shouldn't use LDFLAGS or CXXFLAGS as environment variables. I'll use them directly on the compiler command line instead. The libraries I need to link against are
2008 Aug 17
1
Allocated Memory Warnings in Vista 32 bit with 4 GB (PR#12557)
...total allocation of 1535Mb: see help(memory.size)
>=20
I have been able to reproduce the situation several times. For example, wh=
at is curious is that a command like partial=3Dsample(data,1,T) may or may =
not produce a warning message. In the history, obviously 2.3MB is well bel=
ow the allocated 1535MB. I had been getting this error on my original larg=
er source data (1,000,000 observations), but since I am a new R user, it wa=
s not clear to me what these errors mean.
If you need the original source files, or have additional questions, please=
let me know. I am a certified .NET softw...
2018 Dec 11
3
Using LLD to link against third-party libraries? How?
Are you linking with a C++ compiler? A lot of those missing symbols
look like they come from the C++ standard library.
-David
Osman Zakir via llvm-dev <llvm-dev at lists.llvm.org> writes:
> @blubee blubeeme So what do you think? Got any ideas?
> ----------------------------------------------------------------------
> From: Osman Zakir <osmanzakir90
2016 Mar 23
0
UBSan, StringRef and Allocator.h
...CC more people as needed).
>>
>> I have an UBSan failure in BumpPtrAllocatorImpl.Allocate.
>>
>> The problem is that lld requests that we StringRef::copy an empty string. This passes a length of 0 to a BumpPtrAllocator. The BumpPtrAllocator happened to not have anything allocated yet so the CurPtr is nullptr, but given that we need 0 space we think we have enough space and return an allocation of size 0 at address nullptr. This therefore returns nullptr from Allocate, but that method is marked with LLVM_ATTRIBUTE_RETURNS_NONNULL and LLVM_ATTRIBUTE_RETURNS_NOALIAS, both of...
2018 Dec 12
2
Using LLD to link against third-party libraries? How?
I couldn't get it to build libcxx...
You need c++ and c++abi to compile c++ code.
On Wed, Dec 12, 2018, 07:01 Osman Zakir via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> LLVM on a Developer Command Prompt. The ones I want to fix first are the
> ones from Boost and Jinja2Cpp. I saw some from those as well.
>
> If there any standard library ones missing, could it be
2016 Mar 28
2
UBSan, StringRef and Allocator.h
...t; needed).
>>
>> I have an UBSan failure in BumpPtrAllocatorImpl.Allocate.
>>
>> The problem is that lld requests that we StringRef::copy an empty
>> string. This passes a length of 0 to a BumpPtrAllocator. The
>> BumpPtrAllocator happened to not have anything allocated yet so the CurPtr
>> is nullptr, but given that we need 0 space we think we have enough space
>> and return an allocation of size 0 at address nullptr. This therefore
>> returns nullptr from Allocate, but that method is marked
>> with LLVM_ATTRIBUTE_RETURNS_NONNULL and LLVM...
2016 Mar 23
0
UBSan, StringRef and Allocator.h
.... Please CC more people as needed).
>
> I have an UBSan failure in BumpPtrAllocatorImpl.Allocate.
>
> The problem is that lld requests that we StringRef::copy an empty string.
> This passes a length of 0 to a BumpPtrAllocator. The BumpPtrAllocator
> happened to not have anything allocated yet so the CurPtr is nullptr, but
> given that we need 0 space we think we have enough space and return an
> allocation of size 0 at address nullptr. This therefore returns nullptr
> from Allocate, but that method is marked with LLVM_ATTRIBUTE_RETURNS_NONNULL
> and LLVM_ATTRIBUTE_RETUR...
2006 Nov 05
0
[LLVMdev] Port succesful
Anton Korobeynikov pravi:
> Hello, Ziga.
>
>
>> VCPP throws a warning that class is previously declared as struct.
>> Either it must be struct everywhere or class everywhere.
>> Declaration uses struct, while the definition uses class.
>>
> Nice! However it will be better to do the opposite: have it struct
> everywhere. I'll fix this.
>