Project

General

Profile

Bug #10709

Crop & Rotate Crashes

Added by Joe Giampaoli over 3 years ago. Updated over 3 years ago.

Status:
Incomplete
Priority:
Low
Assignee:
-
Category:
Darkroom
Start date:
11/09/2015
Due date:
% Done:

20%

Affected Version:
2.0rc1
System:
Debian
bitness:
64-bit
hardware architecture:
amd64/x86

Description

Version 2 crashes completely when using crop & rotate, with 4:5 aspect ratio I have an almost 100% crash.

History

#1 Updated by Joe Giampaoli over 3 years ago

Stopped the crashing by resetting parameters for that module and cropping and rotating from zero again.

#2 Updated by Pedro Côrte-Real over 3 years ago

  • % Done changed from 0 to 20
  • Status changed from New to Incomplete

If you still have the xmp or can replicate it we would like to have a look at what was causing that.

#3 Updated by Joe Giampaoli over 3 years ago

Pedro Côrte-Real wrote:

If you still have the xmp or can replicate it we would like to have a look at what was causing that.

Argh! Didn't think about saving the sidecard for posting it here, I reset-ed those settings and compressed the history stack. OK, when I get that crash again I'll do that for sure! It's not the first time, but it was very consistent right now, so I'll do that when it happens again...

Just the sidecard? You dont need the photo file?

Thanks!

#4 Updated by Pedro Côrte-Real over 3 years ago

Just the sidecard? You dont need the photo file?

Both would be great in case there's a combination of settings and characteristics of the file that make it happen.

#5 Updated by Joe Giampaoli over 3 years ago

Pedro Côrte-Real wrote:

Just the sidecard? You dont need the photo file?

Both would be great in case there's a combination of settings and characteristics of the file that make it happen.

Very well! I'll keep that in mind...

I'm thinking it could probably be something to do with the watermark, I also had a crash while working with watermark on the same photo, probably that had to do with it since I was re-scaling with watermark on, I'll see if I can replicate it sooner instead of just waiting for it to happen again...

#6 Updated by Roman Lebedev over 3 years ago

Joe Giampaoli wrote:

Pedro Côrte-Real wrote:

Just the sidecard? You dont need the photo file?

Both would be great in case there's a combination of settings and characteristics of the file that make it happen.

Very well! I'll keep that in mind...

I'm thinking it could probably be something to do with the watermark, I also had a crash while working with watermark on the same photo, probably that had to do with it since I was re-scaling with watermark on, I'll see if I can replicate it sooner instead of just waiting for it to happen again...

I'm sorry to say this, but anything like this without backtrace is pretty pointless.

Darktable should write backtrace when it's crashing into /tmp/darktable_bt_XXXXXX.txt, and when reporting crashes you should always provide that bt.
Also, you need to have debug symbols installed, for dt and libraries it uses (gtk, glib, etc)

Also available in: Atom PDF