| Summary: | Gimp crashes when using tools to make adjustments to the picture | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Richard Riggs <richard.riggs> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED WORKSFORME | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | lewyssmith |
| Version: | 8 | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | gimp-2.10.24-1.2.mga8 | CVE: | |
| Status comment: | |||
|
Description
Richard Riggs
2022-11-01 15:24:59 CET
Thank you for the report and all the crash details. (Long evidence like that is usually more convenient as an attachment to the bug; never mind).
This was bound to happen: I tried the various manoeuvres noted (Unsharp mask, Curves), repeatedly & slowly, on a simple painted design first under Mate, then Plasma, with no ill effect. Same Gimp version.
Unless another user jumps on this bug, it looks like one of those things which cannot be reproduced.
Can you say when the problem arose for you?
To summarise you system, especially the graphics, although you described it, please post the output of:
$ inxi -MSGxx
> I wonder if it is simply unable to handle the workload:
> processor is AMD A10-9700E with RADEON R7, 8GB memory,
> motherboard is Asus A320M-K, pictures are typically 3000x2000
I doubt that this the cause, although the images are large. You have plenty of RAM, and say that the crashes occur "usually when making gradual adjustments", which would seem to less load the system. Gimp works fine on much more modest systems.
I have just re-tried, slowly, adjusting all the Curves, & Unsharp mask, on an image of similar size to yours. No problems.CC:
(none) =>
lewyssmith Was also not able to reproduce this. Downloaded a 3000x3000 jpg and started manipulating. No crash. Used my oldest and weakest machine for it (i7-3520M, Intel HD4000 graphics, 8GB RAM). What you should try: - rename/delete Gimp config under /home/~user~/.config/GIMP As Gimp segfaults and your computer restarts: - perform a memory test as your RAM could be dying - perform a harddrive/ssd test as they could be dying Thanks for your work on it - sorry I didn't notice space for an attachment, I have not done this before and was simply following the instructions that Gimp gave to report it. I had found some similar problems on Google so assumed a bug, but that should not cause Linux to restart, so it makes much more sense that it is a hardware fault and the case can be closed. Will do as you advise. It is rare for problems to be due to hardware (prime suspect: memory; so sturmvogel's suggestion to test that is good; it can take hours), but this does seem a reasonable possibility in this 'unique' case. Closing, but you can still comment on the bug; and re-open it if you have more conclusive evidence. Status:
NEW =>
RESOLVED Can't find my live CD just now, so I searched the syslog for errors, and found them: parity error during data load from IC, decoder predecode buffer parity error, DE error, in MC1 and MC5. They self-correct, but something must be wrong with the memory system. The number varies but there are several each day. I'll live with it for now and think about improvements when the next version of Mageia comes out. Thanks for your help. > I searched the syslog for errors, and found them Well done. And congrats to sturmvogel for suggesting this. > something must be wrong with the memory system The slightest doubt - change it (rather than living with it)! If you have more than one bank, try removing one at a time to see whether errors are confined to that. Do not worry about running with 'just' 4Gb: I have for years, Gimping included. Apologies for this long delay. I had been wondering about those parity errors, in cache L1, whether it might be a timing problem. I didn't want to try fiddling with the many BIOS parameters, but it had been running in energy saving mode and I tried changing it to normal mode. And that cured it (and the power consumption is about the same!) |