| Summary: | Debayer in the FITS viewer | ||
|---|---|---|---|
| Product: | [Applications] kstars | Reporter: | Flavius <flavius.a> |
| Component: | general | Assignee: | Jasem Mutlaq <mutlaqja> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | CC: | nate |
| Priority: | NOR | Keywords: | drkonqi |
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Flavius
2021-07-07 08:52:39 UTC
Can you post a link to the image you wanted to debayer so we can reproduce this? sure, here it is: https://flavius.xyz/download/test.fits also, for what is worth, then i check auto debayer in options, THEN the debayer menu under file becomes enabled. if i untick auto debayer in options, then the debayer menu item is disabled. wasn't it suppose to be the other way around? maybe that's why i have the crash, i'm trying to debayer an already debayered image? It's working fine here. How much RAM do you have? I suspect it could be a memory issue. 6GB but what's the point of having the debayer menu option (ctrl+d) enabled when i also have auto-debayer enabled and the option disabled if i also disable auto-debayer? Because you can manually de-bayer using different options. 6GB then most likely a memory related issue. oh, i get it. so it's more of a "debayer again" option rather than a "manual debayer" i case i have auto-debayer turned off. how much ram will i need to use the option? auto-debayer works ok, no issues there... just tested now, memory definitelly not an issue, 1.2GB used out of 6, hit debayer, crash just found out now. if i open the image in kstars and debayer it (ctrl+d) it works. it only crashes in the fits viewer which opens after the capture with the capture result. Please check against KStars 3.6.1 and report back. (In reply to Jasem Mutlaq from comment #10) > Please check against KStars 3.6.1 and report back. still happening Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |