Version-Release number of selected component: epiphany-3.6.1-2.fc18 Additional info: backtrace_rating: 4 cmdline: epiphany crash_function: sweep_line_delete_edge executable: /usr/bin/epiphany kernel: 3.6.10-4.fc18.x86_64 remote_result: NOTFOUND uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 sweep_line_delete_edge at cairo-bentley-ottmann-rectangular.c:558 #1 sweep_line_delete at cairo-bentley-ottmann-rectangular.c:574 #2 _cairo_bentley_ottmann_tessellate_rectangular at cairo-bentley-ottmann-rectangular.c:659 #3 _cairo_bentley_ottmann_tessellate_boxes at cairo-bentley-ottmann-rectangular.c:877 #4 fixup_unbounded at cairo-traps-compositor.c:885 #5 composite_aligned_boxes at cairo-traps-compositor.c:1290 #6 clip_and_composite_boxes at cairo-traps-compositor.c:1766 #7 clip_and_composite_polygon at cairo-traps-compositor.c:1554 #8 _cairo_traps_compositor_fill at cairo-traps-compositor.c:2229 #9 _cairo_compositor_fill at cairo-compositor.c:203
Created attachment 663978 [details] File: backtrace
Created attachment 663979 [details] File: build_ids
Created attachment 663980 [details] File: cgroup
Created attachment 663981 [details] File: core_backtrace
Created attachment 663982 [details] File: dso_list
Created attachment 663983 [details] File: environ
Created attachment 663984 [details] File: limits
Created attachment 663985 [details] File: maps
Created attachment 663986 [details] File: open_fds
Created attachment 663987 [details] File: proc_pid_status
Created attachment 663988 [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.