[SERVER-319] segmentation fault, core dumped Created: 28/Sep/09  Updated: 20/Oct/09  Resolved: 17/Oct/09

Status: Closed
Project: Core Server
Component/s: Querying
Affects Version/s: 1.0.0
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: gf Assignee: Eliot Horowitz (Inactive)
Resolution: Cannot Reproduce Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

FreeBSD


Participants:

 Description   

Mon Sep 28 17:14:43 main.tvchannels Assertion failure d.moreJSObjs() db/instance.cpp 325
Mon Sep 28 17:14:43 Got signal: 11 (Segmentation fault: 11).
Mon Sep 28 17:14:43 Last op:

{ opid: 3, active: 1, secs_running: 0, op: "update", ns: "main.tvchannels", query: "", inLock: 1, client: "127.0.0.1:48048" }

Mon Sep 28 17:14:43 Got signal: 10 (Bus error: 10).
Mon Sep 28 17:14:43 Last op:

{ opid: 3, active: 1, secs_running: 0, op: "update", ns: "main.tvchannels", query: "", inLock: 1, client: "127.0.0.1:48048" }

Core dump: http://mirror.yatv.ru/mongod.core



 Comments   
Comment by Eliot Horowitz (Inactive) [ 28/Sep/09 ]

I can't reproduce on 1.1 nightly.
I think it was fixed.

Can you try on the current nightly.

Comment by gf [ 28/Sep/09 ]

My own driver. Yes, but I think that server have not to crash after bad queries DoS...

Comment by Eliot Horowitz (Inactive) [ 28/Sep/09 ]

what driver are you using?
seems like the root cause is a driver error.

Generated at Thu Feb 08 02:53:43 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.