Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-23072

Missing stack trace when mongod crashes with heap corruption

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Diagnostics
    • None
    • Fully Compatible
    • ALL
    • Platforms 12 (04/01/16), Platforms 13 (04/22/16)

      In evergreen we had a failure of csrs_upgrade_during_count.js where a mongod crashed with the following error:

      [js_test:csrs_upgrade_during_count] 2016-03-09T03:16:01.447+0000 d20010| 2016-03-09T03:16:01.447+0000 I CONTROL  [conn20] *** C runtime error: HEAP CORRUPTION DETECTED: after Normal block (#4002541) at 0x0000000001E2BC60., terminating
[js_test:csrs_upgrade_during_count] 2016-03-09T03:16:01.447+0000 d20010| 2016-03-09T03:16:01.447+0000 I -        [conn20] Fatal Assertion 17006
[js_test:csrs_upgrade_during_count] 2016-03-09T03:16:01.457+0000 d20010| 2016-03-09T03:16:01.457+0000 I CONTROL  [conn20] *** unhandled exception 0x80000003 at 0x000007FEFD7131F2, terminating
[js_test:csrs_upgrade_during_count] 2016-03-09T03:16:01.457+0000 d20010| 2016-03-09T03:16:01.457+0000 I CONTROL  [conn20] *** stack trace for unhandled exception:

      The lack of a stack trace makes it difficult to debug what actually went wrong.

      sharding_WT failed on windows-64-2k8-debug

      csrs_upgrade_during_count.js - Logs | History

            Assignee:
            mark.benvenuto@mongodb.com Mark Benvenuto
            Reporter:
            charlie.swanson@mongodb.com Charlie Swanson
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: