Skip to content
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

Prefer safe memory management alternatives to plain "malloc/free" #172

Closed
hugbug opened this issue Feb 23, 2016 · 0 comments

Comments

Projects
None yet
1 participant
@hugbug
Copy link
Member

commented Feb 23, 2016

For intro see #88.

Places where malloc/free are used has become rare thanks to previous rework done for string management. Nonetheless there are still possibilities to further reduce the usage of malloc/free. In this issue such places should be identified and reworked in order to use safer memory management alternatives.

@hugbug hugbug added the refactoring label Feb 23, 2016

@hugbug hugbug added this to the Modern C++ milestone Feb 23, 2016

@hugbug hugbug referenced this issue Feb 23, 2016

Closed

Modern C++ #88

21 of 21 tasks complete

hugbug added a commit that referenced this issue Feb 23, 2016

#172: using vector of strings in SplitCommandLine
instead of dynamic array of c-style strings.

hugbug added a commit that referenced this issue Feb 23, 2016

#172: using vector of strings in command line parser
instead of dynamic array of c-style strings.

hugbug added a commit that referenced this issue Feb 23, 2016

#172: using CString in Maintenance-class
instead of c-style string.

hugbug added a commit that referenced this issue Feb 23, 2016

#172: use system objects directly
instead of dynamic creation, which were used to avoid system includes;
that’s become unimportant after using of precompiled headers.

hugbug added a commit that referenced this issue Feb 25, 2016

#172: using vector of strings in script controller
instead of dynamic array of c-style strings

hugbug added a commit that referenced this issue Feb 25, 2016

#172: use vectors in curses frontend on Windows
Replaced raw dynamic arrays with vectors in curses frontend on Windows.

hugbug added a commit that referenced this issue Feb 25, 2016

hugbug added a commit that referenced this issue Feb 26, 2016

#172: new class for cached segments
1) improve memory management; 2) removed dependency of module
“DownloadInfo.cpp” from article cache module “ArticleWriter.h”

hugbug added a commit that referenced this issue Feb 26, 2016

#172: use CString in Tokenzier
instead of raw C-style string.

hugbug added a commit that referenced this issue Feb 26, 2016

#172: use vector of Mutex in TlsSocket
instead of dynamic array of raw pointers.

@hugbug hugbug closed this Feb 26, 2016

hugbug added a commit that referenced this issue Mar 24, 2016

#172: 232c1a5: fixed: segment realloc not properly handled
and may cause program hanging on shutdown, with high cpu usage.

hugbug added a commit that referenced this issue Mar 26, 2016

#172: 232c1a5: fixed: segment alloc not always properly handled
and may cause program hanging on shutdown, with high cpu usage.

hugbug added a commit that referenced this issue Oct 9, 2017

#172: 232c1a5: fixed: segment realloc not properly handled
and may cause program hanging on shutdown, with high cpu usage.

hugbug added a commit that referenced this issue Oct 9, 2017

#172: 232c1a5: fixed: segment alloc not always properly handled
and may cause program hanging on shutdown, with high cpu usage.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.