[SERVER-1390] Server crashes when running PyMongo test suite Created: 09/Jul/10 Updated: 12/Jul/16 Resolved: 12/Jul/10 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 1.5.5 |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | Michael Dirolf | Assignee: | Aaron Staple |
| Resolution: | Done | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
This has only been happening for very recent (last few days or so) server builds. The stack trace I get before the crash is this: [initandlisten] Fri Jul 9 17:47:48 connection accepted from 127.0.0.1:53721 #6
Showed to Mathias but he was hoping somebody else could take a look. Can consistently reproduce on my machine just by running the PyMongo test suite. Narrowed it down to running these two tests in succession, in particular: nosetests -v test.test_connection:TestConnection.test_network_timeout test.test_connection:TestConnection.test_tz_aware |
| Comments |
| Comment by Aaron Staple [ 12/Jul/10 ] |
|
The problem was that ClientCursors were being stored in shared_ptr objects, which is bad since ClientCursor objects can get freed when a yield happens. This storage model was in place before my changes, but I think with the changes we are yielding more and this triggered the recent failures. I added a ClientCursor pointer holder object and used that instead of shared_ptr. |
| Comment by auto [ 12/Jul/10 ] |
|
Author: {'login': 'astaple', 'name': 'Aaron', 'email': 'aaron@10gen.com'}Message: |
| Comment by Eliot Horowitz (Inactive) [ 10/Jul/10 ] |
|
I think this is from your change. |