New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Firebird service stops with c0000005 error when more then 3-5 users connect to database. [CORE3655] #4005
Comments
Modified by: Dmitry Putincev (aektann)security: Developers [ 10012 ] => |
Commented by: Dmitry Putincev (aektann) dr.Watson dump and log |
Modified by: Dmitry Putincev (aektann)Attachment: drwatson.zip [ 12041 ] |
Commented by: @dyemanov Please try the latest v2.1.5 snapshot buld, it should have the issue fixed. |
Commented by: Dmitry Putincev (aektann) Yes, we've tried latest v.21.5-18451 with the same errors too.... |
Commented by: Dmitry Putincev (aektann) There was an option for dr.Watson to append current memory damp, so attached one consists of both FB 2.1.5 and 2.1.3 records. |
Commented by: Dmitry Putincev (aektann) Has anyone faced issues between firebird and Kaspersky antivirus installed on same compuer? We found some simular cases in 1C sofware support, caused by KAV. |
Commented by: @hvlad > There was an option for dr.Watson to append current memory damp, so attached one consists of both FB 2.1.5 and 2.1.3 records. Put corresponding fbserver.pdb file near fbserver.exe, clean up current drWatson's log and give us something more usable for analysys... |
Commented by: @hvlad I also confirm that issue from user.dmp should be fixed in 2.1.5 Also, consider upgrade to 2.5.1 as it have no suspicious code from 2.1 |
Commented by: Dmitry Putincev (aektann) Update on version 2.1.5 has solved the issue. Requiest might be closed. |
Modified by: @pcisarstatus: Resolved [ 5 ] => Closed [ 6 ] |
Modified by: @pavel-zotovQA Status: No test |
Submitted by: Dmitry Putincev (aektann)
Duplicates CORE3050
Duplicates CORE3409
Attachments:
drwatson.zip
Firebird service stops with c0000005 error. Looking in dr.Watson damp logs most of times we found that one of server threads raised an exception inside memove or rtlLeaveCriticalSection functions.
The text was updated successfully, but these errors were encountered: