Crash after moving virtual nodes #2621
Comments
Author: Koying Are you using the latest svn? I cannot immediately reproduce... I've made so many commits today ;-) |
Author: Koying Or maybe I don't understand what you mean by "while (running)" |
Author: dantje Replying to [comment:2 Koying]:
Darn markup. This "while (running)" should mean that you continue to move virtual nodes that came up, after you moved the node before (and so on). I could reproduce it again with svn 19388. Takes some time, 1min or so, maybe 30 iterations of moving virtual nodes. Valgrind says that a TrackPoint was deleted and then used again. Just for the record, I'm running Ubuntu 9.10 and x86-64bit machine.
|
Author: Koying I created 50+ nodes on one road, on win32/Qt 4.6.0 and Gentoo/Qt 4.5.3 without crash. Could it be a Qt bug? I'll try to find something with your (useful) valgrind log. |
Author: Koying Strange thing is that the line numbers for MapFeature.cpp seem to be wrong in the logs, while they are right for the other source files... Would you happen to have some local modification in it? |
Author: dantje Replying to [comment:5 Koying]:
I did a "rm -rf src/ && svn update" before, but I'll do a clean build when I'm home. |
Author: dantje It still happens in svn 19408. Freshly "svn updated" into a empty directory and build there:
Another bug more reproducable bugs with virtual nodes:
I'd be really happy, if somebody could reproduce this stuff ;-) |
Author: Koying Hi Dan, I could more or less reproduce on linux (or is it 4.5.x?) only. I'm not sure it is exactly the same problem, though. While the valgrind log is equivalent, the SEGFAULT was somewhere else (although it seems you have various crash points, too). Could you try again with latest svn? Thx |
Author: dantje Replying to [comment:8 Koying]:
Yes. There are backtraces vary.
In 19520 it is still there. Daniel |
Author: Koying Should be solved by now, isn'it? It it isn't, please reopen |
Reporter: dantje
[Submitted to the original trac issue database at 6.32pm, Sunday, 10th January 2010]
Build from svn
Callstack and valgrind output attached. Valgrind show many illegal reads/writes.
Callstack:
Valgrind:
The text was updated successfully, but these errors were encountered: