Skip to content
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

Crash when adding area #703

Open
wthaem opened this issue Dec 16, 2024 · 0 comments
Open

Crash when adding area #703

wthaem opened this issue Dec 16, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@wthaem
Copy link
Contributor

wthaem commented Dec 16, 2024

Describe the bug

QMS Windows version (both Qt5 and Qt6 version) crashes when trying to add an area to a map

What have you done to circle down the problem?

see next point

To Reproduce

  1. Start QMS with an INI file in which a BRouter configuration is defined
  2. Goto a map window
  3. Right click and select Add area.
  4. Move mouse with attached endpoint of the line segment to a new location. Don't click.
  5. Wait a little moment and see that QMS crashes
  6. This crash can be reproduced. It happens with a release and a release-with-debug Exe
  7. Restart QMS without using a INI file or use a INI without BRouter configuration
  8. Repeat adding an area
  9. See that QMS doesn't crash

Expected behavior

No crash

Screenshots

None

Attachments

None

Tracebacks

The call stack obtained in MSVC when using a RelWithDebug variant indicates that the crash happens somewhere in a Qt module. The last QMS file/function/method used was main(...).

Desktop

  • OS: Windows 10
  • QMapShack Version: latest dev version with Qt5 or Qt6
  • Window Manager: [e.g. KDE, GNOME]

Additional context

Remarks:

There seem to be some common actions with unresolved and still existing issues #388, #624 and, maybe, others:

  • A line segment should be drawn
  • The start of the line segment is fixed by triggering some command (Add area, Add track)
  • The endpoint of the line segment is attached to the mouse
  • The mouse, i.e. the endpoint of the line segment, is moved to some new location
  • The endpoint of the segment is not yet fixed by a mouse click
  • After not moving the mouse for a little while or moving it slightly without clicking the crash happens
  • The call stack points to a series of Qt or other non-QMS modules. The first QMS module mentioned in the call stack doesn't give any useful information about the possible reason of the crash.
  • The crashes can be reproduced
@wthaem wthaem added the bug Something isn't working label Dec 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant