[SERVER-8388] scoped_db_conn_test threading issues Created: 29/Jan/13 Updated: 11/Jul/16 Resolved: 31/Jan/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 2.3.2 |
| Fix Version/s: | 2.4.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Eric Milkie | Assignee: | Randolph Tan |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Steps To Reproduce: | while (build/linux2/normal/mongo/scoped_db_conn_test) do true; done |
| Participants: |
| Description |
|
causing Nightly Linux 64 to sporadically fail. If you run scoped_db_conn_test repeatedly in a while loop, it doesn't even run for a minute before it crashes on shutdown:
|
| Comments |
| Comment by auto [ 31/Jan/13 ] |
|
Author: {u'date': u'2013-01-30T16:35:28Z', u'email': u'randolph@10gen.com', u'name': u'Randolph Tan'}Message: Made sure to wait for all listening threads to terminate before finishing one test case. |
| Comment by Randolph Tan [ 29/Jan/13 ] |
|
Problem1: handler->disconnected( p.get() ); because the main thread already died and called the destructor for the file local variable dummyHandler. Changing dummyHandler to become a heap variable seems to make this go away. Problem2: Likely related to Problem1 stacktraces show mutex desctructors being called from handleIncomingMsg. |