New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is This a Memory Leak? #14561
Comments
The invocation of @reshke I suppose we can remove it, what do you think? |
We can consider making magnetic disk's gpdb/src/backend/storage/smgr/smgr.c Line 51 in 4d7c52a
|
Fixed by #15091, close this issue. Please feel free to reopen this if the PR doesn't fix this problem completely. |
Need backport or not? |
…eenplum-db#15091) This PR is trying to fix the issue of greenplum-db#14561, we should not invoke mdinit() directly at the end of the function smgr_init_standard(). No more tests are needed, cause current tests are enough to cover.
What if
So there are still possible memory leaks. |
The |
So the MemoryContext should be allocated twice even with the same name? |
Maybe we should set the |
or might be better to just make |
@SmartKeyerror this part is still remaining to be addressed from this issue. |
Did I miss something? |
Bug Report
In
smgr.c:
NSmgr=1 && smgrsw[0].smgr_init = mdinit.
so mdinit will be called twice.
and in mdinit MdCxt will be alloced tiwce?
The text was updated successfully, but these errors were encountered: