Description of problem: changing the baseline in lighttable Version-Release number of selected component: darktable-1.1-1.fc18 Additional info: backtrace_rating: 4 cmdline: darktable /home/jan/Pictures/2012/12/02/IMG_2455.CR2 crash_function: CurveDataSample executable: /usr/bin/darktable kernel: 3.6.7-5.fc18.x86_64 remote_result: 837010 uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #5 CurveDataSample at /usr/src/debug/darktable-1.1/src/common/curve_tools.c:754 #6 dt_draw_curve_calc_values at /usr/src/debug/darktable-1.1/src/gui/draw.h:151 #7 dt_iop_basecurve_expose at /usr/src/debug/darktable-1.1/src/iop/basecurve.c:462 #8 _gtk_marshal_BOOLEAN__BOXED at gtkmarshalers.c:86 #13 gtk_widget_event_internal at gtkwidget.c:5017 #14 gtk_widget_send_expose at gtkwidget.c:4846 #15 gtk_main_do_event at gtkmain.c:1610 #16 _gdk_window_process_updates_recurse at gdkwindow.c:5429 #22 _gdk_windowing_window_process_updates_recurse at gdkwindow-x11.c:5643 #23 gdk_window_process_updates_internal at gdkwindow.c:5588
Created attachment 656189 [details] File: backtrace
Created attachment 656190 [details] File: build_ids
Created attachment 656191 [details] File: cgroup
Created attachment 656192 [details] File: core_backtrace
Created attachment 656193 [details] File: dso_list
Created attachment 656194 [details] File: environ
Created attachment 656195 [details] File: limits
Created attachment 656196 [details] File: maps
Created attachment 656197 [details] File: open_fds
Created attachment 656198 [details] File: proc_pid_status
Created attachment 656199 [details] File: var_log_messages
I noticed more strange memory corruption in other programs recently and as it turned out I had a defective RAM module. Effects were very random and rare but could be the cause of most memory corruption I lately reported. I assumed it is related to the beta state of F18 so I didnt suspect the RAM at first but MemTest found a small address range with errors. I am extremely sorry for taking up your time hunting down bugs which are most likely not there. I decided to close my latest bug reports as I can not assure that the memory corruption was actually caused by the program rather than the defect RAM module.