| Summary: | [abrt] gimp-2.6.12-1.fc16: g_type_check_instance_cast: Process /usr/bin/gimp-2.6 was killed by signal 11 (SIGSEGV) | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Georg Greve <greve> | ||||||||
| Component: | gimp | Assignee: | Nils Philippsen <nphilipp> | ||||||||
| Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | unspecified | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 16 | CC: | nphilipp | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | x86_64 | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | abrt_hash:97adc7f36c5470992b8bced79b47b5517c8c6b5c | ||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2012-04-12 07:21:55 UTC | Type: | --- | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Attachments: |
|
||||||||||
|
Description
Georg Greve
2012-04-10 07:13:12 UTC
Created attachment 576401 [details]
File: dso_list
Created attachment 576402 [details]
File: maps
Created attachment 576403 [details]
File: backtrace
Would you please describe what you did when this happened? From the command line I see that you executed some batch script, did you run multiple gimp instances in parallel here? Gimp has been called by a python script to assemble an HDR image, similar to what is described at http://linuxdarkroom.tassy.net/hdr-creation-script/. The script itself only runs sequentially, so never more than a single GIMP instance at the same time, although of course the user may at times start a new instance of the GIMP. I usually do that with the "-n" option, though, so the two should be properly independent in theory. Also, at the time of the crash I was definitely not in front of the computer, and had no instance of GIMP running myself. The only other possible instance of GIMP would have been by the same script running concurrently on a different data set in a different console, and one more such script was running that night. So it would have been the same call (gimp -c -d -i -f -s -n -b '<script>') on a different data set with a similar script. Whether that is what actually happened, I cannot say, however, as I was not at the machine when it happened. HTH *** Bug 811106 has been marked as a duplicate of this bug. *** Can you run this anew and try to reproduce it with the same image files as when it crashed? If yes, can you attach these images and and (non-standard) scripts I'd need to reproduce this here? The script running this removes the temporary files because the resulting .xcf is something like 150 MB, so if you have 100 of them, and for each of them a set of 8 images, which get enfused into three tifs, and then into the resulting xcf file, you really don't want to keep them around. So I cannot provide the pictures that caused this, unfortunately. The script is in the original error message above. Sorry to not be more useful, let me know if there is anything else I can do. Turns out that a whole lot of other components were affected, and in the end it seemed to be defective RAM on the machine that somehow only surfaced with the upgrade to kernel 3.3.1 in a visible way. Will be closing this bug for now, and reopen if it ever reoccurs with a new RAM module. Thanks for reporting back on this, I was really puzzled about what could cause this. |