QGIS crashes using QSqlDatabase connecting to PostGIS

[qgib]

Author Name: Attila Peller (@atisnz)
Original Redmine Issue: 21401
Affected QGIS version: 3.4.4
Redmine category:data_provider/postgis

---

We have a plugin which connects to both MSSQL and Postgis database. The plugin processes data from MSSQL and visualise them in QGis and stores results on Postgis. QGis regulary crashes with the same error blaming qsqlpsql.dll and leaves an event log behind.

The event log says:
Faulting application name: qgis-bin.exe, version: 0.0.0.0, time stamp: 0x5c4bcf50
Faulting module name: qsqlpsql.dll, version: 5.11.2.0, time stamp: 0x5b99eaa0
Exception code: 0xc000041d
Fault offset: 0x0000000000002805
Faulting process id: 0x12f0
Faulting application start time: 0x01d4ce23e728a0b9
Faulting application path: C:\OSGEO42\bin\qgis-bin.exe
Faulting module path: C:\OSGEO42\apps\qt5\plugins\sqldrivers\qsqlpsql.dll
Report Id: 12ed419a-3a3a-11e9-8105-000c2942e70f
Faulting package full name:
Faulting package-relative application ID:

---

• crash.txt (Attila Peller)

[qgib]

Author Name: Giovanni Manghi (@gioman)

---

• priority_id was changed from Normal to High
• subject was changed from Qgis crashes using QSqlDatabase connecting to postgis to QGIS crashes using QSqlDatabase connecting to PostGIS

[Pedro-Murteira]

@atisnz Hello, is this still valid on more recent release?

[github-actions]

The QGIS project highly values your report and would love to see it addressed. However, this issue has been left in feedback mode for the last 14 days and is being automatically marked as "stale".
If you would like to continue with this issue, please provide any missing information or answer any open questions. If you could resolve the issue yourself meanwhile, please leave a note for future readers with the same problem and close the issue.
In case you should have any uncertainty, please leave a comment and we will be happy to help you proceed with this issue.
If there is no further activity on this issue, it will be closed in a week.

[github-actions]

While we hate to see this happen, this issue has been automatically closed because it has not had any activity in the last 42 days despite being marked as feedback. If this issue should be reconsidered, please follow the guidelines in the previous comment and reopen this issue.
Or, if you have any further questions, there are also further support channels that can help you.