https://issues.qgis.org/https://issues.qgis.org/favicon.ico2018-07-02T09:02:47ZQGIS Issue TrackingQGIS Application - Bug report #19297: Repeated Crash making SQL Query in DB Managerhttps://issues.qgis.org/issues/19297?journal_id=906232018-07-02T09:02:47ZBugmi Gnottbugmignott@mailinator.com
<ul></ul><p>Second part (Crash ID: 26a6ac7056ec4001ffdb66d4cdd268098d2a2145) is the same as <a class="issue tracker-1 status-5 priority-4 priority- closed" href="https://issues.qgis.org/issues/19271" title="Crash on SQL queries - virtual layers (Closed)">#19271</a></p> QGIS Application - Bug report #19297: Repeated Crash making SQL Query in DB Managerhttps://issues.qgis.org/issues/19297?journal_id=906242018-07-02T13:07:53ZGiovanni Manghigiovanni.manghi@gmail.com
<ul><li><strong>Priority</strong> changed from <i>Normal</i> to <i>High</i></li><li><strong>Crashes QGIS or corrupts data</strong> changed from <i>No</i> to <i>Yes</i></li><li><strong>Regression?</strong> changed from <i>No</i> to <i>Yes</i></li></ul><p>Of course should not crash. If it works on 2.18 this is a regression. Also the stable release of QGIS is 2.18, not 3.*.</p> QGIS Application - Bug report #19297: Repeated Crash making SQL Query in DB Managerhttps://issues.qgis.org/issues/19297?journal_id=909372018-07-20T06:08:00ZNyall Dawson
<ul><li><strong>Status</strong> changed from <i>Open</i> to <i>Feedback</i></li></ul><p>Please test with QGIS 3.2.1</p> QGIS Application - Bug report #19297: Repeated Crash making SQL Query in DB Managerhttps://issues.qgis.org/issues/19297?journal_id=909782018-07-21T03:06:27ZLoren Amelangloren@pacific.net
<ul><li><strong>File</strong> <a href="/attachments/download/12991/Doc%20error%20on%20download%20page.JPG">Doc error on download page.JPG</a> added</li></ul><p>Nyall,</p>
<p>Help -> Check Version says I'm current, 3.3 is next step.</p>
<p>I checked the web download page, it opened with the "documentation error" message in the screenshot. Does it deserve its own bug report? <br />The newest version there is the 3.2.0-1 that I have.</p>
<p>I see a "final-3_2_1" on Github - is that what you're suggesting? It takes me a couple of hours (if I'm lucky) to download a full version out here. And I'd hate to risk replacing what I have which is mostly working... But I guess I could keep 3.2.0 available alongside that 3.2.1?</p> QGIS Application - Bug report #19297: Repeated Crash making SQL Query in DB Managerhttps://issues.qgis.org/issues/19297?journal_id=915072018-08-12T19:39:37ZLoren Amelangloren@pacific.net
<ul><li><strong>File</strong> <a href="/attachments/download/13119/SQL%20error%2019297.JPG">SQL error 19297.JPG</a> added</li><li><strong>File</strong> <a href="/attachments/download/13120/SQL%20error%2019297%20crash%20report.JPG">SQL error 19297 crash report.JPG</a> added</li></ul><p>I just remembered this issue and realized I now have 3.2.1 - so I tried the SQL query again. I was in a different QGIS project, but I was able to load the original file into my current project and repeat the query. It seems to me 3.2.1 has crashed in exactly the same way.</p>
<p>"SQL error 19297.JPG" shows the query and the error report. No message ever fills in, and mousing over the error dialog gets a wait cursor. <br />"SQL error 19297 crash report.JPG" shows the rest of QGIS with the crash report and id.</p>
<p>After the crash report and "restart QGIS", at the end of the reload of my "Recent Projects" screen, it showed several errors at the top of the project list area. It often shows such messages for such a short time I can't read even the one line that is visible.</p>
<p>The test file for my SQL query was:<br />C:\Users\loren\Giant Files\HEC-RAS Dam Break\QGIS Projects\TestProject\Profiles100-50-25LinesOnly\Profiles100-50-25.shp</p>
<p>I'm not sure if these are leftover from the crash, but I've never seen such reports at this point in QGIS operation:</p>
<pre>
2018-08-12T10:54:14 INFO QGIS Ready!
2018-08-12T10:54:15 WARNING Unable to load C:\Users\loren\Giant
2018-08-12T10:54:15 WARNING Unable to load C:\OSGeo4W64\bin\Files\HEC-RAS
2018-08-12T10:54:15 WARNING Unable to load C:\OSGeo4W64\bin\Dam
2018-08-12T10:54:15 WARNING Unable to load C:\OSGeo4W64\bin\Break\QGIS
</pre>
<p>So I tried a different SQL query on PostGIS tables, that I know works in pgAdmin4. Crash ID: 26a6ac7056ec4001ffdb66d4cdd268098d2a2145. Plus it took about ten times as long as pgAdmin4 execution before it crashed.</p>
<p>The reload showed even more strange error messages:</p>
<pre>
2018-08-12T11:34:43 INFO QGIS Ready!
2018-08-12T11:34:44 WARNING Unable to load C:\Users\loren\Giant
2018-08-12T11:34:44 WARNING Unable to load C:\OSGeo4W64\bin\Files\HEC-RAS
2018-08-12T11:34:44 WARNING Unable to load C:\OSGeo4W64\bin\Dam
2018-08-12T11:34:44 WARNING Unable to load C:\OSGeo4W64\bin\Break\QGIS
2018-08-12T11:34:44 WARNING Unable to load C:\Users\loren\Giant
2018-08-12T11:34:44 WARNING Unable to load C:\OSGeo4W64\bin\Files\HEC-RAS
2018-08-12T11:34:44 WARNING Unable to load C:\OSGeo4W64\bin\Dam
2018-08-12T11:34:44 WARNING Unable to load C:\OSGeo4W64\bin\Break\QGIS
</pre>
<p>The first crash report:</p>
<pre>
h2. User Feedback
Retrying #19297 in QGIS 3.2.1
Same problem!
h2. Report Details
*Crash ID*: 26a6ac7056ec4001ffdb66d4cdd268098d2a2145
*Stack Trace*
QBasicMutex::unlockInternal :
QgsTask::processSubTasksForTermination :
QgsTask::cancel :
PyInit__core :
PyCFunction_FastCallDict :
PyObject_GenericGetAttr :
PyEval_EvalFrameDefault :
PyFunction_FastCallDict :
PyObject_CallFunctionObjArgs :
PyObject_Call :
PyInit_sip :
std::basic_string<char,std::char_traits<char>,std::allocator<char> >::shrink_to_fit :
PyInit__core :
QgsTask::subTaskStatusChanged :
QMetaCallEvent::placeMetaCall :
QObject::event :
PyInit__core :
QApplicationPrivate::notify_helper :
QApplication::notify :
QgsApplication::notify :
QCoreApplication::notifyInternal2 :
QCoreApplicationPrivate::sendPostedEvents :
qt_plugin_query_metadata :
QEventDispatcherWin32::processEvents :
CallWindowProcW :
DispatchMessageW :
QEventDispatcherWin32::processEvents :
qt_plugin_query_metadata :
QEventLoop::exec :
QCoreApplication::exec :
main :
BaseThreadInitThunk :
RtlUserThreadStart :
*QGIS Info*
QGIS Version: 3.2.1-Bonn
QGIS code revision: commit:1edf372fb8
Compiled against Qt: 5.9.2
Running against Qt: 5.9.2
Compiled against GDAL: 2.2.4
Running against GDAL: 2.2.4
*System Info*
CPU Type: x86_64
Kernel Type: winnt
Kernel Version: 10.0.17134
</pre>
<p>The second report:</p>
<pre>
h2. User Feedback
Re: #19297 Tried a SQL query that I know works in pgAdmin4
h2. Report Details
*Crash ID*: 26a6ac7056ec4001ffdb66d4cdd268098d2a2145
*Stack Trace*
QBasicMutex::unlockInternal :
QgsTask::processSubTasksForTermination :
QgsTask::cancel :
PyInit__core :
PyCFunction_FastCallDict :
PyObject_GenericGetAttr :
PyEval_EvalFrameDefault :
PyFunction_FastCallDict :
PyObject_CallFunctionObjArgs :
PyObject_Call :
PyInit_sip :
std::basic_string<char,std::char_traits<char>,std::allocator<char> >::shrink_to_fit :
PyInit__core :
QgsTask::subTaskStatusChanged :
QMetaCallEvent::placeMetaCall :
QObject::event :
PyInit__core :
QApplicationPrivate::notify_helper :
QApplication::notify :
QgsApplication::notify :
QCoreApplication::notifyInternal2 :
QCoreApplicationPrivate::sendPostedEvents :
qt_plugin_query_metadata :
QEventDispatcherWin32::processEvents :
CallWindowProcW :
DispatchMessageW :
QEventDispatcherWin32::processEvents :
qt_plugin_query_metadata :
QEventLoop::exec :
QCoreApplication::exec :
main :
BaseThreadInitThunk :
RtlUserThreadStart :
*QGIS Info*
QGIS Version: 3.2.1-Bonn
QGIS code revision: commit:1edf372fb8
Compiled against Qt: 5.9.2
Running against Qt: 5.9.2
Compiled against GDAL: 2.2.4
Running against GDAL: 2.2.4
*System Info*
CPU Type: x86_64
Kernel Type: winnt
Kernel Version: 10.0.17134
</pre> QGIS Application - Bug report #19297: Repeated Crash making SQL Query in DB Managerhttps://issues.qgis.org/issues/19297?journal_id=915082018-08-12T19:41:47ZGiovanni Manghigiovanni.manghi@gmail.com
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Open</i></li><li><strong>Affected QGIS version</strong> changed from <i>3.2</i> to <i>3.2.1</i></li></ul> QGIS Application - Bug report #19297: Repeated Crash making SQL Query in DB Managerhttps://issues.qgis.org/issues/19297?journal_id=915092018-08-12T20:16:04ZLoren Amelangloren@pacific.net
<ul><li><strong>File</strong> <a href="/attachments/download/13121/Mystery%20project%20(not)%20in%20OSGeo4W64%20after%20crash.JPG">Mystery project (not) in OSGeo4W64 after crash.JPG</a> added</li></ul><p>One more thing... After the crashes and reload, a strange project has appeared, both in the initial display screen and in the Open Recent menu. There is no "Projects" folder in OSGeo4W64. Perhaps this is the source of the "Unable to load" messages? I used the right-click remove option and it is now gone from both places.</p> QGIS Application - Bug report #19297: Repeated Crash making SQL Query in DB Managerhttps://issues.qgis.org/issues/19297?journal_id=955412018-11-08T12:31:36ZGiovanni Manghigiovanni.manghi@gmail.com
<ul><li><strong>Status</strong> changed from <i>Open</i> to <i>Feedback</i></li></ul><p>Please try on QGIS 3.4.1, if the issue is still valid change the affected version, thanks.</p> QGIS Application - Bug report #19297: Repeated Crash making SQL Query in DB Managerhttps://issues.qgis.org/issues/19297?journal_id=956882018-11-09T01:42:41ZLoren Amelangloren@pacific.net
<ul></ul><p>Giovanni,</p>
<p>Sorry to abandon this, but I switched strategies and did my model entirely in HEC-RAS and RAS Mapper, and the report is off to the California DSOD, so I'm not likely to return to this issue. It was extremely obscure, me trying to work around a problem with the RiverGIS plugin, and I solved that one by using a pgAdmin4 query instead. Guess nobody else has run into this...</p> QGIS Application - Bug report #19297: Repeated Crash making SQL Query in DB Managerhttps://issues.qgis.org/issues/19297?journal_id=956962018-11-09T08:58:39ZGiovanni Manghigiovanni.manghi@gmail.com
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Open</i></li></ul>