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
ns-slapd double free or corruption crash #1480
Comments
Comment from lkrispen (@elkris) at 2015-04-17 17:58:19 I wrote a lib389 test and got the following crash: Core was generated by `./ns-slapd -D /root/389TEST/install/etc/dirsrv/slapd-standalone -i /root/389TES'. This looks very close to the customer crash |
Comment from lkrispen (@elkris) at 2015-04-17 18:40:01 attachment |
Comment from lkrispen (@elkris) at 2015-04-17 18:52:05 with the attached test script I did get a crash in 5 out of 10 runs |
Comment from lkrispen (@elkris) at 2015-05-12 14:27:59 attachment |
Comment from lkrispen (@elkris) at 2015-05-12 14:28:39 attachment |
Comment from lkrispen (@elkris) at 2015-05-12 14:34:24 attachment |
Comment from rmeggins (@richm) at 2015-05-12 19:52:38
Should this be "env" instead of "priv"? |
Comment from lkrispen (@elkris) at 2015-05-12 20:27:19 well it is of type 'struct dblayer_private_env *', so I called it priv, but maybe it could be penv |
Comment from rmeggins (@richm) at 2015-05-12 21:52:18 Replying to [comment:9 elkris]:
Ok. I was just confused because everywhere DB_OPEN is used, the first argument is pENV or mypENV, and here the argument is env instead of priv:
If it should be priv for the first definition of DB_OPEN, that's fine. |
Comment from nhosoi (@nhosoi) at 2015-06-04 01:16:12 git patch file (1.2.11 branch) -- fixing a coverity defect |
Comment from nhosoi (@nhosoi) at 2015-06-15 22:06:36 This issue is taken care in 1.2.11. Closing this ticket. Thanks, Ludwig! |
Comment from lkrispen (@elkris) at 2017-02-11 23:06:44 Metadata Update from @elkris:
|
Cloned from Pagure issue: https://pagure.io/389-ds-base/issue/48149
ds crashes occasionally hen performing a cn=monitor search.
his bug was reported in bz1203338, details there.
The core issue is in libdb, see: bz 1211871, but it could eventually fixed in DS by prebvening db_open calls and memp_stat calls to run in parallel
The text was updated successfully, but these errors were encountered: