VERSION 3.6 DEVELOPMENT BUILD JULY 2021

[Mark Liversedge]

We're finalising for release with only a small number of issues left to fix and translations to resolve. The new perspectives feature is in here and a few other fixes.

https://github.com/GoldenCheetah/GoldenCheetah/releases/tag/v3.6-DEV2107

As ever, please report issues with this build in this thread.

Thanks

Mark

[José Luis García Pallero]

El sáb, 10 jul 2021 a las 21:07, Mark Liversedge
(<liver...@gmail.com>) escribió:

>
>
> We're finalising for release with only a small number of issues left to fix and translations to resolve. The new perspectives feature is in here and a few other fixes.
>
> https://github.com/GoldenCheetah/GoldenCheetah/releases/tag/v3.6-DEV2107
>
> As ever, please report issues with this build in this thread.

Hello:

I've obtained a segmentation fault when I try to access to the chart
Ride Plots V5 (Py) from CloudDB. This chart works without problems in
the June release candidate. I obtain also another segmentation fault
in Trends section when I try to access to the chart, also from
CloudDB. One problem is that, as I can't access to the charts I can
not delete them


>
> Thanks
> Mark
>
> --
> _______________________________________________
> Golden-Cheetah-Users mailing list
> golden-che...@googlegroups.com
> http://groups.google.com/group/golden-cheetah-users?hl=en
> ---
> You received this message because you are subscribed to the Google Groups "golden-cheetah-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to golden-cheetah-u...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/golden-cheetah-users/de895180-d8bc-42ca-9d07-95395f39770dn%40googlegroups.com.



--
*****************************************
José Luis García Pallero
jgpa...@gmail.com
(o<
/ / \
V_/_
Use Debian GNU/Linux and enjoy!
*****************************************

[José Luis García Pallero]

El sáb, 10 jul 2021 a las 22:43, José Luis García Pallero
(<jgpa...@gmail.com>) escribió:

>
> El sáb, 10 jul 2021 a las 21:07, Mark Liversedge
> (<liver...@gmail.com>) escribió:
> >
> >
> > We're finalising for release with only a small number of issues left to fix and translations to resolve. The new perspectives feature is in here and a few other fixes.
> >
> > https://github.com/GoldenCheetah/GoldenCheetah/releases/tag/v3.6-DEV2107
> >
> > As ever, please report issues with this build in this thread.
>
> Hello:
>
> I've obtained a segmentation fault when I try to access to the chart
> Ride Plots V5 (Py) from CloudDB. This chart works without problems in
> the June release candidate. I obtain also another segmentation fault
> in Trends section when I try to access to the chart, also from
> CloudDB. One problem is that, as I can't access to the charts I can
> not delete them

Excuse me, I forgot to say that I'm running GNU Debian Sid operating system

[Ale Martinez]

El sábado, 10 de julio de 2021 a la(s) 17:44:34 UTC-3, jgpa...@gmail.com escribió:

El sáb, 10 jul 2021 a las 21:07, Mark Liversedge
(<liver...@gmail.com>) escribió:
>
>
> We're finalising for release with only a small number of issues left to fix and translations to resolve. The new perspectives feature is in here and a few other fixes.
>
> https://github.com/GoldenCheetah/GoldenCheetah/releases/tag/v3.6-DEV2107
>
> As ever, please report issues with this build in this thread.

Hello:

I've obtained a segmentation fault when I try to access to the chart
Ride Plots V5 (Py) from CloudDB. This chart works without problems in
the June release candidate. I obtain also another segmentation fault
in Trends section when I try to access to the chart, also from
CloudDB. One problem is that, as I can't access to the charts I can
not delete them

This is a known issue for Python charts in this build, it is fixed in master and Windows users can download the fixed binary from https://ci.appveyor.com/project/Joern-R/goldencheetah-knhd8/builds/39941096/artifacts, for macOS and Linux we would need to generate a new snapshot, may be after other issues are found and fixed.

[Rui_B]

on mac os11... in addition to the python issue, the search/filter field still displays a black box with black text, no matter which "decor" is selected.

cheers.

Rui

[Mark Liversedge]

On Sunday, 11 July 2021 at 05:06:52 UTC+1 Rui_B wrote:

on mac os11... in addition to the python issue, the search/filter field still displays a black box with black text, no matter which "decor" is selected.

I cannot recreate this, I am on 11.4.

Mark

[Rui_B]

oh... I have my computer in dark mode.... easier on the eyes for me...  here is a screen shot

[pinaman]

After i'm done with my workout and click on Save button it crashes GC. Same is when i try to import (from "GC/records" folder) and click on Save button. In 3.6 June version everything works ok.

Debug message: Segmentation fault (core dumped)

[Sam Horne]

I'm liking the new prespectives feature and using it with a switch expression for activities. This is working for me when moving between activities but when swapping to the activities view the perspective defaults to the first perspective in the list rather than evaluating based on the currently selected activity.

Seperately in the overview chart the column widths do not appear to be saved for me after closing/reopening GC.

[Ale Martinez]

El domingo, 11 de julio de 2021 a la(s) 14:32:52 UTC-3, pinaman escribió:

After i'm done with my workout and click on Save button it crashes GC. Same is when i try to import (from "GC/records" folder) and click on Save button. In 3.6 June version everything works ok.

Debug message: Segmentation fault (core dumped)

Can you run GC with gdb and post the output of backtrace command after the crash?

[pinaman]

I never used gdb before, so i'm not sure if this is the data you need. If not, let me know and i will figure it out.

Thread 1 "AppRun" received signal SIGSEGV, Segmentation fault.
0x0000555555d7c565 in Perspective::filterlist(DateRange) ()
(gdb)

And some extra info...

While running GC with gdb, it doesn't crash, but it is saving for ever. And Abort button doesn't work (in import window). This test was done after stopping workout in train view.

[Ale Martinez]

El lunes, 12 de julio de 2021 a la(s) 03:05:36 UTC-3, pinaman escribió:

I never used gdb before, so i'm not sure if this is the data you need. If not, let me know and i will figure it out.

Thread 1 "AppRun" received signal SIGSEGV, Segmentation fault.
0x0000555555d7c565 in Perspective::filterlist(DateRange) ()
(gdb) 

At (gdb) prompt you can enter bt to display the backtrace leading to the crash, which is what I am looking for.

And some extra info...

While running GC with gdb, it doesn't crash, but it is saving for ever.

That’s expected until you exit gdb, use Ctrl +D

[UlysseUlysse]

Hello,
Crash of this version of GC appimage when opening the "trends" tab on Debian GNU / Linux 10 (buster)

[UlysseUlysse]

Hello,

Crash of this version of GC appimage when opening the "trends" tab on Debian GNU / Linux 10 (buster)

After several tests, still the crash with the "trends" tab, the version of GC that works for me is that of June (Build id: 4004, version: V3.6-DEV2106)

[pinaman]

Thanks for info. I was able to exit it, i just thought it might be related to crash / problem.

So here is backtrace data:

(gdb) bt
#0  0x0000555555d7c565 in Perspective::filterlist(DateRange) ()
#1  0x0000555555740a54 in Bindings::seasonMetrics(bool, DateRange, QString) const ()
#2  0x000055555574208e in Bindings::seasonMetrics(bool, QString, bool) const ()
#3  0x000055555572edd9 in meth_Bindings_seasonMetrics ()
#4  0x00007ffff6f010eb in _PyMethodDef_RawFastCallKeywords () from /tmp/.mount_GoldenQVRAIY/lib/libpython3.7m.so.1.0
#5  0x00007ffff6f00e70 in _PyCFunction_FastCallKeywords () from /tmp/.mount_GoldenQVRAIY/lib/libpython3.7m.so.1.0
#6  0x00007ffff6f8cceb in _PyEval_EvalFrameDefault () from /tmp/.mount_GoldenQVRAIY/lib/libpython3.7m.so.1.0
#7  0x00007ffff6f87473 in _PyEval_EvalCodeWithName () from /tmp/.mount_GoldenQVRAIY/lib/libpython3.7m.so.1.0
#8  0x00007ffff6f87193 in PyEval_EvalCodeEx () from /tmp/.mount_GoldenQVRAIY/lib/libpython3.7m.so.1.0
#9  0x00007ffff6f8714b in PyEval_EvalCode () from /tmp/.mount_GoldenQVRAIY/lib/libpython3.7m.so.1.0
#10 0x00007ffff702e282 in ?? () from /tmp/.mount_GoldenQVRAIY/lib/libpython3.7m.so.1.0
#11 0x00007ffff702e22a in PyRun_StringFlags () from /tmp/.mount_GoldenQVRAIY/lib/libpython3.7m.so.1.0
#12 0x00007ffff702e17c in PyRun_SimpleStringFlags () from /tmp/.mount_GoldenQVRAIY/lib/libpython3.7m.so.1.0
#13 0x000055555571e92b in PythonEmbed::runline(ScriptContext, QString) ()
#14 0x0000555555aa2ebb in DataFilterRuntime::runPythonScript(Context*, QString, RideItem*, QHash<QString, RideMetric*> const*, Specification) ()
#15 0x0000555555aaedf3 in Leaf::eval(DataFilterRuntime*, Leaf*, Result const&, long, RideItem*, RideFilePoint*, QHash<QString, RideMetric*> const*, Specification, DateRange) ()
#16 0x0000555555aafa50 in Leaf::eval(DataFilterRuntime*, Leaf*, Result const&, long, RideItem*, RideFilePoint*, QHash<QString, RideMetric*> const*, Specification, DateRange) ()
#17 0x0000555555e62a5a in UserMetric::compute(RideItem*, Specification, QHash<QString, RideMetric*> const&) ()
#18 0x0000555555e32572 in RideMetric::computeMetrics(RideItem*, Specification, QStringList const&) ()
#19 0x0000555555b029a1 in RideItem::refresh() ()
#20 0x0000555555af216a in RideCache::addRide(QString, bool, bool, bool, bool) ()
#21 0x0000555555a8c803 in Athlete::addRide(QString, bool, bool, bool, bool) ()
#22 0x0000555555d381ea in RideImportWizard::abortClicked() ()
#23 0x00007fffeae8a739 in ?? () from /tmp/.mount_GoldenQVRAIY/lib/libQt5Core.so.5
#24 0x00007ffff4bd3552 in QAbstractButton::clicked(bool) () from /tmp/.mount_GoldenQVRAIY/lib/libQt5Widgets.so.5
#25 0x00007ffff4bd376a in ?? () from /tmp/.mount_GoldenQVRAIY/lib/libQt5Widgets.so.5
#26 0x00007ffff4bd4b4a in ?? () from /tmp/.mount_GoldenQVRAIY/lib/libQt5Widgets.so.5
#27 0x00007ffff4bd4d3d in QAbstractButton::mouseReleaseEvent(QMouseEvent*) () from /tmp/.mount_GoldenQVRAIY/lib/libQt5Widgets.so.5
#28 0x00007ffff4b288d8 in QWidget::event(QEvent*) () from /tmp/.mount_GoldenQVRAIY/lib/libQt5Widgets.so.5
#29 0x00007ffff4ae79bc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /tmp/.mount_GoldenQVRAIY/lib/libQt5Widgets.so.5
#30 0x00007ffff4aefa08 in QApplication::notify(QObject*, QEvent*) () from /tmp/.mount_GoldenQVRAIY/lib/libQt5Widgets.so.5
#31 0x00007fffeae4f728 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /tmp/.mount_GoldenQVRAIY/lib/libQt5Core.so.5
#32 0x00007ffff4aee08f in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool, bool) () from /tmp/.mount_GoldenQVRAIY/lib/libQt5Widgets.so.5
#33 0x00007ffff4b42f91 in ?? () from /tmp/.mount_GoldenQVRAIY/lib/libQt5Widgets.so.5
#34 0x00007ffff4b45c3a in ?? () from /tmp/.mount_GoldenQVRAIY/lib/libQt5Widgets.so.5
#35 0x00007ffff4ae79bc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /tmp/.mount_GoldenQVRAIY/lib/libQt5Widgets.so.5
#36 0x00007ffff4aeebc0 in QApplication::notify(QObject*, QEvent*) () from /tmp/.mount_GoldenQVRAIY/lib/libQt5Widgets.so.5
#37 0x00007fffeae4f728 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /tmp/.mount_GoldenQVRAIY/lib/libQt5Core.so.5
#38 0x00007fffec67b865 in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () from /tmp/.mount_GoldenQVRAIY/lib/libQt5Gui.so.5
#39 0x00007fffec67c995 in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) () from /tmp/.mount_GoldenQVRAIY/lib/libQt5Gui.so.5
#40 0x00007fffec65517b in QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /tmp/.mount_GoldenQVRAIY/lib/libQt5Gui.so.5
#41 0x00007fffdc8ec9da in ?? () from /tmp/.mount_GoldenQVRAIY/plugins/platforms/../../lib/libQt5XcbQpa.so.5
#42 0x00007fffe2d7a537 in g_main_context_dispatch () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#43 0x00007fffe2d7a770 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#44 0x00007fffe2d7a7fc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#45 0x00007fffeaeaea2c in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /tmp/.mount_GoldenQVRAIY/lib/libQt5Core.so.5
#46 0x00007fffeae4dfaa in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /tmp/.mount_GoldenQVRAIY/lib/libQt5Core.so.5
#47 0x00007fffeae57720 in QCoreApplication::exec() () from /tmp/.mount_GoldenQVRAIY/lib/libQt5Core.so.5
#48 0x00005555556e91fb in main ()
(gdb)

[pinaman]

Extra info if needed. My OS is Linux Mint 19.3 xfce 64-bit.

[Ale Martinez]

El lunes, 12 de julio de 2021 a la(s) 06:16:27 UTC-3, pinaman escribió:

Extra info if needed. My OS is Linux Mint 19.3 xfce 64-bit.

On Monday, 12 July 2021 at 10:30:52 UTC+2 pinaman wrote:

Thanks for info. I was able to exit it, i just thought it might be related to crash / problem.

So here is backtrace data:

Thanks, it is a problem similar to the one already fixed with Python charts, but in this case with a Python script inside a user metric which calls GC.seasonMetrics on activity import. Until this is fixed the only solution is to remove that call, or go back to previous dev build.

 

(gdb) bt
#0  0x0000555555d7c565 in Perspective::filterlist(DateRange) ()
#1  0x0000555555740a54 in Bindings::seasonMetrics(bool, DateRange, QString) const ()
#2  0x000055555574208e in Bindings::seasonMetrics(bool, QString, bool) const ()
#3  0x000055555572edd9 in meth_Bindings_seasonMetrics ()
#4  0x00007ffff6f010eb in _PyMethodDef_RawFastCallKeywords () from /tmp/.mount_GoldenQVRAIY/lib/libpython3.7m.so.1.0
#5  0x00007ffff6f00e70 in _PyCFunction_FastCallKeywords () from /tmp/.mount_GoldenQVRAIY/lib/libpython3.7m.so.1.0
#6  0x00007ffff6f8cceb in _PyEval_EvalFrameDefault () from /tmp/.mount_GoldenQVRAIY/lib/libpython3.7m.so.1.0
#7  0x00007ffff6f87473 in _PyEval_EvalCodeWithName () from /tmp/.mount_GoldenQVRAIY/lib/libpython3.7m.so.1.0
#8  0x00007ffff6f87193 in PyEval_EvalCodeEx () from /tmp/.mount_GoldenQVRAIY/lib/libpython3.7m.so.1.0
#9  0x00007ffff6f8714b in PyEval_EvalCode () from /tmp/.mount_GoldenQVRAIY/lib/libpython3.7m.so.1.0
#10 0x00007ffff702e282 in ?? () from /tmp/.mount_GoldenQVRAIY/lib/libpython3.7m.so.1.0
#11 0x00007ffff702e22a in PyRun_StringFlags () from /tmp/.mount_GoldenQVRAIY/lib/libpython3.7m.so.1.0
#12 0x00007ffff702e17c in PyRun_SimpleStringFlags () from /tmp/.mount_GoldenQVRAIY/lib/libpython3.7m.so.1.0
#13 0x000055555571e92b in PythonEmbed::runline(ScriptContext, QString) ()
#14 0x0000555555aa2ebb in DataFilterRuntime::runPythonScript(Context*, QString, RideItem*, QHash<QString, RideMetric*> const*, Specification) ()

Here python=> perspective needs to be set

https://github.com/GoldenCheetah/GoldenCheetah/blob/b7380389071fc638019a2acf1888be9ad1f0e7a5/src/Core/DataFilter.cpp#L689

Or the code calling perspective->filterlist needs to check for null pointer, since I don’t know if there in an applicable perspective in this case.

[pinaman]

Thanks for info! I like new perspective feature, but is not critically important for me. So i will just use June version until is fixed. And i can report back when new version is available. I usually update as soon as new version is available.

[Laurent Caron]

Hi,

I updated from 3.6 DEV June version (working fine) to 3.6 DEV July version and I am now getting crashes when opening the Trends tab.

Below is the crash log, let me know if I can provide anything else to help!

Thanks,

Laurent

Unhandled exception 0xc0000005

RAX=0 RCX=7ff6de12dd68 RDX=0 RBX=1eb02c9bd10

RSP=b7856f8670 RBP=b7856f8770 RSI=0 RDI=0

R8=8 R9=1eb6fc87920 R10=4c5431f3 R11=1eb6fc67590

R12=1eb049b42c0 R13=c R14=1eb7a0a2d70 R15=1eb02c9bd10

GoldenCheetah.exe@0x7ff6dd250000!+0x1a279c

GoldenCheetah.exe@0x7ff6dd250000!+0x1aeeeb

GoldenCheetah.exe@0x7ff6dd250000!+0x1afab4

GoldenCheetah.exe@0x7ff6dd250000!+0x1bc81f

GoldenCheetah.exe@0x7ff6dd250000!+0x634b46

Qt5Core.dll!QObject::qt_static_metacall+0xcfd

Qt5Widgets.dll!QCheckBox::checkStateSet+0x8d

Qt5Widgets.dll!QAbstractButton::setChecked+0xbe

GoldenCheetah.exe@0x7ff6dd250000!+0x635548

GoldenCheetah.exe@0x7ff6dd250000!+0x63582c

Qt5Core.dll!QMetaProperty::write+0x4d1

Qt5Core.dll!QObject::setProperty+0x4bd

GoldenCheetah.exe@0x7ff6dd250000!+0x46f3a8

Qt5Xml.dll!QXmlNamespaceSupport::prefixes+0x75d

Qt5Xml.dll!QXmlSimpleReader::parseContinue+0x9f8

Qt5Xml.dll!QXmlSimpleReader::parse+0x20e5

Qt5Xml.dll!QXmlSimpleReader::parseContinue+0x9d8

Qt5Xml.dll!QXmlSimpleReader::parse+0x20e5

Qt5Xml.dll!QXmlSimpleReader::parseContinue+0x9d8

Qt5Xml.dll!QXmlSimpleReader::parse+0x1361

Qt5Xml.dll!QXmlSimpleReader::parse+0x1d6

GoldenCheetah.exe@0x7ff6dd250000!+0x46d1d6

GoldenCheetah.exe@0x7ff6dd250000!+0x46e051

GoldenCheetah.exe@0x7ff6dd250000!+0x4304cd

Qt5Core.dll!QObject::qt_static_metacall+0xcfd

GoldenCheetah.exe@0x7ff6dd250000!+0x651360

GoldenCheetah.exe@0x7ff6dd250000!+0x481123

Qt5Core.dll!QCoreApplicationPrivate::sendThroughObjectEventFilters+0xd7

Qt5Widgets.dll!QApplicationPrivate::notify_helper+0x126

Qt5Widgets.dll!QApplication::notify+0x8a9

Qt5Core.dll!QCoreApplication::notifyInternal2+0xb9

Qt5Widgets.dll!QApplicationPrivate::sendMouseEvent+0x3e3

Qt5Widgets.dll!QSizePolicy::QSizePolicy+0x2de0

Qt5Widgets.dll!QSizePolicy::QSizePolicy+0xb95

Qt5Widgets.dll!QApplicationPrivate::notify_helper+0x13a

Qt5Widgets.dll!QApplication::notify+0x1bc7

Qt5Core.dll!QCoreApplication::notifyInternal2+0xb9

Qt5Gui.dll!QGuiApplicationPrivate::processMouseEvent+0x911

Qt5Gui.dll!QWindowSystemInterface::sendWindowSystemEvents+0x9b

Qt5Core.dll!QEventDispatcherWin32::processEvents+0x70

qwindows.dll!qt_plugin_query_metadata+0x1ea9

Qt5Core.dll!QEventLoop::exec+0x1eb

Qt5Core.dll!QCoreApplication::exec+0x15e

GoldenCheetah.exe@0x7ff6dd250000!+0x2e1133

GoldenCheetah.exe@0x7ff6dd250000!+0x6b23f7

GoldenCheetah.exe@0x7ff6dd250000!+0x6b1a46

KERNEL32.DLL!BaseThreadInitThunk+0x14

ntdll.dll!RtlUserThreadStart+0x21

[Rui_B]

I was reviewing this conversation looking to see if a new version had been posted addressing the said issues... I notice both Mark & I are both on MacOS 11.4, but the About GC panel indicates MacOS 10.16 — not sure if this was the compiling  OS version or misplaced pointer, or if this is an issue at all. 

On Sunday, July 11, 2021 at 12:21:44 AM UTC-7 Mark Liversedge wrote:

[Ale Martinez]

El lunes, 2 de agosto de 2021 a la(s) 16:31:49 UTC-3, Rui_B escribió:

I was reviewing this conversation looking to see if a new version had been posted addressing the said issues... I notice both Mark & I are both on MacOS 11.4, but the About GC panel indicates MacOS 10.16 — not sure if this was the compiling  OS version or misplaced pointer, or if this is an issue at all. 

It's cosmetic, but I will fix it, see https://github.com/GoldenCheetah/GoldenCheetah/issues/3991

[Rui_B]

Thx Ale

r

[Laurent Caron]

Update:

Getting same error with v3.6-DEV2107 installed on another Windows computer.

Rolling back to v3.6-DEV2106 in the mean time.

Thanks,

Laurent

[Ale Martinez]

El domingo, 8 de agosto de 2021 a la(s) 20:03:11 UTC-3, laurent...@gmail.com escribió:

Update:

Getting same error with v3.6-DEV2107 installed on another Windows computer.

Perspectives introduced in v3.6-DEV2107 are work in progress, some issues are already fixed in current master, and more will be included in 2108 dev build, since you are on Windows you could install latest master build (see https://groups.google.com/g/golden-cheetah-developers/c/5fZUO9DbJDY), or perhaps better wait for the next dev build

 

Rolling back to v3.6-DEV2106 in the mean time.

 Testing the new features in v3.6-DEV2107 and later is (very) welcome, but you will likely find some glitches.

 For users who are looking for a stable build for daily use, v3.6-DEV2106 is the way to go until the new features are debugged.

[Laurent Caron]

Did not know of the master builds artefacts! Thanks Ale.

I just tried again with commit 95cd28a build artefact and I am still unable to open the Trends tab without crashing the app.

I do not code in C++ so unfortunately my debugging abilities are limited at this point. Let me know if I can still help

Laurent

[Ale Martinez]

El martes, 10 de agosto de 2021 a la(s) 09:12:59 UTC-3, laurent...@gmail.com escribió:

Did not know of the master builds artefacts! Thanks Ale.

I just tried again with commit 95cd28a build artefact and I am still unable to open the Trends tab without crashing the app.

I do not code in C++ so unfortunately my debugging abilities are limited at this point. Let me know if I can still help

Sometimes the crash.log file can give a hint, but not always.

Since the problem is happening when you activate Trends the problem can be related to the first chart in that view, which is it?

If you attach config\trends-layout.xml I can give it a look.  

[Ale Martinez]

config\home-layout.xml is the layout file for Trends view, sorry. 

[Laurent Caron]

Thanks for the hints Ale.

I did some playing around, and here are my conclusions:

• The culrpit was   <property name="showCSLinear" type="bool" value="0" />  in the CV chart
• I found the issue doing some trial and error with XML files. I created a new athlete with fresh configs, which worked. From there, I used the "bisection method", adding/removing half of the diff between the fresh athlete and my config, until I found the issue. I stumbled upon a few things doing so:

1. My home-layout.xml was duplicated (Chart 1, ..., Chart n, Chart 1, ..., Chart n). Looking at my backups, this most likely happened when updating from June to July
   
2. The summary tab was not removed from the config
3. The overview tab was not added to the config

I fixed all of the above manually.

I am assuming some code changes relate to how the app interacts with the configs, whereas some code changes relate to how moving from one version to the next updates/moves files around. So first bullet seems to be the first case, while second bullet seems to be the second case

Let me know if I should provide more details or replicate any parts of the above.

Thanks,

Laurent

[Alan Ordóñez]

I am facing the same problem, GC crash when I open the "Trends" tab.

[Ale Martinez]

El lunes, 18 de octubre de 2021 a la(s) 04:25:23 UTC-3, alan.or...@sansano.usm.cl escribió:

I am facing the same problem, GC crash when I open the "Trends" tab.

 

See https://groups.google.com/g/golden-cheetah-users/c/uBOSQ9XerXQ/m/ifFr6oFlBgAJ

[Manu]

I comment this here but in my case it afeccts all 3.6 devs (win 10 user)

When i try to type @ into golden cheeath it doesn´t work.

I know it happens to more friends. I tried to search in the forum but didn´t find anything.

Thanks in advance.

[Ale Martinez]

El viernes, 22 de octubre de 2021 a la(s) 04:38:09 UTC-3, Manu escribió:

I comment this here but in my case it afeccts all 3.6 devs (win 10 user)

When i try to type @ into golden cheeath it doesn´t work.

I know it happens to more friends. I tried to search in the forum but didn´t find anything.

https://groups.google.com/g/golden-cheetah-users/c/bJCO8c3ck-c/m/kCc0JUBmAwAJ 

[Manu]

Thanks Ale, didn´t  see that thread. Confirm that it doesn´t work on 3.6 (worked fine on 3.5). Spanish keyboard.

Sorry for asking again. Keep on the superb work all of you are doing.

[Mauve Freire]

Hello! I just installed that last version but my GC crashes 100% of the times I click on "Trends". It started happening to me with 3.6 august beta, I tried the latest "unstable" beta, and now this version you mentiones but no luck, it crashes all the time.

I installed some graphics/metrics from https://frikisdelabici.com/site/descarga-de-utilidades-graficas-y-ayuda/ but they used to work. Maybe something went wrong when I updated to 3.6.

How can I delete/clean up those graphics/metrics? Or where should I start to look for a solution?

Thank you all!

[Ale Martinez]

El miércoles, 3 de noviembre de 2021 a la(s) 04:46:05 UTC-3, hola...@gmail.com escribió:

Hello! I just installed that last version but my GC crashes 100% of the times I click on "Trends". It started happening to me with 3.6 august beta, I tried the latest "unstable" beta, and now this version you mentiones but no luck, it crashes all the time.

I installed some graphics/metrics from https://frikisdelabici.com/site/descarga-de-utilidades-graficas-y-ayuda/ but they used to work. Maybe something went wrong when I updated to 3.6.

How can I delete/clean up those graphics/metrics?

 You can delete Trends charts removing config/home-layout.xml and config/home-perspectives.xml under your athlete’s folder.

Or where should I start to look for a solution?

For Windows there is a newer version with some fixes and better debugging info, see: https://groups.google.com/g/golden-cheetah-users/c/uBOSQ9XerXQ/m/ifFr6oFlBgAJ 

[Mauve Freire]

Thank you so much Ale. Deleting those files made Trends work again.

Have a nice day!