-
Notifications
You must be signed in to change notification settings - Fork 712
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
Reduce memory footprint of configuration parser #1102
Labels
Comments
frankmorgner
added a commit
to frankmorgner/OpenSC
that referenced
this issue
Jul 4, 2018
frankmorgner
added a commit
that referenced
this issue
Jul 11, 2018
frankmorgner
added a commit
to frankmorgner/OpenSC
that referenced
this issue
Jul 11, 2018
frankmorgner
added a commit
to frankmorgner/OpenSC
that referenced
this issue
Jul 11, 2018
frankmorgner
added a commit
to frankmorgner/OpenSC
that referenced
this issue
Jul 12, 2018
mouse07410
added a commit
to mouse07410/OpenSC
that referenced
this issue
Aug 7, 2018
…ng default PKCS11 library on MacOS)
dengert
added a commit
to dengert/OpenSC
that referenced
this issue
Aug 20, 2018
…nSC#1102 The scconf parser is changes to discard comments and blocks that are empty. Previously comments were saved in memory as well as empty blocks. Traditionally opensc.conf files have add many lines commented out or served as a man page for opensc.conf. c003f38 also addressed issue OpenSC#1102 by removing all but of a few lines to create a minimal opensc.conf file and an opensc.conf.example file. With this change a user could take the example opensc.conf with comments and use it as the opensc.conf as they have done on the past. c003f38 could be reverted so users would not see a major configuration change in the next release and still get the benefit of a small opensc.conf memory footprint. An opensc.conf file has been about 48K bytes, with 40K being comments. On branch jakuje-x41sec-merge Your branch is up-to-date with 'jakuje/x41sec-merge'. Changes to be committed: modified: src/scconf/parse.c
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Expected behaviour
Reasonable memory consumption.
Actual behaviour
pkcs11-tool --test --login
takes about 400 KB of memory, of which most memory is consumed byscconf_parse()
and friends (viastrdup()
).Steps to reproduce
valgrind --tool=massif pkcs11-tool --test --login
ms_print massif.out.*
Logs
The text was updated successfully, but these errors were encountered: