epam / epam/Indigo

Bingo SQLServer is stopped after inserting Molecule or Reaction

Open
#1,930 1 comment 0 reactions 0 assignees View on GitHub
Priority: High Severity: High User`s Feedback
Dominant language
C++
Stars
406
Forks
134
Avg merge
2d 11h
Merged PRs (30d)
24

Description

**Steps to Reproduce**
1. Save Molecule or Reaction to the table using DB Insert Scripts.

**Environment details:**
- SQLServer 2019
- Bingo 1.18.0
- Windows 10/11

**Actual behavior**
SQLServer 2019 is stopped when Molecule or Reaction is added to Table.
The data is not added to table. DB Insert Scripts uses Bingo.FlushOperations() procedure after insert query.

This Error Message is from Event Viewer Windows Log.
```
SQLServer is terminating because of fatal exception c0000005.
This error may be caused by an unhandled Win32 or C++ exception, or by an access violation encountered during exception handling.
Check the SQL error log for any related stack dumps or messages.
This exception forces SQL Server to shutdown. To recover from this error, restart the server (unless SQLAgent is configured to auto restart).
```
Attached is the SQL Log file:
[SQLDump0080.txt](https://github.com/epam/Indigo/files/15109867/SQLDump0080.txt)

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reviewing the attached SQLDump0080.txt and reproducing the failure with the DB Insert Scripts on SQL Server 2019. Focus on the insert followed by Bingo.FlushOperations(); done means the Molecule or Reaction row is inserted and SQL Server remains running without the fatal exception.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp, sql
Domain
databases
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.