[SERVER-17593] Segfault in V8 when running Java driver tests Created: 14/Mar/15 Updated: 20/Mar/15 Resolved: 20/Mar/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | JavaScript |
| Affects Version/s: | 2.6.8 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Pawel | Assignee: | Ramon Fernandez Marina |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Linux 64-bit |
||
| Issue Links: |
|
||||||||||||||||
| Operating System: | ALL | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
running tests from java drivers, tag r2.13.0. Can reproduce this on every run. Server log before death:
No build options were specified for build. |
| Comments |
| Comment by Ramon Fernandez Marina [ 20/Mar/15 ] | ||||||||||
|
pawel, this looks like the same issue as Regards, | ||||||||||
| Comment by Asya Kamsky [ 16/Mar/15 ] | ||||||||||
|
Looks like you are building with
You need to build with --opt=off or you can build with gcc 4.8. | ||||||||||
| Comment by Pawel [ 16/Mar/15 ] | ||||||||||
|
Ramon, you are right, this problem only happens when I build the server myself. It does not happen on the distributed binary build. ldd has the same output for stock/custom built. P.S. Thanks for cleaning the ticket up | ||||||||||
| Comment by Ramon Fernandez Marina [ 14/Mar/15 ] | ||||||||||
|
Hi pawel, I've cleaned up the ticket. As you can see cloning is not a good idea, since JIRA won't let you update the fields in the ticket header (including the description). In the future is best to just open a new ticket. That being said, I'm not able to reproduce the behavior you describe. This is what I did:
I also tried without enabling test commands; some tests fail, but mongod does not crash. Can you please upload detailed instructions on how you're doing these runs so we can try to reproduce this issue on our end? It also seems you're running your own build, so it would be interesting to see if the you can reproduce the same crash with the official 2.6.8. Thanks, |