[SERVER-695] mutex assertion on shutdown is ugly Created: 03/Mar/10 Updated: 12/Jul/16 Resolved: 15/Mar/10 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 1.3.4 |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Aaron Staple | Assignee: | Aaron Staple |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Description |
|
Assertion failed: (!pthread_mutex_destroy(&m)), function ~mutex, file /opt/local/include/boost/thread/pthread/mutex.hpp, line 45. We allow mutexes to be held on shutdown, but boost doesn't like this. We've solved in the past by ensuring that boost mutexes that may be held at shutdown are never destroyed. We should use code to ensure that this the default whenever someone adds a new mutex. |
| Comments |
| Comment by auto [ 15/Mar/10 ] |
|
Author: {'login': 'astaple', 'name': 'Aaron', 'email': 'aaron@10gen.com'}Message: |
| Comment by auto [ 15/Mar/10 ] |
|
Author: {'login': 'astaple', 'name': 'Aaron', 'email': 'aaron@10gen.com'}Message: |
| Comment by auto [ 15/Mar/10 ] |
|
Author: {'login': 'astaple', 'name': 'Aaron', 'email': 'aaron@10gen.com'}Message: Revert "Revert " This reverts commit eb7cde3e751b02eae055a922af8985fe52c807fa. Conflicts: db/instance.h |
| Comment by auto [ 10/Mar/10 ] |
|
Author: {'login': 'astaple', 'name': 'Aaron', 'email': 'aaron@10gen.com'}Message: Revert " This reverts commit 714ec2fdc8e9c8dc1c2cdf5486afdbc185beef14. |
| Comment by auto [ 10/Mar/10 ] |
|
Author: {'login': 'astaple', 'name': 'Aaron', 'email': 'aaron@10gen.com'}Message: Revert " This reverts commit d9b3fbe120d49dd905055fefed4db98122172ca3. |
| Comment by auto [ 10/Mar/10 ] |
|
Author: {'login': 'astaple', 'name': 'Aaron', 'email': 'aaron@10gen.com'}Message: |
| Comment by auto [ 10/Mar/10 ] |
|
Author: {'login': 'astaple', 'name': 'Aaron', 'email': 'aaron@10gen.com'}Message: |