-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
QGIS crash when opening certain WFS projects #17979
Comments
Author Name: Jacob Madsen (Jacob Madsen) Could I get some feedback on this issue please? |
Author Name: Jacob Madsen (Jacob Madsen) Reproduces still in latest master |
Author Name: Martin Dobias (@wonder-sk) If you create the same project with WFS layers in QGIS 32-bit, will it crash when reopened in QGIS 32-bit? |
Author Name: Jacob Madsen (Jacob Madsen) Sorry, but I can still reproduce this with build 57dd877. I create a WFS-project in QGIS x64, and when opening the same project in the same build of the 32-bit version of QGIS, it crashes after logging in. |
Author Name: Jürgen Fischer (@jef-n)
|
Author Name: Jacob Madsen (Jacob Madsen) I have uploaded 2 sample projects for this issue. The projects contain the exact same WFS references. One is created with 57dd877 64-bit, the other is created with the same build 32-bit. If I open the project created with the 64-bit version on the 32-bit version, it crashes after entering credentials. The project created on the 32-bit version works fine with another QGIS 32-bit version. Please figure out, what exactly the difference between these 2 project files is.
|
Author Name: Jürgen Fischer (@jef-n)
|
Author Name: Jacob Madsen (Jacob Madsen) Sent to your email, Jürgen. Thanks in advance. |
Author Name: Jürgen Fischer (@jef-n) Jacob Madsen wrote:
Hm, I don't see any significant differences: just the project extent, the symbol colors and the layer ids are different. But there's no crash here. I tried both projects with a fresh 32bit build, 32bit osgeo4w build of last night (57dd877 / 2.1.0-121), a fresh 64bit build and 2.0.1 from osgeo4w 32bit and 64bit. Might this be caused by a plugin you use? |
Author Name: Jacob Madsen (Jacob Madsen) No, it reproduced at will earlier today on completely fresh installs. The server is Geoserver 2.4.3, and the data comes from an Oracle database. Since I can't reproduce the error any longer (of course), I suspect some kind of invalid response from the server to be the real culprit. Can an invalid response from the server somehow cause issues like this? I've struggled with various JDBC driver issues on the server, and today I've tried to install the latest 11.2 JDBC driver to see, if that solves the issue. Will the minidump files itself be of any use to you? |
Author Name: Jürgen Fischer (@jef-n) Jacob Madsen wrote:
I suppose everything really unexpected can.
Yes, if it's from a recent build. |
Author Name: Jacob Madsen (Jacob Madsen) Here is a minidump file generated by yesterday's crash (which I could no reproduce later). I really hope you can use it for something. |
Author Name: Jacob Madsen (Jacob Madsen) I was unable to upload the minidump here (file too large apparently), so I've sent it to your email using WeTransfer. Hope that's OK. Minidump generated on Windows XP with build 57dd877 32-bit. |
Author Name: Jürgen Fischer (@jef-n) Jacob Madsen wrote:
Unfortunately it doesn't sched much light on the problem. It crashes while QtNetwork does a @realloc@. No idea if it how much memory it requested or if that heap is already corrupted at that point - the stacktrace doesn't show any actual qgis frames. |
Author Name: Jacob Madsen (Jacob Madsen) What more can I do to assist you in fixing this issue? All I can say at this point is, that I've seen this problem on many different systems. You see - I distribute QGIS projects to various customers to give them access to their spatial data through Geoserver. Many customers experienced QGIS crashing right after opening the project - just as I've described here. I really hope, that some kind of solution to this issue will make it into 2.2. |
Author Name: Jürgen Fischer (@jef-n) Jacob Madsen wrote:
You can't reproduce the problem, can you? The minidump would have been useful to verify that what cause the crash was meanwhile fixed. So we don't know if there still is a problem, right? |
Author Name: Jacob Madsen (Jacob Madsen) What do you mean? The problem was reproduced, but apparently it's intermediary. That I can't reproduce it now doesn't mean, that it won't happen again, as I don't know the cause of it other than it's some network issue. So what you're saying is, that there is nothing you can do about this to avoid this crash? I can't give you anything else than this. I had so much hoped to have this issue fixed for 2.2.... |
Author Name: Jacob Madsen (Jacob Madsen) Issue just occurred again today, still latest build. Minidump sent on WeTransfer. |
Author Name: Jürgen Fischer (@jef-n) Jacob Madsen wrote:
Well, then i misunderstood. I thought the problem was gone after both master and your service were changed. Could it be that the crash only happens, when the login window stays on a while (ie. the request meanwhile timesout)? |
Author Name: Jürgen Fischer (@jef-n) Fixed in changeset "7c4c7e897e145eb38ea90be1bf8989e09bec698c".
|
Author Name: Jacob Madsen (Jacob Madsen)
Original Redmine Issue: 9379
Affected QGIS version: 2.0.1
Redmine category:web_services_clients/wfs
Assignee: Jürgen Fischer
Attached file was created on QGIS 2.0.1 64-bit. When it's opened in QGIS 2.0.1 32-bit, QGIS crashes with a minidump after entering the credentials (I'll supply these on e-mail).
The text was updated successfully, but these errors were encountered: