×

INDI Library v2.0.6 is Released (02 Feb 2024)

Bi-monthly release with minor bug fixes and improvements

Raspberry Pi3 - not enough memory

  • Posts: 55
  • Thank you received: 1
Hello,
I was trying some indoor tests with Pi3 and Ubuntu Mate. before starting I did the update of both Mate and indi. My configuration is:
Mount EqMod (used simulator for indoor test)
CCD Moravian G2-8300
Guide camera: QHY5-II M
I basically tested CCD managing and what I found is memory problem in FITS preview as is reported in the log file:
2016-08-17T17:26:21.741 - DEBG - FITHistogram: JMIndex 0.217648
2016-08-17T17:26:25.107 - DEBG - WARNING: bool Phonon::FactoryPrivate::createBackend() phonon backend plugin could not be loaded
2016-08-17T17:26:25.108 - DEBG - WARNING: Phonon::createPath: Cannot connect Phonon::MediaObject ( no objectName ) to Phonon::AudioOutput ( no objectName ).
2016-08-17T17:26:25.108 - DEBG - WARNING: bool Phonon::FactoryPrivate::createBackend() phonon backend plugin could not be loaded
2016-08-17T17:26:25.108 - DEBG - WARNING: bool Phonon::FactoryPrivate::createBackend() phonon backend plugin could not be loaded
2016-08-17T17:26:26.695 - DEBG - fits MIN: 546 - fits MAX: 65535 - pixel range: 64989 - bin width 22.2794 bin count 2918
2016-08-17T17:26:27.374 - DEBG - FITHistogram: JMIndex 0.999997
2016-08-17T17:26:27.988 - DEBG - Capture: "Received image 2 out of 2."
2016-08-17T17:26:27.997 - DEBG - Capture: "Changing filter to B..."
2016-08-17T17:26:28.000 - DEBG - Capture: "Setting temperature to 10.84 C..."
2016-08-17T17:26:29.926 - DEBG - MI CCD G2-8300 : "Setting current filter to slot 4 "
2016-08-17T17:26:29.935 - DEBG - Capture: "Capturing image..."
2016-08-17T17:26:35.115 - WARN - QImage: out of memory, returning null

This happens in capturing if I play with the fit (zoom, autostretch etc) and in focus: in this case is quite impossible to do anything but unpower the Pi3.
In case of crashes, if I run KStars again, Ekos complains about another server is running and asks me whether I want to shut it down. Anyway it can't do it maybe because indi-mi driver is busy or blocked, in fact I can't use the CCD, I have to kill the process by command line.
I know Pi3 has only 1GB of ram but during the normal usage KStars uses less the 50% thanks to the last Jansem commits. I wonder whether FITS viewer could also be optimized, in focusing framing above all.
Last note: windows are not re-sizable so it's very difficult to work with them and sometimes you can't see important footer buttons, maybe a new interface is under developing?
Thanks in advance for your support, I'm available for every test to be performed on Pi3.

Clear Skies,
Giovanni.
7 years 7 months ago #9653

Please Log in or Create an account to join the conversation.

  • Posts: 2876
  • Thank you received: 809
Yes, I too have noticed that on the PI 3, if you start playing around with the fits viewer stretch, histogram, etc, you can sometimes exceed the memory available and crash the system. I did not report the issue however (sorry Jasem) because I was so happy with how well everything else was working. I avoid the problem by selecting the autostretch option before the image is taken. I haven't had any problem with looking at my images in the viewer, zooming in, zooming out, etc, and I don't find the need to change the image stretch, so it became a non-issue, at least for me.

To address your crash issue, I always run the indi server from the command line separate from KStars/Ekos using the INDI web manager. That way, if KStars/Ekos crashes for some reason, the equipment doesn't care, and if an INDI driver crashes, it is a simple matter of killing the indi server and restarting it again rather than restarting KStars.
7 years 7 months ago #9663

Please Log in or Create an account to join the conversation.

  • Posts: 486
  • Thank you received: 87
In the last week I have notice the same issue, not on the RPi, but on a regular x86-64 PC with 2GB of ram.It happens
just zooming in and out wih the mouse wheel. When it happens I notice heavy hard disk activity and KStars hangs and I have
to kill the process manually. It seems available ram is not enough for that operations and I have confirmed it expanding the
ram to 4Gb. Still , sometimes It struggles but it's not hanging anymore. In my case I am working with 34Mb raw files of the
Canon 550D so that may be the cause because that did not happen with my Atik 420 files wich are much much smaller (2mpix).

I was bypassing the problem using + and - signs instead of the mouse wheel to give the PC some time to recover and display
the image.
Last edit: 7 years 7 months ago by nMAC.
7 years 7 months ago #9669

Please Log in or Create an account to join the conversation.

  • Posts: 55
  • Thank you received: 1
Thanks for the suggestion about running server via web-interface. The problem, anyway, is critical for focus or live view task; in my case a fit file is about 16MB considering about 500MB of free RAM I suppose there could be a resource optimization in FITS viewer, maybe a profiling test can help if it is.
Let's wait what Jasem think about it.

Clear skies!

Giovanni.
7 years 7 months ago #9670

Please Log in or Create an account to join the conversation.

  • Posts: 55
  • Thank you received: 1
Hello,
has anyone from developers team checked whether fits viewer can be optimized?

Thanks and clear skies.

Giovanni.
7 years 6 months ago #10341

Please Log in or Create an account to join the conversation.

The memory issue is not from FITSViewer, it's from a leak in KDE Notification system. If you can disable the notifications from playing sounds, then the memory issue becomes a lot better. Under KDE, you go to settings -> Notification then select KStars. Under other DEs, not sure.

P.S. There is no "developer team", I'm the only one working on Ekos
Last edit: 7 years 6 months ago by Jasem Mutlaq.
7 years 6 months ago #10342

Please Log in or Create an account to join the conversation.

  • Posts: 55
  • Thank you received: 1
I'll try it. I thought there were other forum users as developer, you are doing an amazing work!
7 years 6 months ago #10348

Please Log in or Create an account to join the conversation.

  • Posts: 193
  • Thank you received: 46
I think the confusion is, many here seem to think indi and ekos are one and the same. There are a number of folks that contribute to the indi subsystem, but I believe Jasem is the only one working on ekos.
7 years 6 months ago #10400

Please Log in or Create an account to join the conversation.

  • Posts: 2876
  • Thank you received: 809
In addition to that, aren't there more people working on KStars, even though only Jasem is doing Ekos, and even though Jasem is the lead on KStars?
7 years 6 months ago #10403

Please Log in or Create an account to join the conversation.

Time to create page: 0.505 seconds