---
### Author:  [@nsajko](https://discourse.julialang.org/u/nsajko)
#### Post date: [January 10, 2023, 7:32am UTC](https://discourse.julialang.org/t/why-does-each-bigfloat-allocate-a-big-string-in-addition-to-the-mpfr-big-float-object/92745/2 "2023-01-10T07:32:59Z")
Now that I think about the code, I guess the intent behind it is for the String object to hold the memory of the MPFR object, so there shouldn’t be any additional allocation? So I guess this is a bug in the allocation profiler?
Here’s a screenshot of the Julia allocation profiler in the Code editor:
---
### Author:  [@thofma](https://discourse.julialang.org/u/thofma)
#### Post date: [January 10, 2023, 8:02am UTC](https://discourse.julialang.org/t/why-does-each-bigfloat-allocate-a-big-string-in-addition-to-the-mpfr-big-float-object/92745/3 "2023-01-10T08:02:39Z")
> [@nsajko](#):
>
> Now that I think about the code, I guess the intent behind it is for the String object to hold the memory of the MPFR object, so there shouldn’t be any additional allocation?
Yes, there is no additional allocation (your interpretation of the `String` object is correct).
Why do you think there is a Bug in the allocation profiler?
---
### Author:  [@nsajko](https://discourse.julialang.org/u/nsajko)
#### Post date: [January 10, 2023, 8:16am UTC](https://discourse.julialang.org/t/why-does-each-bigfloat-allocate-a-big-string-in-addition-to-the-mpfr-big-float-object/92745/4 "2023-01-10T08:16:02Z")
> [@thofma](#):
>
> Why do you think there is a Bug in the allocation profiler?
Because two equal allocations are noted, both in the flamegraph and in the annotated source, instead of just one.
---
### Author:  [@thofma](https://discourse.julialang.org/u/thofma)
#### Post date: [January 10, 2023, 8:37am UTC](https://discourse.julialang.org/t/why-does-each-bigfloat-allocate-a-big-string-in-addition-to-the-mpfr-big-float-object/92745/5 "2023-01-10T08:37:23Z")
The `BigFloat` object is allocated and the `String` is allocated. Why should there be one?
---
### Author:  [@nsajko](https://discourse.julialang.org/u/nsajko)
#### Post date: [January 10, 2023, 8:58am UTC](https://discourse.julialang.org/t/why-does-each-bigfloat-allocate-a-big-string-in-addition-to-the-mpfr-big-float-object/92745/6 "2023-01-10T08:58:45Z")
_Before_ we exit the `BigFloat` constructor, there are already two allocations, as shown in both the flamegraph and the annotated source.
EDIT: I’m talking about this, specifically:
_Within_ the constructor, there are two equal allocations shown, and then the total is their sum. I guess this causes the profiler to double-count the BigFloat size?
---
### Author:  [@skleinbo](https://discourse.julialang.org/u/skleinbo)
#### Post date: [January 10, 2023, 9:46am UTC](https://discourse.julialang.org/t/why-does-each-bigfloat-allocate-a-big-string-in-addition-to-the-mpfr-big-float-object/92745/7 "2023-01-10T09:46:49Z")
> [@nsajko](#):
>
> _Before_ we exit the `BigFloat` constructor, there are already two allocations
Yes, because the `BigFloat` object is instantiated/allocated in the call to `_BigFloat`.
If you look at the allocation profile, you will find there are two kinds of allocations; the string and the `BigFloat` (although the profiler can’t figure out the type here and calls it `UnknownType`). As you can see, they are of different size. Play with `precision` and observe the string allocation change size. It isn’t doubly allocated though.
```julia-auto
Profile.Allocs.@profile for i in 1:10000000 BigFloat(;precision=2048) end
result = Profile.Allocs.fetch()
result = sort(result.allocs, by=x->x.size)
result[[begin,end]]
2-element Vector{Profile.Allocs.Alloc}:
Profile.Allocs.Alloc(Profile.Allocs.UnknownType, Base.StackTraces.StackFrame[ijl_gc_pool_alloc at libjulia-internal.1.8.dylib:?, ...], 48)
Profile.Allocs.Alloc(String, Base.StackTraces.StackFrame[ijl_alloc_string at libjulia-internal.1.8.dylib:?, ...], 256)
```
---
### Author:  [@nsajko](https://discourse.julialang.org/u/nsajko)
#### Post date: [January 10, 2023, 9:57am UTC](https://discourse.julialang.org/t/why-does-each-bigfloat-allocate-a-big-string-in-addition-to-the-mpfr-big-float-object/92745/8 "2023-01-10T09:57:25Z")
Ah, I thought the profiler was reporting allocation size, but I guess it’s only considering the number of allocations. The Code editor Julia plugin, I mean.