[BUG] Crash when opening gpx files #727
Comments
Author: bart[at]vanhauwaert.org The backtrace in Visual Studio is a bit more clear, although I have not fully studied the issue. There seems to be a mishandling in the layerwidgets. Maybe Chris can find out what the problem is? |
Author: bart[at]vanhauwaert.org Also, if you import a GPX file, merkaartor doesn't crash but you end up with two background image layers. I suppose that one is related. |
Author: dantje I ran this in valgrind and it did not crash. Duh. Heisenbug. |
Author: dantje I stepped thru this until I found the last instruction before the crash. It is in the
|
Author: koying I must say I don't get any of your problems with my development version on linux. Just to be aligned, could you both attach your problematic GPX, just in case it's file dependent. |
Author: koying Also, could you specify which image backend you were using and your Qt version (I'm using 4.3.3) |
Author: dantje I see the same behaviour in a fresh checkout from svn. Qt revision is 4.3.2 on Ubuntu 7.10 (gutsy). It does not seem to be related to the gpx file, but I'll attach a "bad" file that I just got from the traces list. Image backend is the background image layer? I use the OSM one. But if I check "None" it also happens. I can make the file/open work by commenting out the Layout->addWidget(w) line from theLayerDock::updateContent() method. |
Author: koying Definitely cannot reproduce on my gentoo. Will check on monday on win32 (also 4.3.3 unfortunately). I suspect a qt bug which was corrected on 4.3.3, so I'll install a virtual ubuntu 7.10 machine to try to reproduce. |
Author: koying I confirm I get the crash on Ubuntu 7.10/Qt 4.3.2. Debugging... |
Author: koying LayerWidgets are reparented to the groupbox, so leave to it to delete them. |
Author: koying (In [7068]) ADD : Export viewport to OSM |
Reporter: dantje
[Submitted to the original trac issue database at 10.04pm, Friday, 7th March 2008]
Steps:
The backtrace is not directly helpful:
The code visits LayerManger::backZoomIn() twice. The second time around it
calls ImageManager::instance()->abortLoading() and segfaults.
The text was updated successfully, but these errors were encountered: