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.

Sign up for GitHub

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

Jump to bottom

crash on quit #21332

Closed
qgib opened this issue Aug 26, 2015 · 13 comments
Closed

crash on quit #21332

qgib opened this issue Aug 26, 2015 · 13 comments
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Crash/Data Corruption

Comments

@qgib
Copy link
Contributor

qgib commented Aug 26, 2015 •
edited
Loading

Author Name: Roberto BobMaX (Roberto BobMaX)
Original Redmine Issue: 13272
Affected QGIS version: 2.0.1

On Windows (7 or others) QGIS crashes with minidump when quit.

It happens also without plugins.
Deleting .qgis2 dir the problem seems to be solved, but some time after it appears again.

Randomically, it crashes also QGIS MacOSX (there is no minidump, but other messages).

Related issue(s): #21168 (relates)
Redmine related issue(s): 13103
@qgib
Copy link
Contributor Author

qgib commented Aug 26, 2015

Author Name: Roberto BobMaX (Roberto BobMaX)

Image, where I run QGIS without plugins, and it crashes on quit (also with no activity done):

https://drive.google.com/file/d/0Bwg_m86uaXY1LXRvSGV2WE9uZjg/view?usp=sharing

@qgib
Copy link
Contributor Author

qgib commented Aug 26, 2015

Author Name: Roberto BobMaX (Roberto BobMaX)

this is the minidump file:

https://drive.google.com/file/d/0Bwg_m86uaXY1MVNBMVZJRVpuVGM/view?usp=sharing

I hope this helps the debug.

  • 9025 was configured as qgis-20150827-091710-6764-5396-1b929ef_minidump.zip

@qgib
Copy link
Contributor Author

qgib commented Aug 27, 2015

Author Name: Sandro Santilli (@strk)

What's the affected version ? Can you get a backtrace from the dump ?
Note that on unix you can prevent the creation of dumps (if that bothers you) using ulimit -c 0

@qgib
Copy link
Contributor Author

qgib commented Aug 27, 2015

Author Name: Jürgen Fischer (@jef-n)

Sandro Santilli wrote:

What's the affected version ? Can you get a backtrace from the dump ?
Note that on unix you can prevent the creation of dumps (if that bothers you) using ulimit -c 0

@qgis-20150827-091710-6764-5396-@ 1b929ef @_minidump.zip@

@qgib
Copy link
Contributor Author

qgib commented Aug 27, 2015

Author Name: Roberto BobMaX (Roberto BobMaX)

I used QGIS Pisa 2.10.1 on Windows 7 64 bit.

But, I had this minidump problem from QGIS 2.0.1

And, I know, many others have these (thousand of) minidumps :(

Sometimes, it crashes during layer editing, losing all changes.

Honestly, you do not ever ?

@qgib
Copy link
Contributor Author

qgib commented Sep 4, 2015

Author Name: Salvatore Larosa (@slarosa)

I am a little bit confused....

Which the version affected is? (ok, I see it is since 2.0, but it is no longer candidate for backporting)
2.8.2-3 or 2.10.1 ? (the attache image is referred to 2.8.2 and even the minidump) Could you reproduce the crash with 2.10.1 version (or 2.8.3)?

Platform MacOSX should to throw a more verbose backtrace, could you reproduce the crash and paste the stacktrace of the OSX system?

Thanks for your feedback.

  • status_id was changed from Open to Feedback

@qgib
Copy link
Contributor Author

qgib commented Sep 4, 2015

Author Name: Roberto BobMaX (Roberto BobMaX)

I want to dissolve your doubts.

I have (indeed, we all have) the minidump messages from QGIS 2.0.1 version (that is, if I remember well, the first with multithreading in viewing ).

The minidump problem continues since QGIS 2.10, today, uninterruptedly, and

it also occurs by completely disabling the plugin.

Only deleting the .qgis2 directory, the problem seems to disappear, but after some time occurs again (repeat: also without python plugins).

The peak happens if you run an older version of QGIS (especially the 2.6) before using again the version 2.10.

I am not alone in which this happens, but it is a widespread problem among users.

As soon as possible, I send messages on MacOSX, when I will experience a crash, however, Windows 7 64-bit I became a regular message.

Update: here there is a MacOSX crash report I had with QGIS:

https://drive.google.com/file/d/0Bwg_m86uaXY1M0dmdFpnMTRrZVU/view?usp=sharing

I hope this can be useful to your debug.

Regards

Roberto

@qgib
Copy link
Contributor Author

qgib commented Sep 4, 2015

Author Name: Salvatore Larosa (@slarosa)

Roberto BobMaX wrote:

I want to dissolve your doubts.

I have (indeed, we all have) the minidump messages from QGIS 2.0.1 version (that is, if I remember well, the first with multithreading in viewing ).

Multithreading is landed since 2.4 version.

The minidump problem continues since QGIS 2.10, today, uninterruptedly, and

it also occurs by completely disabling the plugin.

Unfortunately your statements are too generic for the bug tracker but it may be very useful if you'd manage to send a very small project (.qgs) to reproduce the crash which will help a lot the developers to solve the issue.

Only deleting the .qgis2 directory, the problem seems to disappear, but after some time occurs again (repeat: also without python plugins).

The peak happens if you run an older version of QGIS (especially the 2.6) before using again the version 2.10.

I am not alone in which this happens, but it is a widespread problem among users.

As soon as possible, I send messages on MacOSX, when I will experience a crash, however, Windows 7 64-bit I became a regular message.

Thanks, once you get the crash report back the stacktrace message, I'm 99% sure anyone take in account it in order to make happy everybody again!

@qgib
Copy link
Contributor Author

qgib commented Oct 5, 2015

Author Name: Jürgen Fischer (@jef-n)

What in your .qgis2 and what the difference between .qgis2 in the state where it causes the crash and a clean one? You could try to regularly backup .qgis2 until it's broken again, then verify that it actually causes the crash by renaming the last bad copy and renaming the last good one to .qgis2. Comparing the good and bad copy might then give an insight what's actually causing the problem.

  • subject was changed from minidump to crash on quit

@qgib
Copy link
Contributor Author

qgib commented Oct 8, 2015

Author Name: Giovanni Manghi (@gioman)

please note that there are 3rdparty plugins known to crash qgis even when disabled in the plugin manager (even after restarting qgis).

@qgib
Copy link
Contributor Author

qgib commented Nov 7, 2015

Author Name: Giovanni Manghi (@gioman)

  • fixed_version_id removed Version 2.10

@qgib
Copy link
Contributor Author

qgib commented Nov 10, 2015

Author Name: Giovanni Manghi (@gioman)

Closing for lack of feedback. Reopen if necessary.

  • status_id was changed from Feedback to Closed
  • resolution was changed from to not reproducable

@qgib
Copy link
Contributor Author

qgib commented Nov 21, 2015

Author Name: Roberto BobMaX (Roberto BobMaX)

Update: here there is a MacOSX crash report I had with QGIS:

https://drive.google.com/file/d/0Bwg_m86uaXY1M0dmdFpnMTRrZVU/view?usp=sharing

I hope this can be useful to your debug.

Regards

Roberto

@qgib qgib added Bug Either a bug report, or a bug fix. Let's hope for the latter! Crash/Data Corruption labels May 25, 2019
@qgib qgib closed this as completed May 25, 2019
This was referenced May 25, 2019
Closed
Closed
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Crash/Data Corruption
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@qgib