Issue Details (XML | Word | Printable)

Key: CORE-5863
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Vlad Khorsun
Reporter: Vlad Khorsun
Votes: 0
Watchers: 2
Operations

If you were logged in you would be able to see more operations.
Firebird Core

Classic process crashes when client disconnected

Created: 01/Jul/18 02:52 PM   Updated: 01/Aug/18 05:54 AM
Component/s: Engine
Affects Version/s: 4.0 Alpha 1, 3.0.3
Fix Version/s: 3.0.4, 4.0 Beta 1

QA Status: Cannot be tested


 Description  « Hide
The Classic process crashes few times on our test machine. All crash dumps shows the same:

     000000000072f8b0() Unknown
> firebird.exe!SRVR_multi_thread(0x000007fe00000001, 55200) Line 1730 C++
     firebird.exe!WinMain(0x0000000000463d4f, 0x0000000000000000, 0x0000000000000000, 0) Line 295 C++
     firebird.exe!__tmainCRTStartup() Line 547 C
     kernel32.dll!BaseThreadInitThunk() Unknown
     ntdll.dll!RtlUserThreadStart() Unknown

The crash happens at the very end of SRVR_multi_thread:

  1720: }
  1721: catch (const Exception&)
  1722: {
  1723: // Some kind of unhandled error occurred during server setup. In lieu
  1724: // of anything we CAN do, log something (and we might be so hosed
  1725: // we can't log anything) and give up.
  1726: // The likely error here is out-of-memory.
  1727: gds__log("SRVR_multi_thread: error during startup, shutting down");
  1728: }
  1729: --cntServers;
0000000140030389 or rax,0FFFFFFFFFFFFFFFFh
000000014003038D lock xadd qword ptr [cntServers (01400C7590h)],rax
  1730: }
0000000140030396 mov rcx,qword ptr [mainPortRef]
000000014003039E test rcx,rcx
00000001400303A1 je SRVR_multi_thread+68Ah (01400303AAh)
00000001400303A3 mov rax,qword ptr [rcx]
00000001400303A6 call qword ptr [rax+8] <<<<<<<<<< HERE
00000001400303A9 nop

mainPortRef contains pointer to the already released port instance with reference count of zero.


 All   Comments   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
There are no comments yet on this issue.