Symptoms
Assume that you use SQL Server 2017. You notice that the core dump may be generated when you restart the SQL Server. In addition, you may receive the following diagnostic information:
Reason: ReasonId
Status: StatusId
Message: 0 <= m_currentCount
Stack:
IP Function
---------------- --------------------------------------
000055777bae169d malloc_usable_size+0x9d82d
000055777bae1277 malloc_usable_size+0x9d407
000055777ba2331e std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > std::__1::operator+<char, std::__1::char_traits<char>, std::__1::allocator<char> >(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > c
000055777bb305cb void google::protobuf::internal::arena_delete_object<google::protobuf::Message>(void*)+0x2edb
000055777ba67722 malloc_usable_size+0x238b2
Process: ProcessId- sqlservr
Thread: ThreadId (application thread 0x1d0)
Instance Id: InstanceId
Crash Id: CrashId
Build stamp: BuildStampId
Distribution: Ubuntu 16.04.6 LTS
Processors: ProcessorsId
Total Memory: 198486151168 bytes
Timestamp: DateTime
{
"reason": "ReasonId",
"processName": "sqlservr",
"pid": "11728",
"instanceId": "InstanceId",
"crashId": "CrashId",
"threadState": "0x00007f837bc556c0",
"threadId": "11893",
"libosThreadId": "0x1d0",
"buildStamp": "06d1c8d43553e575793a805281163952dd2d1f05a20764a17482e81ee902398c",
"status": "0x00000000",
"message": "0 <= m_currentCount",
"stack": [
"0x000055777bae24de",
"0x000055777bae1285",
"0x000055777ba2331e",
"0x000055777bb305cb",
"0x000055777ba67722"
],
"stackText": [
"malloc_usable_size+0x9e66e",
"malloc_usable_size+0x9d415",
"std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > std::__1::operator+<char, std::__1::char_traits<char>, std::__1::allocator<char> >(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > c",
"void google::protobuf::internal::arena_delete_object<google::protobuf::Message>(void*)+0x2edb",
"malloc_usable_size+0x238b2"
],
}
}
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Resolution
This issue is fixed in the following cumulative update for SQL Server:
About cumulative updates for SQL Server:
Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. Check out the latest cumulative updates for SQL Server:
References
Learn about the terminology that Microsoft uses to describe software updates.
