https://bugs.kde.org/show_bug.cgi?id=430127
Jasem Mutlaq changed:
What|Removed |Added
Resolution|WAITINGFORINFO |FIXED
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=430127
--- Comment #12 from mountainai...@outlook.com ---
Unfortunately I don't believe I'll be able to conveniently test this, but in
the more than year and a half since reporting the issue I'm sure others have
had some experience with the issue. Please close
https://bugs.kde.org/show_bug.cgi?id=430127
Jasem Mutlaq changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=430127
--- Comment #10 from mountainai...@outlook.com ---
I believe this just happened with my new ASI294MM-Pro in 1x1 binning mode.
I'll try to reproduce again, but I'm not sure I'll be using this camera
tonight.
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=430127
--- Comment #9 from Jasem Mutlaq ---
I started investigating this issue in depth now.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=430127
--- Comment #8 from mountainai...@outlook.com ---
Another full-frame camera has graced my doorstep, so this issue will now affect
both my RPis. Hopefully we can find a solution for this mystery.
--
You are receiving this mail because:
You are watching
https://bugs.kde.org/show_bug.cgi?id=430127
--- Comment #7 from Jasem Mutlaq ---
Btw, I'm still checking why we can't use the supposedly 3GB limit for App. 3GB
would be more than enough.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=430127
--- Comment #6 from mountainai...@outlook.com ---
Just a note for the ticket, Jasem was able to connect and noted that as soon as
KStars approached 2GB RAM, it crashed. It should be able to use 3GB in this
x86 kernel, so it's a mystery that he is resear
https://bugs.kde.org/show_bug.cgi?id=430127
--- Comment #5 from Jasem Mutlaq ---
Thank you for the update, the log shows it stops when reading the file. It
would be better to arrange for teamviewer session to debug the rpi4 in more
detail. Once teamviewer is installed, please share the details pr
https://bugs.kde.org/show_bug.cgi?id=430127
--- Comment #4 from mountainai...@outlook.com ---
Created attachment 134107
--> https://bugs.kde.org/attachment.cgi?id=134107&action=edit
Crash log
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=430127
--- Comment #3 from mountainai...@outlook.com ---
Unfortunately the 8GB version of the RPi4 did not resolve this issue. While I
never saw memory climb much above 3.3GB according to the task manager, KStars
continued to crash after 3-5 frames. I am atta
https://bugs.kde.org/show_bug.cgi?id=430127
--- Comment #2 from mountainai...@outlook.com ---
I was able to capture successfully using KStars on macOS Big Sur running on a
Mac mini with 16GB RAM. However, that is undesired because it is not as stable
as Linux (6 crashes last night) and I'm not cr
https://bugs.kde.org/show_bug.cgi?id=430127
--- Comment #1 from mountainai...@outlook.com ---
Note: RPi4 was not overheating. It has a cooling fan, and it is in a
refrigerator at 34°F (I'm taking darks for this new camera).
Also, this crash/hang seems to happen even if I am just looping images.
13 matches
Mail list logo
