Eric thanked Teseo in topic Error build 1 month ago

Teseo created a new topic ' Error build' in the forum. 1 month ago

Hi, last nt build, return this error:

[ 97%] Building CXX object Tests/skyobjects/CMakeFiles/test_skypoint.dir/test_skypoint_autogen/mocs_compilation.cpp.o
libKStarsLib.a(indiproperty.cpp.o): in the function "INDI_P::buildLightGUI()":
/opt/Astronomia/indi_ekos_build/Projects/kstars/kstars/indi/indiproperty.cpp:279:undefined reference a "INDI::Property::getLight() const"
libKStarsLib.a(indistd.cpp.o): in the function "ISD::GenericDevice::getJSONProperty(QString const&, QJsonObject&, bool)":
/opt/Astronomia/indi_ekos_build/Projects/kstars/kstars/indi/indistd.cpp:931: undefined reference a "INDI::Property::getLight() const"
libKStarsLib.a(indidbus.cpp.o): in the function "INDIDBus::getProperties(QString const&)":
/opt/Astronomia/indi_ekos_build/Projects/kstars/kstars/indi/indidbus.cpp:184: undefined reference a "INDI::Property::getLight() const"
libKStarsLib.a(indidbus.cpp.o): in the function "INDIDBus::getLight(QString const&, QString const&, QString const&)":
/opt/Astronomia/indi_ekos_build/Projects/kstars/kstars/indi/indidbus.cpp:305: undefined reference a "INDI::Property::getLight() const"
collect2: error: ld returned 1 exit status
kstars/CMakeFiles/kstars.dir/build.make:227: recipe for target 'kstars/kstars' failed
make[2]: *** [kstars/kstars] Error 1
CMakeFiles/Makefile2:393: recipe for target 'kstars/CMakeFiles/kstars.dir/all' failed
make[1]: *** [kstars/CMakeFiles/kstars.dir/all] Error 2
make[1]: *** Attesa per i processi non terminati....
[ 98%] Linking CXX executable test_skypoint
[ 98%] Built target testfwparser
[ 98%] Built target testcsvparser
[ 98%] Built target test_skypoint
Makefile:140: recipe for target 'all' failed
make: *** [all] Error 2

Thanks.

Read More...

Teseo replied to the topic 'Memory Leak' in the forum. 1 month ago

Very good, work ok.
Thanks knro.

Read More...

Teseo thanked Jasem Mutlaq in topic Memory Leak 2 months ago

Teseo thanked Eric in topic Error compiling 2 months ago

Teseo created a new topic ' Error compiling' in the forum. 2 months ago

For several days kstars has not been compiled,
fails with this error:

[ 99%] Built target kstars
CMakeFiles/kstars_ui_tests.dir/test_ekos.cpp.o: in the function "KStarsUiTests::manipulateEkosProfiles()::{lambda()#3}::operator()() const":
/opt/Astronomia/indi_ekos_build/Projects/kstars/Tests/kstars_ui/test_ekos.cpp:198: undefined reference a "bool QTest::qCompare<QString, char [20]>(QString const&, char const (&) [20], char const*, char const*, char const*, int)"
/opt/Astronomia/indi_ekos_build/Projects/kstars/Tests/kstars_ui/test_ekos.cpp:202: undefined reference a "bool QTest::qCompare<QString, char [14]>(QString const&, char const (&) [14], char const*, char const*, char const*, int)"
collect2: error: ld returned 1 exit status
Tests/kstars_ui/CMakeFiles/kstars_ui_tests.dir/build.make:258: recipe for target 'Tests/kstars_ui/kstars_ui_tests' failed
make[2]: *** [Tests/kstars_ui/kstars_ui_tests] Error 1
CMakeFiles/Makefile2:1407: recipe for target 'Tests/kstars_ui/CMakeFiles/kstars_ui_tests.dir/all' failed
make[1]: *** [Tests/kstars_ui/CMakeFiles/kstars_ui_tests.dir/all] Error 2
Makefile:140: recipe for target 'all' failed
make: *** [all] Error 2
[pcxz@kstars]$ 


Read More...

Teseo replied to the topic 'Celestron hybernation mode' in the forum. 3 months ago

ChrisRowland wrote: The earliest is NS+ HC 5.22 for gems and 5.24 for fork mounts. This is when Celestron implemented the command in their HCs.

Chris


Version 4.22 also has the hibernation function, I use it every night.
No problem, I continue to do it manually.
Bye

Read More...

Teseo replied to the topic 'Celestron hybernation mode' in the forum. 3 months ago

ChrisRowland wrote: I worked with the Celestron developers to arrange a set of RS232 ...
It's for the NexStar Plus HC only...

Chris


Only for Plus version? .. is not possible port also in non Plus version ? ( NexStar 4.22 )
Thanks

Read More...

Teseo replied to the topic 'Memory Leak' in the forum. 3 months ago

hy wrote: I was wondering, for the folks with the memory leak--do you have the option "Single Preview Tab" checked? (I think you should have it checked).
You find that under the KStars options, then FITS, then it's a checkbox on that page.
I believe that KStars/fitsviewer would leak tabs if you had it unchecked (perhaps it should limit the number of tabs, I don't know if it does or doesn't).
Hy


Yes is checked and Fits viewer is disabled.
Thanks

Read More...

Tim Schuh thanked Teseo in topic Memory Leak 3 months ago

Teseo replied to the topic 'Memory Leak' in the forum. 3 months ago

knro wrote: I would like to know how I can replicate this.. I took 500 images on StellarMate a couple of weeks ago and I couldn't detect any memory leak. Was HIPS overlay enabled? I'd like to replicate exact conditions.


Thanks knro, next time I create a log, HIPS is disabled.
I forgot to mention that they are all FITS image ( fits viewer is disabled ).

Read More...

Teseo thanked Jasem Mutlaq in topic Memory Leak 3 months ago

Teseo replied to the topic 'Memory Leak' in the forum. 3 months ago

Lead_weight wrote: I have a 4GB RPi4 and the memory leak stops it too after about 4 hours of imaging. Happens every single time. I've since changed how I use KStars/EKOS. I used to run it all on the Pi device and would VNC in to the desktop and monitor it from a computer in the house. But since the memory leak, I only run the INDI Server now on the Pi Device and connect to it from KStars/EKOS in the house. This method does not experience the memory leak, and I've been able to image reliably now for about a month.


I also use it remotely, and as I said in the computer I have 8GB of memory.
After the automatic capture of over 100 images (asteroid orbit measurement) the computer becomes slow, so much so that I have to close kstars to free up more than 7gb of memory.
Every time download an image it takes up a lot of ram memory.

Read More...

Teseo replied to the topic 'Memory Leak' in the forum. 3 months ago

I'm experiencing the same behavior.

When it got to finishing a capture, downloading, and beginning the next capture however the memory would increase by ~20 MiB each time until it ran out of memory when downloading a capture and kstars would force close.


Yes, that's the problem, it seems that Kstars doesn't free up memory after the image has been downloaded (in my case every FITS image has a weight greater than 30 MB), after more than 100 images are captured, my computer with 8 GB of memory it does not respond and requires "absolutely" that I close kstars.

With the latest kstars, indi, indi-3rdparty.
And all image captured in automatic scheduler.

Read More...

Teseo thanked Sean Pickard in topic Memory Leak 3 months ago