if more than one rider is open, GC does not provide a menu method to switch rider windows.

this is especially problematic if one window is minimized as there is no menu option for accessing the minimized window.

also it GC does not respect OS specific window switching (CMD+~ on osx) to "find" the other window.

the only way to access it is reopening the rider.

Associated revisions

Revision eb45055
Added by Mark Liversedge about 1 year ago

Reinstate View and add Window menu

View menu reinstated to allow users to show
or hide the toolbar and sidebar as well as
select layout views; home, analysis et al.

Also added a window menu option to switch
between the current open windows. This is
particularly useful if the other windows
are on another virtual screen.

Fixes #367.
Fixes #29.

History
#1 Updated by Justin Knotzke over 2 years ago

Status changed from New to Feedback
Priority changed from High to Low
GoldenCheetah Version changed from developer to 1.3.0
This is because when you create a new cyclist, you aren't creating a new application but are creating a new window.
If you were to create a new window in Safari, for instance the second window would not appear when using CMD+Tab. I would classify this as a feature request.
#2 Updated by Robert Carlsen over 2 years ago

Command+~ (tilde) should switch between open windows of the same application. We'll have to see if it's lacking in Qt or our implementation.
#3 Updated by Justin Knotzke over 2 years ago

Ah Command ~

Well in this case it works for me.
#4 Updated by greg steele over 2 years ago

command+~ does switch between two open riders... when neither is minimized.

if you minimize the window to the taskbar, there is no way of retrieving it except for right+clicking the icon on the taskbar...

there (in OSX) should be a window menu item to "resurrect" these minimized windows - this appears to be an OS standard.

g
#5 Updated by Justin Knotzke over 2 years ago

Status changed from Feedback to New
This is different from standard OS X. It might be a Qt issue. One that we don't have control over. I'll leave it as a bug, but it's low priority.
#6 Updated by Mark Liversedge over 1 year ago

Target version set to 3.1
Patch Attached set to No
#7 Updated by Mark Liversedge about 1 year ago

Status changed from New to Closed
% Done changed from 0 to 100
Applied in changeset eb45055.

The google map creates a temporary file called 'maps.html' in the O/S specific temp directory (e.g. /tmp/maps.html on Linux). If you have multiple users on the same host using GoldenCheetah the file will not be writable by one of the users (O/S level permissions) and this will cause the map to display the last map displayed by whichever user DOES have permissions to write.

Should fix by using a temporary & unique filename and unlinking it once it is no longer required.

Associated revisions

Revision 4851dfc
Added by Mark Liversedge over 1 year ago

Fix temp file permissions issue with Google Map

The google map control creates a temporary file to load
which is not unique for each logged in user. This causes
permissions issues.

The use of a temporary file has been removed by replacing
the webView->load() call with a webView->setHtml() call. This
allows us to pass the contents as a string rather than a URL.

Fixes #331.

History
#1 Updated by Mark Liversedge over 1 year ago

Status changed from New to Closed
% Done changed from 0 to 100
Applied in changeset 4851dfc.

Exercise files that have been created under Windows ((at the Office))XP Pro 32 bit, Garmin Edge 500) can`t be red using Ubuntu 10.4 (at home) and the other way round in the critical power plot. I use an installation of GC on a USB memory stick and have both versions, Linux and windows installed in the same directory using the same library of exercise files.
Currently i am using a nightly build: 2011-01-09, but the problem appeared also with other versions. All other plots seam to work properly

Example of an error:
"Error Reading
K:/GoldenCheetah/Library/GoldenCheetah/xxx.cpi, line 0,017

i have attached a recent file that doesn`t work under Win XP
746"

2011_04_25_15_00_13.cpi - File that was created using Linux, doesn`t work under WinXp (185.8 kB) hejman komarac, 27/04/2011 04:52 am
History
#1 Updated by Mark Liversedge over 1 year ago

Status changed from New to Closed
Target version set to 3.0
Fixed in v3.0 with a cross platform .cpx file

Hi,
I reported a bug a couple months ago (#715) where GC crashed after downloading from an SRM PC V when the last file created on the PC V ended with the PC V's battery dying. However, now I'm having a similar problem with what seems to be a normal file. Erased it and created a new file, same result, GC crashes until corrupt file is deleted.

I'll attach one of the offending files, as well as paste the error report below.

Thanks a million for the help!
Elliot

Process: GoldenCheetah [7034]
Path: /Volumes/VOLUME/GoldenCheetah.app/Contents/MacOS/GoldenCheetah
Identifier: com.yourcompany.GoldenCheetah
Version: ? (?)
Code Type: X86 (Native)
Parent Process: launchd [117]

Date/Time: 2012-10-21 18:17:00.729 -0700
OS Version: Mac OS X 10.7.5 (11G63)
Report Version: 9
Sleep/Wake UUID: 16E2FB62-6796-4E91-AFF6-6FCFA1F25CBA

Interval Since Last Report: 98512 sec
Crashes Since Last Report: 9
Per-App Interval Since Last Report: 26583 sec
Per-App Crashes Since Last Report: 7
Anonymous UUID: DC0DA2B0-BD12-49EB-A9CE-41D175FF953B

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000

Application Specific Information:
abort() called
objc7034: garbage collection is OFF

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libsystem_kernel.dylib 0x964089c6 pthread_kill + 10
1 libsystem_c.dylib 0x90194f78 pthread_kill + 106
2 libsystem_c.dylib 0x90185bdd abort + 167
3 QtCore 0x020c1bb5 qt_message_output(QtMsgType, char const) + 149
4 QtCore 0x020c1d7a qt_message_output(QtMsgType, char const) + 602
5 QtCore 0x020c1eb9 qFatal(char const_, ...) + 25
6 QtCore 0x020c1ef7 qt_assert_x(char const_, char const_, char const_, int) + 55
7 com.yourcompany.GoldenCheetah 0x0009cada QVector<RideFilePoint*>::operator const + 74
8 com.yourcompany.GoldenCheetah 0x0020e91c SrmFileReader::openRideFile(QFile&, QStringList&) const + 5784
9 com.yourcompany.GoldenCheetah 0x001cfe1f RideFileFactory::openRideFile(QFile&, QStringList&) const + 399
10 com.yourcompany.GoldenCheetah 0x001e1970 RideItem::ride() + 238
11 com.yourcompany.GoldenCheetah 0x001e8a09 FormField::rideSelected() + 71
12 com.yourcompany.GoldenCheetah 0x00250eba FormField::qt_metacall(QMetaObject::Call, int, void**) + 138
13 QtCore 0x021ea242 QMetaObject::activate(QObject_, QMetaObject const_, int, void**) + 594
14 com.yourcompany.GoldenCheetah 0x00249f86 MainWindow::rideSelected() + 50
15 com.yourcompany.GoldenCheetah 0x00111915 MainWindow::rideTreeWidgetSelectionChanged() + 423
16 com.yourcompany.GoldenCheetah 0x0024a1cf MainWindow::qt_metacall(QMetaObject::Call, int, void**) + 579
17 QtCore 0x021ea242 QMetaObject::activate(QObject_, QMetaObject const_, int, void**) + 594
18 QtGui 0x02b3c772 QTreeWidget::itemSelectionChanged() + 50
19 QtGui 0x02b3f164 QTreeWidget::findItems(QString const&, QFlagsQt::MatchFlag, int) const + 692
20 QtGui 0x02b45509 QTreeWidget::qt_metacall(QMetaObject::Call, int, void**) + 841
21 QtCore 0x021ea242 QMetaObject::activate(QObject_, QMetaObject const_, int, void**) + 594
22 QtGui 0x02b17704 QItemSelectionModel::selectionChanged(QItemSelection const&, QItemSelection const&) + 68
23 QtGui 0x02b1b0d0 QItemSelectionModel::emitSelectionChanged(QItemSelection const&, QItemSelection const&) + 928
24 QtGui 0x02b1fcdd QItemSelectionModel::select(QItemSelection const&, QFlagsQItemSelectionModel::SelectionFlag) + 589
25 QtGui 0x02b1a982 QItemSelectionModel::select(QModelIndex const&, QFlagsQItemSelectionModel::SelectionFlag) + 66
26 QtGui 0x02b17a68 QItemSelectionModel::setCurrentIndex(QModelIndex const&, QFlagsQItemSelectionModel::SelectionFlag) + 328
27 QtGui 0x02abddb2 QAbstractItemView::setCurrentIndex(QModelIndex const&) + 162
28 QtGui 0x02b43c7f QTreeWidget::setCurrentItem(QTreeWidgetItem_, int) + 95
29 QtGui 0x02b43cc0 QTreeWidget::setCurrentItem(QTreeWidgetItem_) + 32
30 com.yourcompany.GoldenCheetah 0x001108f6 MainWindow::addRide(QString, bool) + 1248
31 com.yourcompany.GoldenCheetah 0x000adcdf DownloadRideDialog::downloadClicked() + 3743
32 com.yourcompany.GoldenCheetah 0x00247d63 DownloadRideDialog::qt_metacall(QMetaObject::Call, int, void**) + 131
33 QtCore 0x021ea242 QMetaObject::activate(QObject_, QMetaObject const_, int, void**) + 594
34 QtGui 0x02c4a1d4 QAbstractButton::clicked(bool) + 68
35 QtGui 0x02944fd6 QAbstractButton::mousePressEvent(QMouseEvent_) + 198
36 QtGui 0x029450eb QAbstractButton::mousePressEvent(QMouseEvent_) + 475
37 QtGui 0x0294534c QAbstractButton::mouseReleaseEvent(QMouseEvent_) + 140
38 QtGui 0x025872b3 QWidget::event(QEvent_) + 4323
39 QtGui 0x02945bb3 QAbstractButton::event(QEvent_) + 83
40 QtGui 0x029ec5e1 QPushButton::event(QEvent_) + 65
41 QtGui 0x0252d67f QApplicationPrivate::notify_helper(QObject_, QEvent_) + 175
42 QtGui 0x025339d2 QApplication::notify(QObject_, QEvent_) + 2690
43 QtCore 0x021d16f2 QCoreApplication::notifyInternal(QObject_, QEvent_) + 98
44 QtGui 0x0252b13c QApplication::palette(QWidget const*) + 428
45 QtGui 0x024dd192 QMacCocoaAutoReleasePool::~QMacCocoaAutoReleasePool() + 17282
46 QtGui 0x024ce44f QMacInputContext::isComposing() const + 9839
47 com.apple.AppKit 0x9b983ecb -[NSWindow sendEvent:] + 7787
48 QtGui 0x024cb354 non-virtual thunk to QWidget::metric(QPaintDevice::PaintDeviceMetric) const + 5684
49 com.apple.AppKit 0x9b91cf77 -[NSApplication sendEvent:] + 4788
50 QtGui 0x024d774a QMacInputContext::isComposing() const + 47466
51 com.apple.AppKit 0x9b8aeb21 -[NSApplication run] + 1007
52 QtGui 0x024e1e11 non-virtual thunk to QDesktopWidget::~QDesktopWidget() + 11905
53 QtCore 0x021d0741 QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) + 65
54 QtCore 0x021d097d QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) + 189
55 QtCore 0x021d49fe QCoreApplication::exec() + 174
56 com.yourcompany.GoldenCheetah 0x00242a49 main + 4485
57 com.yourcompany.GoldenCheetah 0x000084b2 _start + 216
58 com.yourcompany.GoldenCheetah 0x000083d9 start + 41

Thread 1:: Dispatch queue: com.apple.libdispatch-manager
0 libsystem_kernel.dylib 0x9640990a kevent + 10
1 libdispatch.dylib 0x993b3e04 _dispatch_mgr_invoke + 969
2 libdispatch.dylib 0x993b2853 _dispatch_mgr_thread + 53

Thread 2:
0 libsystem_kernel.dylib 0x96408b5e __select_nocancel + 10
1 libsystem_kernel.dylib 0x96407af6 select + 89
2 QtCore 0x021a81f8 QFSFileEngine::drives() + 9128
3 QtCore 0x020cb33f QThread::setTerminationEnabled(bool) + 271
4 libsystem_c.dylib 0x90192ed9 _pthread_start + 335
5 libsystem_c.dylib 0x901966de thread_start + 34

Thread 3:
0 libsystem_kernel.dylib 0x9640990a kevent + 10
1 QtCore 0x021b3cf2 QFSFileEngine::drives() + 56994
2 QtCore 0x020cb33f QThread::setTerminationEnabled(bool) + 271
3 libsystem_c.dylib 0x90192ed9 _pthread_start + 335
4 libsystem_c.dylib 0x901966de thread_start + 34

Thread 4:
0 libsystem_kernel.dylib 0x9640883e __psynch_cvwait + 10
1 libsystem_c.dylib 0x90196e78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x9013e82a pthread_cond_wait + 48
3 QtWebKit 0x018e9115 JSValueProtect + 1604165
4 QtWebKit 0x018e91b1 JSValueProtect + 1604321
5 libsystem_c.dylib 0x90192ed9 _pthread_start + 335
6 libsystem_c.dylib 0x901966de thread_start + 34

Thread 5:
0 libsystem_kernel.dylib 0x96408b5e select_nocancel + 10
1 libsystem_kernel.dylib 0x96407af6 select + 89
2 QtCore 0x021fdcf2 qt_safe_select(int, fd_set, fd_set, fd_set_, timeval const_) + 82
3 QtCore 0x022014a3 QEventDispatcherUNIXPrivate::doSelect(QFlagsQEventLoop::ProcessEventsFlag, timeval*) + 451
4 QtCore 0x02202c5c QEventDispatcherUNIX::processEvents(QFlagsQEventLoop::ProcessEventsFlag) + 156
5 QtCore 0x021d0741 QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) + 65
6 QtCore 0x021d097d QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) + 189
7 QtCore 0x020c953d QThread::exec() + 157
8 QtCore 0x020cb33f QThread::setTerminationEnabled(bool) + 271
9 libsystem_c.dylib 0x90192ed9 _pthread_start + 335
10 libsystem_c.dylib 0x901966de thread_start + 34

Thread 6:
0 libsystem_kernel.dylib 0x9640902e __workq_kernreturn + 10
1 libsystem_c.dylib 0x90194ccf _pthread_wqthread + 773
2 libsystem_c.dylib 0x901966fe start_wqthread + 30

Thread 7:
0 libsystem_kernel.dylib 0x9640902e __workq_kernreturn + 10
1 libsystem_c.dylib 0x90194ccf _pthread_wqthread + 773
2 libsystem_c.dylib 0x901966fe start_wqthread + 30

Thread 0 crashed with X86 Thread State (32-bit):
eax: 0x00000000 ebx: 0x020c1b2e ecx: 0xbfffdafc edx: 0x964089c6
edi: 0xac0212c0 esi: 0x00000006 ebp: 0xbfffdb18 esp: 0xbfffdafc
ss: 0x00000023 efl: 0x00200246 eip: 0x964089c6 cs: 0x0000000b
ds: 0x00000023 es: 0x00000023 fs: 0x00000000 gs: 0x0000000f
cr2: 0x0e4ec000
Logical CPU: 0

Binary Images:
0x1000 - 0x48ffef com.yourcompany.GoldenCheetah (? - ?) /Volumes/VOLUME/GoldenCheetah.app/Contents/MacOS/GoldenCheetah
0x754000 - 0x757ffd +liboauth.0.dylib (7.0.0 - compatibility 7.0.0) <1722EABE-2547-EC38-446F-A9FEE70E62D5> /Volumes/VOLUME/GoldenCheetah.app/Contents/Frameworks/liboauth.0.dylib
0x75c000 - 0x809ff7 libcrypto.0.9.7.dylib (0.9.7 - compatibility 0.9.7) <7B6DB792-C9E5-3772-8734-8D0052757B8C> /usr/lib/libcrypto.0.9.7.dylib
0x84e000 - 0x8edff7 +libkmldom.0.dylib (? - ?) /Volumes/VOLUME/GoldenCheetah.app/Contents/Frameworks/libkmldom.0.dylib
0x988000 - 0x9a8ffe +libkmlconvenience.0.dylib (? - ?) <6B47D3D8-F0B0-395C-6BD3-A890B7EC57CB> /Volumes/VOLUME/GoldenCheetah.app/Contents/Frameworks/libkmlconvenience.0.dylib
0x9c9000 - 0xa03ff7 +libkmlengine.0.dylib (? - ?) <7570A1C0-7074-4148-C393-82FD9931FDA4> /Volumes/VOLUME/GoldenCheetah.app/Contents/Frameworks/libkmlengine.0.dylib
0xa45000 - 0xa53fff +libkmlbase.0.dylib (? - ?) /Volumes/VOLUME/GoldenCheetah.app/Contents/Frameworks/libkmlbase.0.dylib
0xa61000 - 0x1c49fe2 +QtWebKit (4.7.4 - compatibility 4.7.0) <87B787F8-0FA0-6BC2-AB8A-851F478EA892> /Volumes/VOLUME/GoldenCheetah.app/Contents/Frameworks/QtWebKit.framework/Versions/4/QtWebKit
0x2002000 - 0x2093fef +QtSql (4.7.4 - compatibility 4.7.0) /Volumes/VOLUME/GoldenCheetah.app/Contents/Frameworks/QtSql.framework/Versions/4/QtSql
0x20ac000 - 0x22d9fe3 +QtCore (4.7.4 - compatibility 4.7.0) /Volumes/VOLUME/GoldenCheetah.app/Contents/Frameworks/QtCore.framework/Versions/4/QtCore
0x2355000 - 0x23a0fff +QtXml (4.7.4 - compatibility 4.7.0) <5D8175E5-14BB-D1BD-0EB5-7AE7AE02DD43> /Volumes/VOLUME/GoldenCheetah.app/Contents/Frameworks/QtXml.framework/Versions/4/QtXml
0x23b9000 - 0x2476fee +QtOpenGL (4.7.4 - compatibility 4.7.0) <2637F739-E4EE-FDA3-E1D8-A585B1F2BE4E> /Volumes/VOLUME/GoldenCheetah.app/Contents/Frameworks/QtOpenGL.framework/Versions/4/QtOpenGL
0x24a4000 - 0x2dc8fe2 +QtGui (4.7.4 - compatibility 4.7.0) <4C7965CC-F709-81B3-BBFA-98A6C22F1EA5> /Volumes/VOLUME/GoldenCheetah.app/Contents/Frameworks/QtGui.framework/Versions/4/QtGui
0x2ff4000 - 0x30eafe2 +QtNetwork (4.7.4 - compatibility 4.7.0) <700FB92D-143B-8B27-EDA4-6AFFF8A93D77> /Volumes/VOLUME/GoldenCheetah.app/Contents/Frameworks/QtNetwork.framework/Versions/4/QtNetwork
0x3130000 - 0x3156ffb +libexpat.1.dylib (7.2.0 - compatibility 7.0.0) /Volumes/VOLUME/GoldenCheetah.app/Contents/Frameworks/libexpat.1.dylib
0x315c000 - 0x3161ffc +libminizip.0.dylib (? - ?) <4B38771E-9BE2-55A1-4C01-F9479B6952F6> /Volumes/VOLUME/GoldenCheetah.app/Contents/Frameworks/libminizip.0.dylib
0x3165000 - 0x3179fff +liburiparser.1.dylib (2.5.0 - compatibility 2.0.0) <8244A1C2-F28F-DA37-F2A0-C727CE9A9DB2> /Volumes/VOLUME/GoldenCheetah.app/Contents/Frameworks/liburiparser.1.dylib
0x317e000 - 0x31b5fe2 +phonon (4.4.0 - compatibility 4.4.0) /Volumes/VOLUME/GoldenCheetah.app/Contents/Frameworks/phonon.framework/Versions/4/phonon
0x31d0000 - 0x31e1feb +libz.1.dylib (1.2.5 - compatibility 1.0.0) <6ADAD283-82B4-1A69-50DA-7ADA6DF852D7> /Volumes/VOLUME/GoldenCheetah.app/Contents/Frameworks/libz.1.dylib
0x4fee000 - 0x4ff5fe8 +libqgenericbearer.dylib (? - ?) <9EB72DD7-4F09-B768-1256-ADCEEDE420A6> /Volumes/VOLUME/GoldenCheetah.app/Contents/PlugIns/bearer/libqgenericbearer.dylib
0x67c5000 - 0x67e5fe3 +libqcncodecs.dylib (? - ?) <5819D4E1-654A-79B4-9529-63E09B8A3383> /Volumes/VOLUME/GoldenCheetah.app/Contents/PlugIns/codecs/libqcncodecs.dylib
0x67e9000 - 0x67fafeb +libqkrcodecs.dylib (? - ?) /Volumes/VOLUME/GoldenCheetah.app/Contents/PlugIns/codecs/libqkrcodecs.dylib
0xa042000 - 0xa068fe9 +libqjpcodecs.dylib (? - ?) <2F80162B-8C5A-54EB-1DFC-BEA51F3D4C57> /Volumes/VOLUME/GoldenCheetah.app/Contents/PlugIns/codecs/libqjpcodecs.dylib
0xa06e000 - 0xa092ffb +libqtwcodecs.dylib (? - ?) <9D22190E-4EF6-1EA3-D103-FDDAE32F7082> /Volumes/VOLUME/GoldenCheetah.app/Contents/PlugIns/codecs/libqtwcodecs.dylib
0xa096000 - 0xa0a2ffb libGPUSupport.dylib (? - ?) /System/Library/PrivateFrameworks/GPUSupport.framework/Versions/A/Libraries/libGPUSupport.dylib
0xa0a9000 - 0xa0d6ff0 GLRendererFloat (? - ?) /System/Library/Frameworks/OpenGL.framework/Resources/GLRendererFloat.bundle/GLRendererFloat
0xa0df000 - 0xa0e8ff6 libcldcpuengine.dylib (2.0.19 - compatibility 1.0.0) <95A88DC8-E5EE-363F-9275-214D5AB7A2EF> /System/Library/Frameworks/OpenCL.framework/Versions/A/Libraries/libcldcpuengine.dylib
0xa0ef000 - 0xa0f1fff libCoreFSCache.dylib (? - ?) <9E7CBE71-566C-36E9-A49F-C5FF6956D76F> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreFSCache.dylib
0xa400000 - 0xa588ff9 GLEngine (? - ?) <84549EEF-900F-397A-AABC-47DD261F40BE> /System/Library/Frameworks/OpenGL.framework/Resources/GLEngine.bundle/GLEngine
0xa5bf000 - 0xa729ffb libGLProgrammability.dylib (? - ?) <169ED314-B937-3877-A7D7-4AFB96D8C561> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLProgrammability.dylib
0xa75c000 - 0xa760fff +libqgif.dylib (? - ?) /Volumes/VOLUME/GoldenCheetah.app/Contents/PlugIns/imageformats/libqgif.dylib
0xb000000 - 0xb381fef com.apple.driver.AppleIntelHD3000GraphicsGLDriver (7.32.12 - 7.3.2) /System/Library/Extensions/AppleIntelHD3000GraphicsGLDriver.bundle/Contents/MacOS/AppleIntelHD3000GraphicsGLDriver
0xb48c000 - 0xb490ff3 +libqico.dylib (? - ?) /Volumes/VOLUME/GoldenCheetah.app/Contents/PlugIns/imageformats/libqico.dylib
0xb495000 - 0xb4caff7 +libqjpeg.dylib (? - ?) /Volumes/VOLUME/GoldenCheetah.app/Contents/PlugIns/imageformats/libqjpeg.dylib
0xb782000 - 0xb7ccff7 +libqmng.dylib (? - ?) /Volumes/VOLUME/GoldenCheetah.app/Contents/PlugIns/imageformats/libqmng.dylib
0xc6a0000 - 0xc6eefeb +libqtiff.dylib (? - ?) /Volumes/VOLUME/GoldenCheetah.app/Contents/PlugIns/imageformats/libqtiff.dylib
0x8feb7000 - 0x8fee9aa7 dyld (195.6 - ?) <60FD3471-A1D7-342E-99A7-3EDECDAEC6EC> /usr/lib/dyld
0x90005000 - 0x9008cfff com.apple.print.framework.PrintCore (7.1 - 366.3) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/PrintCore.framework/Versions/A/PrintCore
0x900fa000 - 0x90124ff1 com.apple.CoreServicesInternal (113.19 - 113.19) /System/Library/PrivateFrameworks/CoreServicesInternal.framework/Versions/A/CoreServicesInternal
0x90136000 - 0x90201fff libsystem_c.dylib (763.13.0 - compatibility 1.0.0) <52421B00-79C8-3727-94DE-62F6820B9C31> /usr/lib/system/libsystem_c.dylib
0x90202000 - 0x9028ffe7 libvMisc.dylib (325.4.0 - compatibility 1.0.0) /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvMisc.dylib
0x902d3000 - 0x90317fff com.apple.MediaKit (12 - 602) <6E429DD7-8829-37DE-94AF-940FB70F2FB9> /System/Library/PrivateFrameworks/MediaKit.framework/Versions/A/MediaKit
0x90318000 - 0x9037cfff com.apple.framework.IOKit (2.0 - ?) <94827954-5906-36C4-819B-24CDAFD85C72> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
0x90388000 - 0x90391fff libc+abi.dylib (14.0.0 - compatibility 1.0.0) /usr/lib/libc++abi.dylib
0x903d0000 - 0x903d1fff com.apple.TrustEvaluationAgent (2.0 - 1) <4BB39578-2F5E-3A50-AD59-9C0AB99472EB> /System/Library/PrivateFrameworks/TrustEvaluationAgent.framework/Versions/A/TrustEvaluationAgent
0x903d2000 - 0x904e2fe7 libsqlite3.dylib (9.6.0 - compatibility 9.0.0) <34E1E3CC-7B6A-3B37-8D07-1258D11E16CB> /usr/lib/libsqlite3.dylib
0x90560000 - 0x90567ffd com.apple.NetFS (4.0 - 4.0) /System/Library/Frameworks/NetFS.framework/Versions/A/NetFS
0x90568000 - 0x9056fff9 libsystem_dnssd.dylib (? - ?) /usr/lib/system/libsystem_dnssd.dylib
0x90570000 - 0x90872fff com.apple.CoreServices.CarbonCore (960.25 - 960.25) /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore
0x90b6e000 - 0x90bc9ff3 com.apple.Symbolication (1.3 - 91) /System/Library/PrivateFrameworks/Symbolication.framework/Versions/A/Symbolication
0x90bca000 - 0x90bd8ff7 libxar-nossl.dylib (? - ?) <5BF4DA8E-C319-354A-967E-A0C725DC8BA3> /usr/lib/libxar-nossl.dylib
0x90bdf000 - 0x90c44ff7 libvDSP.dylib (325.4.0 - compatibility 1.0.0) <4B4B32D2-4F66-3B0D-BD61-FA8429FF8507> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvDSP.dylib
0x90c45000 - 0x90c4cff7 libsystem_notify.dylib (80.1.0 - compatibility 1.0.0) <47DB9E1B-A7D1-3818-A747-382B2C5D9E1B> /usr/lib/system/libsystem_notify.dylib
0x90dd8000 - 0x90e35ffb com.apple.htmlrendering (76 - 1.1.4) <409EF0CB-2997-369A-9326-BE12436B9EE1> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HTMLRendering.framework/Versions/A/HTMLRendering
0x90e36000 - 0x90edafff com.apple.QD (3.40 - ?) <3881BEC6-0908-3073-BA44-346356E1CDF9> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/QD.framework/Versions/A/QD
0x90edb000 - 0x90f43fff libc++.1.dylib (28.4.0 - compatibility 1.0.0) /usr/lib/libc++.1.dylib
0x911f7000 - 0x9120cff7 com.apple.ImageCapture (7.1.0 - 7.1.0) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/ImageCapture.framework/Versions/A/ImageCapture
0x91239000 - 0x91256ff3 com.apple.openscripting (1.3.3 - ?) <0579A4CB-FD6F-3D7F-A17B-AC0F2CF11FC7> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/OpenScripting.framework/Versions/A/OpenScripting
0x91257000 - 0x9144fff7 com.apple.CoreData (104.1 - 358.14) /System/Library/Frameworks/CoreData.framework/Versions/A/CoreData
0x91450000 - 0x915a6fff com.apple.audio.toolbox.AudioToolbox (1.7.3 - 1.7.3) /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox
0x915a7000 - 0x91609ff3 libstdc++.6.dylib (52.0.0 - compatibility 7.0.0) <266CE9B3-526A-3C41-BA58-7AE66A3B15FD> /usr/lib/libstdc++.6.dylib
0x916ad000 - 0x916b6ff3 com.apple.CommonAuth (2.2 - 2.0) /System/Library/PrivateFrameworks/CommonAuth.framework/Versions/A/CommonAuth
0x916b7000 - 0x916bbffa libcache.dylib (47.0.0 - compatibility 1.0.0) <56256537-6538-3522-BCB6-2C79DA6AC8CD> /usr/lib/system/libcache.dylib
0x916bc000 - 0x916bfff7 libcompiler_rt.dylib (6.0.0 - compatibility 1.0.0) <7F6C14CC-0169-3F1B-B89C-372F67F1F3B5> /usr/lib/system/libcompiler_rt.dylib
0x916f5000 - 0x91723ff7 com.apple.DictionaryServices (1.2.1 - 158.3) <8D03D180-D834-39F3-A106-78E0B22A7893> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/DictionaryServices.framework/Versions/A/DictionaryServices
0x91724000 - 0x91727ff9 libCGXType.A.dylib (600.0.0 - compatibility 64.0.0) <16DCE20A-9790-369A-94C1-B7954B418C77> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/CoreGraphics.framework/Versions/A/Resources/libCGXType.A.dylib
0x91729000 - 0x9172aff7 libquarantine.dylib (36.7.0 - compatibility 1.0.0) <46980EC2-149D-3CF7-B29A-401FB89C275D> /usr/lib/system/libquarantine.dylib
0x9172b000 - 0x917b5ffb com.apple.SearchKit (1.4.0 - 1.4.0) /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchKit.framework/Versions/A/SearchKit
0x917b6000 - 0x917befff com.apple.DiskArbitration (2.4.1 - 2.4.1) <28D5D8B5-14E8-3DA1-9085-B9BC96835ACF> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration
0x917bf000 - 0x917c1ffb libRadiance.dylib (? - ?) <4721057E-5A1F-3083-911B-200ED1CE7678> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/libRadiance.dylib
0x9203d000 - 0x9205fffe com.apple.framework.familycontrols (3.0 - 300) <6735D7ED-7053-3AB8-B144-E7F70A124CCD> /System/Library/PrivateFrameworks/FamilyControls.framework/Versions/A/FamilyControls
0x923ad000 - 0x923b1fff libGIF.dylib (? - ?) <2ADFED97-2228-343D-9A53-207CBFDE7984> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/libGIF.dylib
0x923e9000 - 0x926f3ff3 com.apple.Foundation (6.7.2 - 833.25) <4C52ED74-A1FD-3087-A2E1-035AB3CF9610> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
0x92932000 - 0x92968ff7 com.apple.AE (527.7 - 527.7) <7BAFBF18-3997-3656-9823-FD3B455056A4> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.framework/Versions/A/AE
0x929b9000 - 0x929c9fff libsasl2.2.dylib (3.15.0 - compatibility 3.0.0) /usr/lib/libsasl2.2.dylib
0x92a44000 - 0x92a81fef libGLImage.dylib (? - ?) /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLImage.dylib
0x92a82000 - 0x92a86fff com.apple.CommonPanels (1.2.5 - 94) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CommonPanels.framework/Versions/A/CommonPanels
0x92a87000 - 0x92aa3ff5 com.apple.GenerationalStorage (1.0 - 126.1) /System/Library/PrivateFrameworks/GenerationalStorage.framework/Versions/A/GenerationalStorage
0x92c10000 - 0x92c1bffe com.apple.NetAuth (3.2 - 3.2) <4377FB18-A550-35C6-BCD2-71C42134EEA6> /System/Library/PrivateFrameworks/NetAuth.framework/Versions/A/NetAuth
0x92c1c000 - 0x92c22ffd com.apple.CommerceCore (1.0 - 17) /System/Library/PrivateFrameworks/CommerceKit.framework/Versions/A/Frameworks/CommerceCore.framework/Versions/A/CommerceCore
0x93441000 - 0x93452fff libbsm.0.dylib (? - ?) <54ACF696-87C6-3652-808A-17BE7275C230> /usr/lib/libbsm.0.dylib
0x9373c000 - 0x9374fff8 com.apple.MultitouchSupport.framework (231.4 - 231.4) <083F7787-4C3B-31DA-B5BB-1993D9A9723D> /System/Library/PrivateFrameworks/MultitouchSupport.framework/Versions/A/MultitouchSupport
0x93750000 - 0x93757fff com.apple.agl (3.2.0 - AGL-3.2.0) /System/Library/Frameworks/AGL.framework/Versions/A/AGL
0x9375c000 - 0x937f3ff3 com.apple.securityfoundation (5.0 - 55116) /System/Library/Frameworks/SecurityFoundation.framework/Versions/A/SecurityFoundation
0x937f4000 - 0x938b7fff com.apple.CoreServices.OSServices (478.49 - 478.49) <5AF33605-C893-3F60-89CF-1BC9C0BC35AF> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServices.framework/Versions/A/OSServices
0x938e0000 - 0x938e8ff3 liblaunch.dylib (392.39.0 - compatibility 1.0.0) <9E6135FF-C2B1-3BC9-A160-B32D71BFA77C> /usr/lib/system/liblaunch.dylib
0x9396a000 - 0x939a7ff7 libcups.2.dylib (2.9.0 - compatibility 2.0.0) <007A1877-E981-3007-A8FA-9B179F4ED6D1> /usr/lib/libcups.2.dylib
0x939a8000 - 0x93e84ff6 libBLAS.dylib (? - ?) <134ABFC6-F29E-3DC5-8E57-E13CB6EF7B41> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBLAS.dylib
0x93e85000 - 0x93ea8fff com.apple.CoreVideo (1.7 - 70.3) <4234C11C-E8E9-309A-9465-27D6D7458895> /System/Library/Frameworks/CoreVideo.framework/Versions/A/CoreVideo
0x947c3000 - 0x947c3fff com.apple.vecLib (3.7 - vecLib 3.7) <8CCF99BF-A4B7-3C01-9219-B83D2AE5F82A> /System/Library/Frameworks/vecLib.framework/Versions/A/vecLib
0x947c4000 - 0x947f3ff7 libsystem_info.dylib (? - ?) <37640811-445B-3BB7-9934-A7C99848250D> /usr/lib/system/libsystem_info.dylib
0x947f4000 - 0x949cbfe7 com.apple.CoreFoundation (6.7.2 - 635.21) <4D1D2BAF-1332-32DF-A81B-7E79D4F0A6CB> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
0x949cc000 - 0x94a0afff libRIP.A.dylib (600.0.0 - compatibility 64.0.0) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/CoreGraphics.framework/Versions/A/Resources/libRIP.A.dylib
0x94a1b000 - 0x94a2bfff com.apple.LangAnalysis (1.7.0 - 1.7.0) <6D6F0C9D-2EEA-3578-AF3D-E2A09BCECAF3> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/LangAnalysis.framework/Versions/A/LangAnalysis
0x94a2c000 - 0x94a39fff libGL.dylib (? - ?) /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib
0x94aa5000 - 0x94b62ff3 ColorSyncDeprecated.dylib (4.6.0 - compatibility 1.0.0) <726898F5-E718-3F27-B415-D6FDCDE09174> /System/Library/Frameworks/ApplicationServices.framework/Frameworks/ColorSync.framework/Versions/A/Resources/ColorSyncDeprecated.dylib
0x94b63000 - 0x94bb3ffa libTIFF.dylib (? - ?) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/libTIFF.dylib
0x94bb4000 - 0x94c50fff com.apple.ink.framework (10.7.5 - 113) <05CAFB64-D3B8-3973-87EA-CB8BBE580F6B> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Ink.framework/Versions/A/Ink
0x9500d000 - 0x9500efff libsystem_blocks.dylib (53.0.0 - compatibility 1.0.0) /usr/lib/system/libsystem_blocks.dylib
0x95384000 - 0x953cdff7 libGLU.dylib (? - ?) <9AF7AD51-16E3-3674-B60E-30EE499D7B46> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLU.dylib
0x953ce000 - 0x954beff1 libiconv.2.dylib (7.0.0 - compatibility 7.0.0) <9E5F86A3-8405-3774-9E0C-3A074273C96D> /usr/lib/libiconv.2.dylib
0x95519000 - 0x95533fff com.apple.Kerberos (1.0 - 1) /System/Library/Frameworks/Kerberos.framework/Versions/A/Kerberos
0x95534000 - 0x95544ff7 libCRFSuite.dylib (? - ?) <94E040D2-2769-359A-A21B-DB85FCB73BDC> /usr/lib/libCRFSuite.dylib
0x95545000 - 0x955b9fff com.apple.CoreSymbolication (2.2 - 73.2) /System/Library/PrivateFrameworks/CoreSymbolication.framework/Versions/A/CoreSymbolication
0x955e8000 - 0x955e8fff com.apple.Carbon (153 - 153) <13CB5B39-BBDB-397B-A4F2-69773047D092> /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon
0x955f4000 - 0x95646ff7 libFontRegistry.dylib (? - ?) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libFontRegistry.dylib
0x9564d000 - 0x95723aab libobjc.A.dylib (228.0.0 - compatibility 1.0.0) <2E272DCA-38A0-3530-BBF4-47AE678D20D4> /usr/lib/libobjc.A.dylib
0x95757000 - 0x9576bfff com.apple.CFOpenDirectory (10.7 - 146) <982C417B-5A0F-3DD6-AB50-7E8273A80B38> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/Frameworks/CFOpenDirectory.framework/Versions/A/CFOpenDirectory
0x95ade000 - 0x95b1eff7 libauto.dylib (? - ?) <984C81BE-FA1C-3228-8F7E-2965E7E5EB85> /usr/lib/libauto.dylib
0x95b1f000 - 0x95b3cfff libresolv.9.dylib (46.1.0 - compatibility 1.0.0) <2870320A-28DA-3B44-9D82-D56E0036F6BB> /usr/lib/libresolv.9.dylib
0x95b3d000 - 0x95c4eff7 libJP2.dylib (? - ?) <2B5EB147-F845-30DF-87C4-D2D3C3D0680A> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/libJP2.dylib
0x95cdb000 - 0x95ce6ffb com.apple.speech.recognition.framework (4.0.21 - 4.0.21) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SpeechRecognition.framework/Versions/A/SpeechRecognition
0x95ce7000 - 0x95d07ff7 com.apple.RemoteViewServices (1.5 - 44.2) <11C87337-FF29-3976-A230-6387D96563C5> /System/Library/PrivateFrameworks/RemoteViewServices.framework/Versions/A/RemoteViewServices
0x95d08000 - 0x95df0fff libxml2.2.dylib (10.3.0 - compatibility 10.0.0) <1841196F-68B5-309F-8ED1-6714B1DFEC83> /usr/lib/libxml2.2.dylib
0x95e60000 - 0x961a6ff3 com.apple.HIToolbox (1.9 - ?) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/HIToolbox
0x961a7000 - 0x961f8ff9 com.apple.ScalableUserInterface (1.0 - 1) <3C39DF4D-5CAE-373A-BE08-8CD16E514337> /System/Library/Frameworks/QuartzCore.framework/Versions/A/Frameworks/ScalableUserInterface.framework/Versions/A/ScalableUserInterface
0x961f9000 - 0x96240ff5 com.apple.opencl (2.0.19 - 2.0.19) <7689E7B9-EE5A-3F74-8699-4CDED9162260> /System/Library/Frameworks/OpenCL.framework/Versions/A/OpenCL
0x963d7000 - 0x963e2ff3 libCSync.A.dylib (600.0.0 - compatibility 64.0.0) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/CoreGraphics.framework/Versions/A/Resources/libCSync.A.dylib
0x963e3000 - 0x963eefff libkxld.dylib (? - ?) <14E79D7A-B6C2-35C5-B56D-D343BEC2A106> /usr/lib/system/libkxld.dylib
0x963f0000 - 0x9640eff7 libsystem_kernel.dylib (1699.32.7 - compatibility 1.0.0) <79179F83-457A-3539-A76B-E960D2108109> /usr/lib/system/libsystem_kernel.dylib
0x9641c000 - 0x9641fffc libpam.2.dylib (3.0.0 - compatibility 3.0.0) <6FFDBD60-5EC6-3EFA-996B-EE030443C16C> /usr/lib/libpam.2.dylib
0x96420000 - 0x96454ff8 libssl.0.9.8.dylib (44.0.0 - compatibility 0.9.8) <567E922C-E64F-321B-9A47-6B18BF481625> /usr/lib/libssl.0.9.8.dylib
0x96455000 - 0x96573fec com.apple.vImage (5.1 - 5.1) <7757F253-B281-3612-89D4-F2B04061CBE1> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/vImage
0x96577000 - 0x9657fff5 libcopyfile.dylib (85.1.0 - compatibility 1.0.0) /usr/lib/system/libcopyfile.dylib
0x96975000 - 0x96c44ffb com.apple.security (7.0 - 55148.6) <8DF67BDD-C98F-3B7E-AC63-D468407FA82D> /System/Library/Frameworks/Security.framework/Versions/A/Security
0x96c45000 - 0x96cb4fff com.apple.Heimdal (2.2 - 2.0) <2E1B8779-36D4-3C62-A67E-0034D77D7707> /System/Library/PrivateFrameworks/Heimdal.framework/Versions/A/Heimdal
0x96cb5000 - 0x96cb5ff0 com.apple.ApplicationServices (41 - 41) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices
0x96cb6000 - 0x96cb7ff7 libsystem_sandbox.dylib (? - ?) <5CFCCFB7-CF29-3E04-801D-8532AE004768> /usr/lib/system/libsystem_sandbox.dylib
0x96cc3000 - 0x97138ff7 FaceCoreLight (1.4.7 - compatibility 1.0.0) <3E2BF587-5168-3FC5-9D8D-183A9C7C1DED> /System/Library/PrivateFrameworks/FaceCoreLight.framework/Versions/A/FaceCoreLight
0x97139000 - 0x97181ff7 com.apple.SystemConfiguration (1.11.3 - 1.11) <68B92FEA-F754-3E7E-B5E6-D512E26144E7> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfiguration
0x97555000 - 0x97556ff0 libunc.dylib (24.0.0 - compatibility 1.0.0) <2F4B35B2-706C-3383-AA86-DABA409FAE45> /usr/lib/system/libunc.dylib
0x977b1000 - 0x977b7ffb com.apple.print.framework.Print (7.4 - 247.3) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Print.framework/Versions/A/Print
0x97bed000 - 0x97da1ff3 libicucore.A.dylib (46.1.0 - compatibility 1.0.0) <4AFF6FC3-6283-3934-8EFC-CA227CA11164> /usr/lib/libicucore.A.dylib
0x97da2000 - 0x97f04ffb com.apple.QuartzCore (1.7 - 270.5) <6D0EC7FC-11E5-35FB-A08A-3B438E89FBDB> /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore
0x97f05000 - 0x98004ffb com.apple.DiskImagesFramework (10.7.4 - 331.7) <31A74A7E-E2AE-313D-A7C4-6DFCF0F22C9A> /System/Library/PrivateFrameworks/DiskImages.framework/Versions/A/DiskImages
0x98005000 - 0x980c5ffb com.apple.ColorSync (4.7.4 - 4.7.4) <0A68AF35-15DF-3A0A-9B17-70CE2A106A6C> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ColorSync.framework/Versions/A/ColorSync
0x980ce000 - 0x980d3ff7 libmacho.dylib (800.0.0 - compatibility 1.0.0) <943213F3-CC9B-328E-8A6F-16D85C4274C7> /usr/lib/system/libmacho.dylib
0x980d4000 - 0x980d7ffd libCoreVMClient.dylib (? - ?) /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreVMClient.dylib
0x98151000 - 0x98151fff libOpenScriptingUtil.dylib (? - ?) /usr/lib/libOpenScriptingUtil.dylib
0x981a5000 - 0x98275ffb com.apple.ImageIO.framework (3.1.2 - 3.1.2) <2092785C-795A-3CDF-A1B4-6C80BA3726DD> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/ImageIO
0x98276000 - 0x982a4fe7 libSystem.B.dylib (159.1.0 - compatibility 1.0.0) <0D8984D3-BFCF-35A7-AA71-BEDC92126B7E> /usr/lib/libSystem.B.dylib
0x982c8000 - 0x982c8fff libdnsinfo.dylib (395.11.0 - compatibility 1.0.0) <7EFAD88C-AFBC-3D48-BE14-60B8EACC68D7> /usr/lib/system/libdnsinfo.dylib
0x982c9000 - 0x982f1ff7 libxslt.1.dylib (3.24.0 - compatibility 3.0.0) /usr/lib/libxslt.1.dylib
0x983ea000 - 0x98460fff com.apple.Metadata (10.7.0 - 627.37) /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadata.framework/Versions/A/Metadata
0x992ae000 - 0x992b4fff libGFXShared.dylib (? - ?) <9C9834EB-B794-38C8-9B90-31D8CB234F86> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGFXShared.dylib
0x992b5000 - 0x992d7ff8 com.apple.PerformanceAnalysis (1.11 - 11) <453463FF-7C42-3526-8C96-A9971EE07154> /System/Library/PrivateFrameworks/PerformanceAnalysis.framework/Versions/A/PerformanceAnalysis
0x992d8000 - 0x992d8ff2 com.apple.CoreServices (53 - 53) <7CB7AA95-D5A7-366A-BB8A-035AA9E582F8> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
0x992d9000 - 0x9930fff4 com.apple.LDAPFramework (3.2 - 120.2) /System/Library/Frameworks/LDAP.framework/Versions/A/LDAP
0x99310000 - 0x9931efff com.apple.opengl (1.8.1 - 1.8.1) <766AFB12-A2CB-3A55-B662-FC9FFCAE0008> /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL
0x9931f000 - 0x99378fff com.apple.HIServices (1.21 - ?) <91EC636D-AC27-3332-BA1C-FD7301917429> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/HIServices.framework/Versions/A/HIServices
0x993ae000 - 0x993afff4 libremovefile.dylib (21.1.0 - compatibility 1.0.0) <6DE3FDC7-0BE0-3791-B6F5-C15422A8AFB8> /usr/lib/system/libremovefile.dylib
0x993b0000 - 0x993b0fff com.apple.Accelerate (1.7 - Accelerate 1.7) <4192CE7A-BCE0-3D3C-AAF7-6F1B3C607386> /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate
0x993b1000 - 0x993bffff libdispatch.dylib (187.10.0 - compatibility 1.0.0) <1B857064-288D-3919-B81A-38E9F4D19B54> /usr/lib/system/libdispatch.dylib
0x993cb000 - 0x9942dffb com.apple.datadetectorscore (3.0 - 179.4) <3A418498-C189-37A1-9B86-F0ECB33AD91C> /System/Library/PrivateFrameworks/DataDetectorsCore.framework/Versions/A/DataDetectorsCore
0x9942e000 - 0x99453ff9 libJPEG.dylib (? - ?) <743578F6-8C0C-39CC-9F15-3A01E1616EAE> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/libJPEG.dylib
0x995bc000 - 0x995beff7 libdyld.dylib (195.6.0 - compatibility 1.0.0) <1F865C73-5803-3B08-988C-65B8D86CB7BE> /usr/lib/system/libdyld.dylib
0x99664000 - 0x99745ff7 com.apple.DiscRecording (6.0.4 - 6040.4.1) <08BADDAD-FA79-3872-9387-EEE2A9FAA2F0> /System/Library/Frameworks/DiscRecording.framework/Versions/A/DiscRecording
0x99746000 - 0x99855ff7 com.apple.DesktopServices (1.6.5 - 1.6.5) /System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/DesktopServicesPriv
0x998d6000 - 0x998daffd IOSurface (? - ?) /System/Library/Frameworks/IOSurface.framework/Versions/A/IOSurface
0x998db000 - 0x9993cffb com.apple.audio.CoreAudio (4.0.3 - 4.0.3) <7A14BE52-6789-3CE3-9AE9-B733F4903EB1> /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio
0x9993d000 - 0x99d3fff6 libLAPACK.dylib (? - ?) <00BE0221-8564-3F87-9F6B-8A910CF2F141> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLAPACK.dylib
0x99d43000 - 0x99dbeffb com.apple.ApplicationServices.ATS (317.12.0 - ?) <4D124B65-3D43-32E9-B296-3671347BB888> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/ATS
0x9a1fd000 - 0x9a234fef com.apple.DebugSymbols (2.1 - 87) /System/Library/PrivateFrameworks/DebugSymbols.framework/Versions/A/DebugSymbols
0x9a274000 - 0x9a275ffd libCVMSPluginSupport.dylib (? - ?) <4B0476F9-950D-3EB7-BD83-F65AF0B05F0E> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCVMSPluginSupport.dylib
0x9a276000 - 0x9a36eff7 libFontParser.dylib (? - ?) <71B33EB1-27F8-3C68-B940-FC61A3CFE275> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libFontParser.dylib
0x9ada1000 - 0x9adacffe libbz2.1.0.dylib (1.0.5 - compatibility 1.0.0) <13FF02F8-7AF6-3E12-B183-9A725B526B50> /usr/lib/libbz2.1.0.dylib
0x9adad000 - 0x9adadfff com.apple.Accelerate.vecLib (3.7 - vecLib 3.7) <22997C20-BEB7-301D-86C5-5BFB3B06D212> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/vecLib
0x9adae000 - 0x9b022ff3 com.apple.CoreImage (7.99.1 - 1.0.1) /System/Library/Frameworks/QuartzCore.framework/Versions/A/Frameworks/CoreImage.framework/Versions/A/CoreImage
0x9b02e000 - 0x9b06eff7 com.apple.NavigationServices (3.7 - 193) <16A8BCC8-7343-3A90-88B3-AAA334DF615F> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/NavigationServices.framework/Versions/A/NavigationServices
0x9b06f000 - 0x9b070fff libDiagnosticMessagesClient.dylib (? - ?) /usr/lib/libDiagnosticMessagesClient.dylib
0x9b071000 - 0x9b071ffe libkeymgr.dylib (23.0.0 - compatibility 1.0.0) <7F0E8EE2-9E8F-366F-9988-E2F119DB9A82> /usr/lib/system/libkeymgr.dylib
0x9b072000 - 0x9b0ffff7 com.apple.CoreText (220.22.0 - ?) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/CoreText.framework/Versions/A/CoreText
0x9b100000 - 0x9b116ffe libxpc.dylib (77.19.0 - compatibility 1.0.0) <0585AA94-F4FD-32C1-B586-22E7184B781A> /usr/lib/system/libxpc.dylib
0x9b117000 - 0x9b11fff3 libunwind.dylib (30.0.0 - compatibility 1.0.0) /usr/lib/system/libunwind.dylib
0x9b120000 - 0x9b13cff1 libPng.dylib (? - ?) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/libPng.dylib
0x9b1c1000 - 0x9b1cffff libz.1.dylib (1.2.5 - compatibility 1.0.0) /usr/lib/libz.1.dylib
0x9b1d0000 - 0x9b1d3ff7 libmathCommon.A.dylib (2026.0.0 - compatibility 1.0.0) <69357047-7BE0-3360-A36D-000F55E39336> /usr/lib/system/libmathCommon.A.dylib
0x9b248000 - 0x9b24bffb com.apple.help (1.3.2 - 42) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Help.framework/Versions/A/Help
0x9b24c000 - 0x9b32fff7 libcrypto.0.9.8.dylib (44.0.0 - compatibility 0.9.8) /usr/lib/libcrypto.0.9.8.dylib
0x9b330000 - 0x9b38eff7 com.apple.coreui (1.2.2 - 165.11) <340B0B83-1407-3AB4-BCAB-505C29303EE2> /System/Library/PrivateFrameworks/CoreUI.framework/Versions/A/CoreUI
0x9b38f000 - 0x9b425ff7 com.apple.LaunchServices (480.40 - 480.40) /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/LaunchServices
0x9b426000 - 0x9b42aff7 com.apple.OpenDirectory (10.7 - 146) /System/Library/Frameworks/OpenDirectory.framework/Versions/A/OpenDirectory
0x9b47f000 - 0x9b5abff9 com.apple.CFNetwork (520.5.1 - 520.5.1) /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CFNetwork.framework/Versions/A/CFNetwork
0x9b5ac000 - 0x9b5b0ff3 libsystem_network.dylib (? - ?) <62EBADDA-FC72-3275-AAB3-5EDD949FEFAF> /usr/lib/system/libsystem_network.dylib
0x9b5b1000 - 0x9b5bbff2 com.apple.audio.SoundManager (3.9.4.1 - 3.9.4.1) <2A089CE8-9760-3F0F-B77D-29A78940EA17> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CarbonSound.framework/Versions/A/CarbonSound
0x9b5f0000 - 0x9b61bfff com.apple.GSS (2.2 - 2.0) <2C468B23-FA87-30B5-B9A6-8C5D1373AA30> /System/Library/Frameworks/GSS.framework/Versions/A/GSS
0x9b61c000 - 0x9b61eff9 com.apple.securityhi (4.0 - 1) <8196A6AC-4F97-3DCB-8F09-AE8D983823DF> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SecurityHI.framework/Versions/A/SecurityHI
0x9b662000 - 0x9b6a3ff9 libcurl.4.dylib (7.0.0 - compatibility 7.0.0) <9FD420FB-7984-3A07-8914-BB19E687D38B> /usr/lib/libcurl.4.dylib
0x9b6a4000 - 0x9b6e7ffd libcommonCrypto.dylib (55010.0.0 - compatibility 1.0.0) <6B35F203-5D72-335A-A4BC-CC89FEC0E14F> /usr/lib/system/libcommonCrypto.dylib
0x9b8a8000 - 0x9b8a8fff com.apple.audio.units.AudioUnit (1.7.3 - 1.7.3) <2E71E880-25D1-3210-8D26-21EC47ED810C> /System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit
0x9b8a9000 - 0x9c33eff6 com.apple.AppKit (6.7.5 - 1138.51) /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
0x9c33f000 - 0x9c354fff com.apple.speech.synthesis.framework (4.0.74 - 4.0.74) <92AADDB0-BADF-3B00-8941-B8390EDC931B> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/SpeechSynthesis.framework/Versions/A/SpeechSynthesis
0x9c3df000 - 0x9c3e0fff liblangid.dylib (? - ?) /usr/lib/liblangid.dylib
0x9c606000 - 0x9cf3172b com.apple.CoreGraphics (1.600.0 - ???) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/CoreGraphics.framework/Versions/A/CoreGraphics

External Modification Summary:
Calls made by other processes targeting this process:
task_for_pid: 4
thread_create: 0
thread_set_state: 0
Calls made by this process:
task_for_pid: 0
thread_create: 0
thread_set_state: 0
Calls made by all processes on this machine:
task_for_pid: 6612
thread_create: 0
thread_set_state: 0

VM Region Summary:
ReadOnly portion of Libraries: Total=189.0M resident=99.1M(52%) swapped_out_or_unallocated=89.9M(48%)
Writable regions: Total=142.6M written=12.2M(9%) resident=23.9M(17%) swapped_out=68K(0%) unallocated=118.6M(83%)

REGION TYPE VIRTUAL =========== =======
(null) (reserved) 4160K reserved VM address space (unallocated)
ATS (font support) 31.8M
ATS (font support) (reserved) 4K reserved VM address space (unallocated)
CG backing stores 5624K
CG image 8K
CG raster data 120K
CG shared images 3448K
CoreGraphics 8K
CoreServices 980K
IOKit 172K
JS garbage collector 256K
MALLOC 68.3M
MALLOC guard page 64K
Memory tag=240 4K
Memory tag=242 12K
Stack 67.6M
VM_ALLOCATE 17.4M
_CI_BITMAP 80K
_DATA 11.7M
_DATA/_OBJC 68K
_IMAGE 528K
_IMPORT 224K
_LINKEDIT 50.8M
_OBJC 1480K
_PAGEZERO 4K
_TEXT 138.2M
__UNICODE 544K
mapped file 158.5M
shared memory 1996K
shared pmap 10.3M =========== =======
TOTAL 573.9M
TOTAL, minus reserved VM space 569.8M

Model: MacBookAir4,2, BootROM MBA41.0077.B0F, 2 processors, Intel Core i5, 1.7 GHz, 4 GB, SMC 1.73f63
Graphics: Intel HD Graphics 3000, Intel HD Graphics 3000, Built-In, 384 MB
Memory Module: BANK 0/DIMM0, 2 GB, DDR3, 1333 MHz, 0x80AD, 0x484D54333235533642465238432D48392020
Memory Module: BANK 1/DIMM0, 2 GB, DDR3, 1333 MHz, 0x80AD, 0x484D54333235533642465238432D48392020
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0xE9), Broadcom BCM43xx 1.0 (5.106.198.19.22)
Bluetooth: Version 4.0.8f17, 2 service, 18 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en0
Serial ATA Device: APPLE SSD SM128C, 121.33 GB
USB Device: FaceTime Camera (Built-in), apple_vendor_id, 0x850a, 0xfa200000 / 3
USB Device: hub_device, 0x0424 (SMSC), 0x2513, 0xfa100000 / 2
USB Device: USB-Serial Controller, 0x067b (Prolific Technology, Inc.), 0x2303, 0xfa130000 / 6
USB Device: BRCM20702 Hub, 0x0a5c (Broadcom Corp.), 0x4500, 0xfa110000 / 5
USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x821f, 0xfa113000 / 7
USB Device: Apple Internal Keyboard / Trackpad, apple_vendor_id, 0x024c, 0xfa120000 / 4
USB Device: hub_device, 0x0424 (SMSC), 0x2513, 0xfd100000 / 2
USB Device: Internal Memory Card Reader, apple_vendor_id, 0x8404, 0xfd110000 / 3

2012_10_14_05_02_55.srm (289.6 kB) Elliot Hawkes, 10/21/2012 06:27 pm
2012_10_14_05_02_55-fixed.srm (289.6 kB) Rainer Clasen, 10/22/2012 12:37 am
Add
Related issues

History
#1 Updated by Rainer Clasen 17 days ago

File 2012_10_14_05_02_55-fixed.srm added
Status changed from New to Assigned
Assignee set to Rainer Clasen
Target version set to 3.0
% Done changed from 0 to 50

Hi,

the provided file has bad indices in the lap/marker record. GC isn't checking the start index and therefore causes this crash.

I have a patch for proper bounds checking pending, but need to test it, first.

I think the bad marker indices originate from the PCV memory and the download code just copies them over... but I need to verify that, aswell.

In the meantime I'm attaching a fixed version of the file

Import ride does a check for duplicates but including the file extension. So if you import ride.tcx and ride.tcx already exists it works fine. If, however, the ride has been changed and saved (ride.gc or ride.json) the check fails and you end up with two rides with the same date/time.

Import should therefore check regardless of the extension. As a safety-net the addRide function should also check and throw an error dialog (which should never happen if the import wizard is fixed, but will catch any errant code elsewhere).

Associated revisions

Revision e55ed50
Added by Mark Liversedge about 1 year ago

Check Duplicates when importing rides

When importing a ridefile we have never checked that the
same ride (date/time) does not already exist but in a
different ridefile format.

For example, importing a TCX file when a .RAW file already
exists for the same date/time causes conflicts with the
.cpx and .notes file (it is not possible to distinguish
which ridefile the notes/cpx file belong to).

Fixes #389.

History
#1 Updated by Mark Liversedge about 1 year ago

Target version changed from 2.1 to 3.0
Set target to 3.0, see list for explanation (leave be in 2.1, fix in 3.0, move to native in 3.1). We can cherry pick this back to 2.1 if the general consensus suggests it should be there.
#2 Updated by Mark Liversedge about 1 year ago

Status changed from New to Closed
% Done changed from 0 to 100
Applied in changeset e55ed50.

An empty filename is generated, which causes ride name collisions and an assertion failure in debug mode (this issue only exists in release_3.0.0dev):

src/PowerTapDevice.cpp:
@@ -316,7 +316,7 @@ PowerTapDevice::download( const QDir &tmpdir,
if (!time_set && PowerTapUtil::is_time(data + i, bIsVer81)) {
struct tm time;
time_t timet = PowerTapUtil::unpack_time(data + i, &time, bIsVer81);

•        file.startTime.fromTime_t( timet ); // fromTime_t is a static method call that doesn't populate file.startTime
  

•        file.startTime.setTime_t( timet );
       time_set = true;
   }
  

  }

0001-PowerTapDevice-fix-date-initialisation.patch - actual fix (1 kB) Rainer Clasen, 28/07/2011 05:05 pm
0002-DownloadDialog-handle-unset-invalid-timestamps.patch - better handling in download dialog inspired by bug (1.2 kB) Rainer Clasen, 28/07/2011 05:05 pm
Associated revisions

Revision 851f989
Added by Rainer Clasen over 1 year ago

PowerTapDevice: fix date initialisation

startDate for the rideList returned after download wasn't set properly.
Use proper method instead of static fabric funcition.

Thanks to Eric Yoo for finding and fixing this.

fixes #365

History
#1 Updated by Rainer Clasen over 1 year ago

Status changed from New to Assigned
Assignee set to Rainer Clasen
Target version set to 3.0
% Done changed from 0 to 50
Hi Eric,

thanks for reporting this and providing a patch.

Just checked, and fortunatly I didn't do the same mistake for the other Devices (Macro, Srm, ...).

Rainer
#2 Updated by Rainer Clasen over 1 year ago

File 0001-PowerTapDevice-fix-date-initialisation.patch added
File 0002-DownloadDialog-handle-unset-invalid-timestamps.patch added
Status changed from Assigned to Resolved
% Done changed from 50 to 100
Patch Attached changed from No to Yes
Please find attached Eric's patch incl. commit message.

I've also added another patch that makes the download dialog fall back to the current time. So it doesn't crash and we keep the downloaded data so user can take care of this (if he wants to).

In case you prefer pull, it's also on github together with the srmio d2xx changes.
[email protected]:rclasen/GoldenCheetah.git pc7
#3 Updated by Rainer Clasen over 1 year ago

Status changed from Resolved to Closed
Applied in changeset 851f989.

Need to fix the way date ranges are managed in LTM and LTMtool. they are a mess!

When clicking on a ride in the monthly (calendar) view in the diary does not always select it. On Mac builds it NEVER selects the ride, on Linux builds it SOMETIMES does not select the ride.

Associated revisions

Revision da8e22a
Added by Mark Liversedge over 1 year ago

Fix Diary doesn't select ride on Mac

The metricDB columns are renamed to more friendly values
in RideNavigator, and the GcCalendarModel was looking for
a columns "Filename" when it was named "File".

This mean't the call to the model to retrieve the filename
when an entry was clicked on the table view (diary) would
return "".

Strangely, this worked fine on Linux. But it is definitely
a bug. This patch fixes that.

Fixes #330.

History
#1 Updated by Mark Liversedge over 1 year ago

Priority changed from Normal to High
Made high since it is a core function of the calendar view.
#2 Updated by Mark Liversedge over 1 year ago

Status changed from New to Closed
% Done changed from 0 to 100
Applied in changeset da8e22a.

When GC is first installed by the user it would be nice to have a wizard walk them through initial setup of cyclist details and import any ridefiles etc before they start. It would certainly avoid issues related to metrics being zero because Zones are not set up. It would also make GC a little less daunting upon first execution....

Add
Related issues

History
#1 Updated by Mark Liversedge over 1 year ago

Additionally, since the most common issue new users have is about zones and blank metrics etc we should also add
sanity check on startup to insist on defaul lthr/cp
new cyclist dialog to force entry of lthr/cp and also allow user to set other optional data such as age, sex, weight, avatar etc
#2 Updated by Mark Liversedge over 1 year ago

Assignee set to Mark Liversedge
Target version set to 3.0
% Done changed from 0 to 50

New cyclist dialog has been updated now. This feature now set to 50% complete

Adding any chart to an existing home layout with Windows 7 is causing GC 3.0 to crash. There is no issues performing the same action with XP64.

Jason

2011-06-04__22_22_07.avi (2.5 MB) Mark Liversedge, 31/07/2011 06:58 pm
Associated revisions

Revision 14c1d77
Added by Mark Liversedge about 1 year ago

Remove drop shadows

They're dog slow and looking through the QT bug
tracker no longer developed or supported on normal
QT widgets without QT Quick.

They also break drag and drop on Win7 64bit.

Fixes #324.

History
#1 Updated by Mark Liversedge over 1 year ago

Status changed from New to Feedback
Thanks for the bug report -- I was wondering if anyone was using this stuff!

When starting GC on Win 7 do you see any charts on the home window?

Did you use the same home-layout.xml file on Win7 as well as XP ?

Does it do the same for all charts?

Did you have a LTM chart in there?

Did you have write permissions on home-layout.xml ?

Are you using your own build or Gareth's?

Finally, if you delete the home-layout.xml file and start GC does it work ok?

Thanks,
Mark
#2 Updated by Mark Liversedge over 1 year ago

Status changed from Feedback to Assigned
Assignee set to Mark Liversedge
Priority changed from Normal to High
Target version set to 3.0
Estimated time set to 3.00
Qt Version set to 4.7.0
Jason's reply:

I sure am. It makes scrolling back through your rides to gauge fitness and
progress much easier and more visual.
Yes, I see the charts I setup in XP64.
Yes, I started the home xml file on my XP64 laptop and then copied all the
files to my Windows 7 machine.
I didn't try every last chart, but for sure adding a summary or a summary with
notes causes the crash. I also tried a few others at random which also causes
the crash.
LTM Chart?
Yes, I have write permissions on the file and folder.
I'm using the 3.0 build from the website without any additions.
Deleting the home xml file and trying to add a chart results in the crash.

Mark's comments:

I think the critical point is on the last item then. Bummer. In short, when adding a chart on Win7 x64 it crashes.

I did have a memory management issue during the development of this feature which was related to 'taking the parent' of a widget when moving it from the dialog box to the layout page. Maybe this is related?

Will investigate.
#3 Updated by Mark Liversedge over 1 year ago

File 2011-06-04__22_22_07.avi added
Estimated time changed from 3.00 to 16.00
Attaching Rob Massa's video from #339 which was a duplicate of this bug report.
#4 Updated by Mark Liversedge over 1 year ago

Latest build from stand2surf.net (8th August) still exhibits this problem on Windows;

• Win7 32 bit - Drag and drop, edit details click ok then CRASH
• Win7 64 bit - Drag .. release button to drop and CRASH

I note that with static builds we do not get any crashes. Still trying to hunt down this bug.
#5 Updated by Mark Liversedge over 1 year ago

Status changed from Assigned to Feedback
% Done changed from 0 to 70
The drag and drop functions have been adjusted in commit 78bb7e to fix for win 7. Win7 64bit still remains an issue, but this seems to be related to eanbling drop shadows in appearances on a tiled view.

To avoid the bug on Win7 64;

1. drag and drop in tabbed mode
2. drag and drop in tiled mode without drop shadows

I have moved this bug to feedback to get answers for the above from other users -- if it is drop shadows we will just remove them altogether.
#6 Updated by Mark Liversedge about 1 year ago

Status changed from Feedback to Closed
% Done changed from 70 to 100
Did further testing and drop shadows are the culprit. Pushed commit 14c1d7 to fix this for good.

It would be beneficial in the New Athlete dialog to be able to select the units (Metric or Imperial) that the user would like to use and have the input dialog then use the units selected.

When a metric chart is added to a layout the controls do not work until GC is restarted. This may be related to the crash on Windows 7 when adding a chart, but added as a separate issue since it manifests itself on Linux (and possibly Mac).

History
#1 Updated by Mark Liversedge over 1 year ago

Status changed from New to Closed
This was fixed in commit 5bd102b.

It bugs the hell out of me. The x-axis should show the sample time in a time format rather than minutes and fractions of a minute. The same applies to the tooltip.

Lets fix it.

Lat and Lon are not decoded corectly on 64bit builds - they are decoded via a signed long which is 64 bits rather than the 32 bits that seem to be assumed in the code.

Associated revisions

Revision 5e89f99
Added by Mark Liversedge over 1 year ago

Fix 64bit WKO parsing GPS data

The decoding of GPS data erroneously assumed that a
signed long was 32 bits, which is not true on a 64bit
platform.

Fixes #333.

History
#1 Updated by Mark Liversedge over 1 year ago

Status changed from New to Closed
% Done changed from 10 to 100
Applied in changeset 5e89f99.

Two ride files that cause problems;

1. The first (json) causes GC to crash on Windows, it was imported as a WKO file and has recording interval set to 5s when its really 1s. It causes an out of bounds crash in RideFileCache when computing mean-max for >6m).
2. The second (tcx) causes the CP plot to have huge values for power (14000+) for short intervals.

2009_02_14_13_53_00.json (143.6 kB) Mark Liversedge, 25/04/2011 06:44 am
2010_08_27_16_41_41.tcx.gz (134 kB) Mark Liversedge, 25/04/2011 06:44 am
Associated revisions

Revision 659d354
Added by Mark Liversedge over 1 year ago

Fix CP calculation crash

Fixes SEGV in RideFileCache caused by incorrect recIntSecs setting
for a ridefile. Other reported issues with high power values for
short intervals was data related and not a bug.

Fixes #314.

History
#1 Updated by Mark Liversedge over 1 year ago

Status changed from New to Closed
% Done changed from 10 to 100
Applied in changeset 659d354.

When importing a file, the file import dialog box loses focus and ends up behind the main GC screen. If you import a couple of files you end up with a bunch of import diaglog boxes behind GC and they even stay there after you close GC. The work around is to minimize GC and close the dialog boxes then restore the GC window again.

Shouldn't there be just one dialog box as opposed to one box for every time you drop a file onto GC?

If you close GC these dialog boxes stay open, I would think they should close also or there should be a warning that other GC windows are open.

Associated revisions

Revision 1929733
Added by Mark Liversedge over 1 year ago

Fix Configure Pane 'on top' obscuring other windows

Notably when you select a color in the config appearances
the dialog will have modal focus but be hidden behind the
config pane, this is tedious as hell.

I have now checked across the codebase and there are no
dialogs which insist on being on top so the OS window
manager and user is now free to manage windows as they
see fit.

Although not directly related this fixes the only possible
problems with window focus that could be related to another
bug reported by Fernando.

Fixes #117.

History
#1 Updated by Robert Carlsen over 2 years ago

Status changed from New to Feedback
Could you describe a bit more about your scenario?
You can import multiple rides at once, either by dragging the ride files onto Golden Cheetah, or by selecting multiple files in the file selection dialog.

The file import dialog will list all files it's currently trying to import in one window.

However, I did notice that focusing Golden Cheetah's main window, then selecting "Import from file..." while another import dialog is already visible will spawn multiple file selection dialogs, then multiple file import dialog windows.
#2 Updated by Mark Liversedge over 1 year ago

Assignee set to Mark Liversedge
Priority changed from Normal to High
Target version set to 3.0
Patch Attached set to No
We need to fix this, it drives me mad!
#3 Updated by Mark Liversedge over 1 year ago

Status changed from Feedback to Closed
% Done changed from 0 to 100
Applied in changeset 1929733.

Currently the data entered in the activity notes has priority over the data entered in the sport and workout code for colouring the calendar and the activity. This can give inconsistent colouring. As an example; I enter Sport: "Bike", Workout: "E2. Extensive Endurance", Notes: "bike ride around Embrun". This will automatically catch the run letter from the Embrun word and colour the activity as if it where a run, instead of a bike activity (I am assuming I have assigned different colours to bike and run activities).

I believe the priority should be changed to:

1.Sport
2.Workout
3.Notes

Add
Related issues

History
#1 Updated by Mark Liversedge 11 months ago

I would prefer we specify the fields to use for keyword coloring and add as a configurable item.
#2 Updated by Arturo Mac Dowell 11 months ago

That sounds good to me. I proposed it in another way because I thought it would be easier to code. What you are proposing is far better.

Update Watch Copy Delete

Hi,

Currently, Golden Cheetah is proposing a shade for the power data using the power zones defined by the user.
It could be great also to propose the same tool for heart rate data. I think that this tool could be proposed as a combo box where the shade can be applied on heart rate or power or none of them.

Cheers,

Guillaume Lemaitre

0001-Add-shade-for-heart-rate-data.patch (25.7 kB) Guillaume Lemaitre, 07/01/2012 04:22 pm
Add
Related issues

History
#1 Updated by Guillaume Lemaitre 4 months ago

Assignee set to Guillaume Lemaitre

Hey,

I will try to take care of this feature and come back with a patch to test.

Cheers,

Guillaume Lemaitre
#2 Updated by Guillaume Lemaitre 4 months ago

File 0001-Add-shade-for-heart-rate-data.patch added
Patch Attached changed from No to Yes

Hi,

I have a first version of how it should be possible to propose the option shade for heart rate and power data.
I am not totally sure that it is without bugs because I am not really confident at some points if I took the good information to display with qwt. At least, it could give a good start;

Best regards,

Guillaume Lemaitre
#3 Updated by Mark Liversedge 4 months ago

Status changed from New to Feedback
Target version set to 3.0

I applied and GC core dumped with:

GoldenCheetah: AllPlot.cpp:1250: void AllPlot::showPower(int): Assertion `id != Qt::PartiallyChecked' failed.
Aborted (core dumped)

Is this the latest patch?
#4 Updated by Guillaume Lemaitre 4 months ago

Yes it was the last patch. I didn't get this bug, this is strange. I think that the problem is the following. Previously the message with id was sent by the currentIndex of the combobox and was between 0 and 2. I replaced this combobox by a checkbox where the index can be only 0 or 2 (Qt::UnChecked or Qt::Checked). The only thing that I can imagine is that somewhere in the code, the id == 1 is still send. I will try to find it.

Best,
#5 Updated by Mark Liversedge 17 days ago

Any news on this Guillaume?

I downloaded the Mac OSX 10.4 version onto my eMac running Mac OSX 10.4.11 with 1GB of SDRAM and a 700MHz processor. I also have the PL2303 driver downloaded and installed on my computer, but when I go to download my SRM Powercontrol V directly into Golden Cheetah, the program closes. I have tried it multiply times and the same thing happens over and over.

History
#1 Updated by Rainer Clasen over 1 year ago

Hmm, on a first glance, this might be related to srmio...
Maybe some endianess issue? Is anybody using SRM download on PPC successfully?

Would be nice if an OSX savvy person could help Andrew collecting some debug information (stack trace, ...) to narrow down the issue.

@andrew: Just to clarify: GC closes each time you try to download? Does this also happen, when you try to clear the PCV memory from the seperate Menu entry?

Rainer
#2 Updated by Rainer Clasen over 1 year ago

Hi Andrew,

hope, you're still interested in this issue...

Did you try to import a SRM file, as well?

I'm asking, because the PCV download first saves the data to a file and
then reads it, again. Actually I found and fixed some bug in the file
reader, that might prevent SRM files bein read on PPC / big endian
machines (issue #348).

Would be nice, if we could narrow down the crash to either file reading or
the actual download.

Rainer
#3 Updated by Mark Liversedge over 1 year ago

Status changed from New to Closed
Target version set to 3.0

#553

Power readings seem to be too high.

When coasting, power goes to negative for a while.

In fortius_1942.txt, the file accompanying the Linux driver by Michel Dagenais, it is said that the values in bytes 39&40 is the force on the wheel, not the power. Force x Speed would yield power:

Bytes 39, 40 is the force on the wheel to compute the power
(little endian, two's complement) When pedalling fast and letting go suddenly,
the force may be negative. The force multiplied by the speed gives the power.

I'll check if I can fix this during my Christmas holiday.

fortius_1942.txt - Text file describing Fortius protocol (9.2 kB) Ilja Booij, 12/20/2011 12:12 am
Add
Related issues

History
#1 Updated by Ilja Booij 11 months ago

File fortius_1942.txt added
#2 Updated by Mark Liversedge 11 months ago

Take care here. I spent a long time working on this, I may have got it wrong, but you will see power tracking in ergo mode that suggests it is correct. What makes you think it is too high?

I think calibration is probably required ... but have not worked on that bit yet.
#3 Updated by Ilja Booij 11 months ago

Well, my ride yesterday was just way too easy.

My FTP is about 295W, but I could hold 370W without really breaking a
sweat. Also, in slope mode, with the slope at about 6% (indicated, it
felt like less), I was at 250W. I then increased the slope by about 2%
without changing cadence and the power increased to 400W, before going
back to 250W, all without change cadence. This cannot be right, can
it?

I rebooted and started the Fortius software (the old blue software, I
don't have TTS), did a manual slope program. The same wattages felt a
lot harder and I did not experience the behaviour of the power going
down after having increased the slope. That made me believe that
something is different.

I have not tested with my power meter (Power2Max) yet. I'll have to do
some power meter swapping to do that.

It could of course be that our Fortius firmware files are different,
which could also explain the different behaviour. The md5sum of my
firmware file is 432c1a4fc03dd96f51f2607e46c5f25f.
#4 Updated by Ilja Booij 11 months ago

Forgot to add: Yes the power tracking does work very nicely, which would indicate that power readings are correct.

I'll investigate using my power meter. That'll probably help.

Ilja
#5 Updated by Ilja Booij 11 months ago

I have made some changes which seem to make power readings and load settings work better. Instead of interpreting the values from bytes 39 and 40 as the power (times 10), I interpret them as the force (inspired by the document of Michel Dagenais). Force x Speed (in m/s) yields power.

The interpretation of the speed was also wrong, I think. The value of bytes 33 and 34 seems to be the speed in meters per second times 1000.

I'll do a real test tomorrow, to see if my heart rate and feel matches better now. This weekend I'll probably be able to test with power meter.
#6 Updated by Ilja Booij 10 months ago

Unfortunately, the numbers are still off. It's better than it was, but still too easy.

I have not checked with a power meter equipped bike yet. As my trainer bike has Italian threads, I cannot just swap bottom brackets. I'll try to put the PM on my CX bike and test with that.

Quite disappointed, but not giving up yet..

#554

When riding at 0% it feels like going downhill steeply.

Steps to reproduce:

Open 'Training' mode.
Choose Tacx Fortius as device.
Set manual slope mode.
Start cycling.
After some initial resistance, the resistance goes to 0. From about 4% (on the display) the feeling starts to equate to riding on a level road.
In fortius_1942.txt (attached) the protocol for the Fortius is explained, perhaps this will give some idea about how to tackle this.

I'll start working after having fixed #553.

After a ride last Saturday I have some errors in my Critical Power figure (first 5 seconds). See the attached printscreen. Its due to the attached data. I cannot find some wrong data which can cause this weir figure. Is there a solution?

Thanks a lot!

Critical_Power.jpg (254.8 kB) Tom Wassink, 08/03/2011 03:12 pm
mrt_5.csv (296.3 kB) Tom Wassink, 08/03/2011 03:12 pm
History
#1 Updated by Mark Liversedge over 1 year ago

Status changed from New to Resolved
Your file has lots of gaps in recording and goes back in time at around 2:33 ... I used the editor to fix that by deleting a few samples and it looked fine after that.
#2 Updated by Mark Liversedge over 1 year ago

Status changed from Resolved to Closed
A ride file integrity check will fix this, I am closing this bug report since the bug is not with CP.

If you add or delete a ride the CP curve is not updated to reflect this until GC is restarted, or the chart is deleted/re-added or a different season is selected/deselected.

It would be better to refresh the chart if a ride is added/deleted in the current range. Since there is a signal in mainwindow to notify of add/delete this should be trivial to implement.

This was originally raised by Guillaume Lemaître on the mailing list:

"Then,
Start GC
Import my last ride from file.
Observing again the CP chart (which was created from the last time), the curve (black) representing this last ride is ok.
But if you have any change in the Overall Season Curve (Best Power), it will not occur on this second curve (zonal color curve). However, if you restart GC (or maybe add a new chart again) the overall curve will be fine."
Associated revisions

Revision 8f53e1c
Added by Mark Liversedge over 1 year ago

Refresh CP curve when rides added/deleted

This patch forces a refresh of the CP curve
plot (if it is visible) when rides are added
or deleted.

Fixes #400.

History
#1 Updated by Mark Liversedge over 1 year ago

Status changed from New to Closed
% Done changed from 0 to 100
Applied in changeset 8f53e1c.

This is an update to the old issue 402, which was about handling null rides / state well.

Thinking about the GC UX there is more to this than just the blank state. There are also functions that are hidden, or don't exist and really should if we are to have a consistent and usable application.

See this article for some insight into handling complexity: http://uxmag.com/articles/the-dirtiest-word-in-ux-complexity

So here they are:

(1) HANDLE BLANK STATE BETTER

a. No data to show on chart - handle this gracefully -- When a cyclist has no rides most of the charts are notified that there is nothing to display by setting the ride property to NULL. On the most part this is fine, but since this will be the first experience any new user will have of GC it is very important that it "feels" ok, and charts don't crash or do odd things when you try to interact with them.

b. Not data available/blank state - offer help to new users, with visually appealling and friendly help to guide them to the most common tasks when first arriving; importing current/old data, configuring their devices and preferences etc. This is going to be very different for Home, Diary, Analysis and Train views.

(2) STOP HIDING FUNCTIONS

Right click must be augmented -- ie. allow right click, but also provide a more obvious route to get to the same functionality. The functions currently 'hidden' need to be made visible to the user, whilst retaining a clean an unobtrusive UI. The top examples are;

a. Chart Settings -- they are hidden behind a menu -- address this - done with reveal controls see below
b. Chart settings is being used as a 'catch all' -- e.g. ride editor find/anomalies, CP curve bests display
b. Sidebar Functions -- add/delete/save etc on the sidebar widgets are under right click -- make them more obvious by using buttons or even hover items (i.e. appear when you hover over the item).

(3) MISSING/INCONSISTENT FUNCTIONS

a. The train view sidebar doesn't have right click functions -- create them and make them consistent with point 2 above -- add/delete device, workout, media

b. Splitters are hard to grab and hide/unhide -- make them easier to grab and add toggle buttons to show hide them.

c. The splitter in summary and detail doesn't get remembered -- it does everywhere else.

d. Diary view summary level selection doesn't get remembered -- it does everywhere else.

(4) REMOVE DUPLICATE FUNCTIONS

a. Deprecate Weekly view by recreating functionality in Diary view

b. Deprecate Performance Manager -- when its functionality is present in LTM PMC -- notably the use of a span slider.

I noticed that the MAP tab was just displaying a blank page when I was connected to my work VPN.
It seems Golden Cheetah doesn't detect the Internet Options Proxy settings in Windows nor does it have anywhere that you can set a proxy, that I can find.

Need the ability to define a proxy server or have Gold Cheetah read the Internet Options Proxy Settings in Windows for users who are on a VPN or who have some other need to have a proxy server set when connected to the Internet.

Add
Related issues

History
#1 Updated by Mark Liversedge over 1 year ago

Target version set to 3.0
#2 Updated by Dave Severn about 1 year ago

Tested in latest version of 3.0.
I defined the proxy that I use in IE in Golden Cheetah and it still doesn't display the map.
If someone needs me to do any type of testing if they don't have a VPN, please let me know. I'll be happy to assist.
#3 Updated by Mark Liversedge about 1 year ago

Proxies are not working at present .. I spent some time on it last month and found the proxy support in Qt is a bit weird, or more accurately, I couldn't get it to pick up OS level settings on Linux.

It will get fixed before we release 3.0 early next year, which is why we set the target version for resolving this bug to 3.0.

Cheers,
Mark
#4 Updated by Dave Severn about 1 year ago

No worries. Just saw that there is a place to enter a Proxy in version 3.0 so I thought I'd test it in the latest 3.0 build.
Personally, I like having the ability to enter a proxy rather than have it picking it up from Windows IE settings. There are times when I might have them set differently, depending on what network I'm connected to.
#5 Updated by Gareth Coco 9 months ago

Tracker changed from Bug to Feature

Hi all,

dev 3.0 on kubuntu 10.10

When i use the prev/next button in monthly diary, then the vertical header adjusts to the size needed to show the weeknumbers, but not always.

Sometimes i can't see the complete weeknumbers because the vertical header is too small. (test it and go from jan 2011 to may 2011 using the next button )

I debugged headerData in GcCalendarModel.h and obviously the week numbers are set correctly there.
QheaderView is not reimplemented in GC so i suspect this is a Qt bug. i'll check if i can reproduce it with a minimal compilable example and send it to the trolls.

Here is one line of code that can resolve the issue :
in DiaryWindow.cpp add after line 81 : monthlyView->verticalHeader()->setFixedWidth(QFontMetrics (monthlyView->font()).width("ww"));
I think it's better to have one fixed width to avoid unnessessary rearranging of the agenda horizontally even if the width is always set correctly.

Best Regards,

Eddy

History
#1 Updated by Mark Liversedge over 1 year ago

Priority changed from Normal to Low
Update to low priority since it is cosmetic (low when compared with crashes).
#2 Updated by Mark Liversedge over 1 year ago

Status changed from New to Closed
I am closing this since the calendar no longer shows week numbers, since ironically,it stole screen estate. If you would like support for week numbers (?) then can you please raise a feature request for that.

A mini-calendar will be reinstated in v3, and will likely use the same widget

hi,

I'm appreciate if you tag the released version to github tree, or put an released
source tarball on website download page.

(I'm a debian package maintainer, and want to know the url where I can get
a specific version of software source code archive.)

In weekly metrics (i.e. weekly climbing) the days used to make a week are wrong. For example on july 18th (sunday) "this week" is july 16-23 (friday-friday). It should be July 12-18 (monday - sunday).

Screenshot-Mark_Liversedge.png (87.3 kB) Mark Liversedge, 14/08/2010 02:46 pm
GoldenCheetahweekBug.png (187.7 kB) Eric Murray, 17/08/2010 02:47 am
Associated revisions

Revision 8f42f84
Added by Mark Liversedge over 1 year ago

Fix LTM plot to always bin in Mon-Sun weeks

Fixes #120.

History
#1 Updated by Mark Liversedge about 2 years ago

Status changed from New to Feedback
I went to fix this, but I couldn't get it to exhibit this behaviour. This week, for example starts on Aug 9th and finishes on August 15th. Similarly when grouping in Weeks not days.

I wonder if this is a localisation issue or something??????
#2 Updated by Eric Murray about 2 years ago

I can still see the bug. Select "this year" for date range, "elevation gain" for metric, and chart "weeks": the most recent week is from aug 6 - aug 13.

If I select "this week" for date range and chart days, then it comes out correct.
#3 Updated by Mark Liversedge about 2 years ago

File Screenshot-Mark_Liversedge.png added
weird. screenie attached and it is fine for me.
#4 Updated by Eric Murray about 2 years ago

File GoldenCheetahweekBug.png added
I'm on Linux. Screenshot attached.
#5 Updated by Mark Liversedge about 2 years ago

Aha. I get the same if I choose this year. Its all about the start date. The function groupForDate() in LTMPlot.cpp needs to use week numbers rather than taking the day range and dividing by 7.

Of course its more complicated than that when the date range spans a year, since the week# is likely to repeat, so you need to add the year into the equation, but then not every year has a week 53, although some do.

Its quite a tricky problem, good luck!!!
#6 Updated by John Ehrlinger about 2 years ago

First post, and I haven't dug into the code yet.

BUT, shouldn't there be someway of stating that the week starts on Monday (or Sunday)? Then every week metric would start on Monday (or whatever user pref was selected).

It does change by start date, selecting 2010 picks one day, last 12 months picks another. So I can only compare weeks on Sunday night?

There has to a be a pattern for this somewhere.
#7 Updated by John Ehrlinger about 2 years ago

Qt Version set to 4.6
OK. I've poked at this some more. Here is my behavior:

Choose chart of interest: (i.e. Cardiovascular Response, or Time & Distance... whatever)

Select "Weeks" view. The range of the last week is 9/3-9/10 (Friday to Friday) (today is Thurs 9/9).

Selecting a different chart produces the same weekly ranges.

If I select a new Date Range, the week shifts to start on Monday. Returning to the previous DateRange, maintains the new week range, starting on Monday.

It seems LTMWindow::dateRangeSelected (Line 224 LTMWindow.cpp) which forces weeks to start on Monday, is only called on DateRange change, but not on "group by" change. It's getting thick now, I am not familiar enough with the code yet to attempt a patch here.

Or lift the logic from LTMWindow::dateRangeSelected and place it in groupForDate() in LTMPlot.cpp.
#8 Updated by Mark Liversedge over 1 year ago

Target version set to 3.0
#9 Updated by Mark Liversedge over 1 year ago

Status changed from Feedback to Closed
% Done changed from 0 to 100
Applied in changeset 8f42f84

How to replicate:
Select the oldest ride in the ride list.
Use the up arrow to the column header "All Rides"
Use the down arrow to navigate to the first ride in the list
Segmentation fault.

Associated revisions

Revision e8d213c
Added by Mark Liversedge over 1 year ago

Temporary Fix for Ride Selection after NULL ride selected

When you clicked on 'All Rides' mainwindow emits a rideSelected
signal with a ridefile of NULL. When then selecting a valid ride
a SEGV occurred.

This temporary fix removes that signal, but the underlying issue
related to actions after a NULL ride is selected need to be resolved.

Fixes #318.

History
#1 Updated by Mark Liversedge over 1 year ago

Status changed from New to Closed
% Done changed from 0 to 100
Applied in changeset e8d213c.

he "Today's data" curve shown no data greater than 6 minutes on some files only.
This occurred after the new multi-thread implementation on V3

bad_file.zip - Hopefully demonstrates the problem. (234.6 kB) Gary Smith, 25/04/2011 12:48 pm
Screenshot-Mark_Liversedge.png (95.4 kB) Mark Liversedge, 25/04/2011 01:03 pm
Associated revisions

Revision 64d44cd
Added by Mark Liversedge over 1 year ago

Fix CP curve only shows first 6 seconds bug

Many thanks to Gary Smith for helping to diagnose and fix
this error. It is caused by ridefiles that have a gap in
recording at the very start of the ride (i.e. the first
sample is > recIntSecs).

Hopefully this means the CP code is now robust. It is also
worth noting that after fixing the erroneous copy/paste
code in compute() it is now 5 times faster than the original
code and computes 5 times more data series.

Fixes #316.

History
#1 Updated by Mark Liversedge over 1 year ago

File Screenshot-Mark_Liversedge.png added
Status changed from New to Feedback
Mmmm. Wonder it its a 64 bit issue? Also, have you tried after today's fix?

Attached a screen grab of the plot imported as ridden today.
#2 Updated by Mark Liversedge over 1 year ago

FWIW, I ran fix gaps in recording on the source file (there were a few long gaps) and it cleaned up some of the anomalies in the CP chart. Not sure if that is related, but worth a look.
#3 Updated by Gary Smith over 1 year ago

Target version set to 3.0
Mark, yes it is the latest build.
Note that I only saw this after the multiple thread implementation.

But I believe that I have a clue for you :-) ...
All of the rides which show the problem have a start time time which is not 00:00:00 or 00:00:01. That is there is a "delay" of 6 secs or more. That is they start at 00:00:06 etc. This is probably due to the "auto-pause" feature being enabled on the Garmin.
#4 Updated by Mark Liversedge over 1 year ago

Status changed from Feedback to Closed
% Done changed from 0 to 100
Applied in changeset 64d44cd.

2011-06-04__22_22_07.avi - video example (2.5 MB) Rob Massa, 04/06/2011 04:29 pm
History
#1 Updated by Mark Liversedge over 1 year ago

Status changed from New to Closed
This is a duplicate of #224, I should have closed it before. Thank you for the video, I will attach it to 224. I am looking to solve this at the moment, but am failing to recreate it. It is such a widely reported bug and has such dramatic impact! I will fix it.

In the developer release of 1.4 if you delete a ride that you created notes for, the notes are not deleted. So if you download a different ride (maybe different source such as tcx file instead of csv file) the notes from the first ride file load in for the second ride.

Associated revisions

Revision aa9f6c5
Added by Mark Liversedge over 1 year ago

Fix delete ride to remove .notes file

Will also remove the .cpi or .cpx if it is there.
It still renames the original to original.bak so
it doesn't actually zap the file.

Fixes #115.

History
#1 Updated by Robert Carlsen over 2 years ago

Status changed from New to Feedback
What is the expected behavior? While this may technically be an oversight (ie. not cleaning up entirely after a user-initiated action)....this could be a "feature. not a bug". :)

We're matching based on the date/time of the ride, and if it's exactly the same it still represents the same event, regardless of whichever format/path used to get the ride data into Golden Cheetah...right?

-r
#2 Updated by Mark Liversedge over 1 year ago

Target version set to 3.0
Patch Attached set to No
#3 Updated by Mark Liversedge over 1 year ago

Status changed from Feedback to Closed
% Done changed from 0 to 100
Applied in changeset aa9f6c5.

Related to bug 400, charts should update to reflect aggregated data needs to be recomputed when rides are added and deleted. this affects;

Metrics chart
Treemap chart
Histogram (when plotting a range)
Performance Manager
Weekly Summary
CP chart (when plotting a range) already fixed in Bug 400.
This will mean that ride add/delete is going to be a more expensive operation if lots of charts are open so great care needs to be taken to ensure the update is only performed if necessary.

History
#1 Updated by Mark Liversedge over 1 year ago

% Done changed from 0 to 30
Metric chart fixed in commit a69c7b.
CP was fixed in commit 8f53e1.
#2 Updated by Mark Liversedge over 1 year ago

% Done changed from 30 to 50
Histogram chart fixed in commit 78f683.
#3 Updated by Mark Liversedge over 1 year ago

% Done changed from 50 to 70
Treemap plots, remarkably, already handle ride add/delete. Go me.
#4 Updated by Mark Liversedge 10 months ago

% Done changed from 70 to 90
Weekly Summary was fixed in commit 75334fd.
#5 Updated by Mark Liversedge 10 months ago

Status changed from New to Closed
% Done changed from 90 to 100
PMC was update in commit c2b847d.

All plots are now up to date, this bug can be closed.

This file results in a high 5s HR. Looking at the editor, nothing is over 170. This effects the maximal value for the entire season also... obviously.

This is with the latest git fetch.... (this timestamp any way)

2011_04_17_08_54_25.fit - Garmin fit file (136.7 kB) John Ehrlinger, 26/04/2011 10:11 pm
HR.jpeg - Resulting HR critical value (66.9 kB) John Ehrlinger, 26/04/2011 10:11 pm
Associated revisions

Revision f57ac7d
Added by Mark Liversedge over 1 year ago

Fix CP calculation for files with sub-recIntSecs samples

Peak 1s - 5s critical heartrate was way off the charts and did
not represent the data within the ride file.

Almost certainly caused by the WKO+ file importer, or possibly
by the WKO+ files themselves. It is possible to have ride files
with samples that are shorter than recIntSecs, e.g. where the
recording sample rate is 1s you might see:

Time HR
01:21:32.0 157
01:21:32.7 157
01:21:33.0 157

In this case there are two samples between 1:21:32 and 1:21:33 rather
than the expected one sample. The code to compute averages used the
duration and recIntSecs to determine the average. This patch now
maintains a count instead.

Fixes #319

History
#1 Updated by Mark Liversedge over 1 year ago

Status changed from New to Closed
% Done changed from 0 to 100
Applied in changeset f57ac7d.

The PM lines look huge. Same on metric page.

Is this a setting somewhere, or fixed line widths.

pm.jpeg (90.3 kB) John Ehrlinger, 13/04/2011 11:24 pm
History
#1 Updated by Mark Liversedge over 1 year ago

Status changed from New to Rejected
Configyration Pane - Appearances allows you to set the line widths to use in plots.
#2 Updated by John Ehrlinger over 1 year ago

Thanks: Line width worked. But:

Lines on the ride plots (by default) are one width (the width speced in the apperance page), and the PM are another (maybe 2 or 4 times the appearance width). Until AFTER a user changes the line width.... then they are the same

0001-Corrected-to-in-CycleOps-formula.patch (1018 Bytes) Darren Hague, 17/01/2011 10:18 pm
0001-Fix-CycleOps-Fluid-2-virtual-power-calculation.patch (1 kB) Darren Hague, 26/03/2011 08:04 am
Associated revisions

Revision 7e42cdd
Added by Darren Hague almost 2 years ago

Corrected - to + in CycleOps formula

Fixes #239

Revision 010e27e
Added by Darren Hague over 1 year ago

Fix CycleOps Fluid 2 virtual power calculation

Fixes #239
There was a missing "break" after the CycleOps calc, so it went ahead
and overwrote the value with the BT-ATS calc. "break" now inserted.

History
#1 Updated by Darren Hague almost 2 years ago

File 0001-Corrected-to-in-CycleOps-formula.patch added
Status changed from New to Resolved
% Done changed from 0 to 100
Patch Attached changed from No to Yes
#2 Updated by Darren Hague almost 2 years ago

Status changed from Resolved to Closed
Applied in changeset 7e42cdd.
#3 Updated by Darren Hague over 1 year ago

File 0001-Fix-CycleOps-Fluid-2-virtual-power-calculation.patch added
Target version changed from 2.1 to 3.0
Added missing "break" statement to really fix CycleOps Fluid2 calculation

The HrPw plot crashes with glibc memory errors when it is selected if the cyclist HR zones have not been set.

History
#1 Updated by Mark Liversedge over 1 year ago

Status changed from New to Closed
This was fixed in commit 83b2aa8. Closing.

GC appears to be importing the speed data from Power Agent exported files incorrectly. I opened the .tcx file and the speeds appear correct, but when I look at the same data in GC Editor the speed is all over the place.

Jason_2010-11_2011-04-09_08-59-21.pwx (511.8 kB) Jason Swindle, 21/04/2011 01:03 pm
Jason_2010-11_2011-04-09_08-59-21.tcx (1.9 MB) Jason Swindle, 21/04/2011 01:03 pm
Associated revisions

Revision 780ae99
Added by Mark Liversedge over 1 year ago

Better support for Negative, Inf, NaN and High Values

Some ride file formats use -1 to indicate sensor not
present or data loss (e.g. TPX) and on occasion a NaN
or Infinite value will be presented.

This patch handles this by converting negative data sample
values to zero and handling out of bounds values when
selecting zone ranges.

This is not a substitute for better handling of poor ride
data but it reduces the effect.

Also fixes #311.

Revision 00959be
Added by Mark Liversedge over 1 year ago

Better support for Negative, Inf, NaN and High Values

Some ride file formats use -1 to indicate sensor not
present or data loss (e.g. TPX) and on occasion a NaN
or Infinite value will be presented.

This patch handles this by converting negative data sample
values to zero and handling out of bounds values when
selecting zone ranges.

This is not a substitute for better handling of poor ride
data but it reduces the effect.

Also fixes #311.

History
#1 Updated by Mark Liversedge over 1 year ago

Priority changed from Normal to High
The attached files also cause a crash when HR zones are not set see trace:

Program received signal SIGABRT, Aborted.
0x00007ffff31fad05 in raise () from /lib/x86_64-linux-gnu/libc.so.6
(gdb) bt
#0 0x00007ffff31fad05 in raise () from /lib/x86_64-linux-gnu/libc.so.6
#1 0x00007ffff31feab6 in abort () from /lib/x86_64-linux-gnu/libc.so.6
#2 0x00007ffff3f9c785 in qt_message_output(QtMsgType, char const*) () from /opt/QtSDK/Desktop/Qt/473/gcc/lib/libQtCore.so.4
#3 0x00007ffff3f9c96a in ?? () from /opt/QtSDK/Desktop/Qt/473/gcc/lib/libQtCore.so.4
#4 0x00007ffff3f9cb25 in qFatal(char const*, ...) () from /opt/QtSDK/Desktop/Qt/473/gcc/lib/libQtCore.so.4
#5 0x000000000066791d in operator[](this=0x7fffffffc940, array=..., series=RideFile::watts)

at /opt/QtSDK/Desktop/Qt/473/gcc/include/QtCore/qvector.h:347
#6 RideFileCache::computeDistribution (this=0x7fffffffc940, array=..., series=RideFile::watts) at RideFileCache.cpp:709
#7 0x0000000000667c65 in RideFileCache::compute (this=0x7fffffffc940) at RideFileCache.cpp:288
#8 0x00000000006682a0 in RideFileCache::refreshCache (this=0x7fffffffc940) at RideFileCache.cpp:240
#9 0x00000000006691d2 in RideFileCache::RideFileCache (this=0x7fffffffc940, main=0xebf2d0, fileName=,

passedride=, check=true) at RideFileCache.cpp:92
#10 0x00000000005caa68 in MetricAggregator::refreshMetrics (this=0x10244b0) at MetricAggregator.cpp:161
#11 0x00000000005b78f5 in MainWindow::MainWindow (this=0xebf2d0, home=...) at MainWindow.cpp:163
#12 0x000000000071dfd9 in main (argc=1, argv=) at main.cpp:124

(gdb) bt full
#0 0x00007ffff31fad05 in raise () from /lib/x86_64-linux-gnu/libc.so.6

No symbol table info available.
#1 0x00007ffff31feab6 in abort () from /lib/x86_64-linux-gnu/libc.so.6

No symbol table info available.
#2 0x00007ffff3f9c785 in qt_message_output(QtMsgType, char const*) () from /opt/QtSDK/Desktop/Qt/473/gcc/lib/libQtCore.so.4

No symbol table info available.
#3 0x00007ffff3f9c96a in ?? () from /opt/QtSDK/Desktop/Qt/473/gcc/lib/libQtCore.so.4

No symbol table info available.
#4 0x00007ffff3f9cb25 in qFatal(char const*, ...) () from /opt/QtSDK/Desktop/Qt/473/gcc/lib/libQtCore.so.4

No symbol table info available.
#5 0x000000000066791d in operator[](this=0x7fffffffc940, array=..., series=RideFile::watts)

at /opt/QtSDK/Desktop/Qt/473/gcc/include/QtCore/qvector.h:347
No locals.
#6 RideFileCache::computeDistribution (this=0x7fffffffc940, array=..., series=RideFile::watts) at RideFileCache.cpp:709

value = 1
offset =
dp = 0x122aee0
container = {c = {{d = 0x12b93d0, p = 0x12b93d0}}, brk = 0, i = 0x12b97d8, e = 0x12c15c0}
zoneRange = 0
hrZoneRange = -1
decimals =
min = 0
max =
#7 0x0000000000667c65 in RideFileCache::compute (this=0x7fffffffc940) at RideFileCache.cpp:288

thread1 = { = {}, ride = 0x121f1f0, array = @0x7fffffffc968, integratedArray = {{d = 0xc77d20, p = 0xc77d20}},
series = RideFile::watts}
thread3 = { = {}, ride = 0x121f1f0, array = @0x7fffffffc978, integratedArray = {{d = 0xc77d20, p = 0xc77d20}},
series = RideFile::cad}
thread5 = { = {}, ride = 0x121f1f0, array = @0x7fffffffc988, integratedArray = {{d = 0xc77d20, p = 0xc77d20}},
series = RideFile::kph}
thread7 = { = {}, ride = 0x121f1f0, array = @0x7fffffffc998, integratedArray = {{d = 0xc77d20, p = 0xc77d20}},
series = RideFile::NP}
thread2 = { = {}, ride = 0x121f1f0, array = @0x7fffffffc970, integratedArray = {{d = 0xc77d20, p = 0xc77d20}},
series = RideFile::hr}
thread4 = { = {}, ride = 0x121f1f0, array = @0x7fffffffc980, integratedArray = {{d = 0xc77d20, p = 0xc77d20}},
series = RideFile::nm}
thread6 = { = {}, ride = 0x121f1f0, array = @0x7fffffffc990, integratedArray = {{d = 0xc77d20, p = 0xc77d20}},
series = RideFile::xPower}
#8 0x00000000006682a0 in RideFileCache::refreshCache (this=0x7fffffffc940) at RideFileCache.cpp:240

outFile =
writeerror = false
cacheFile =
#9 0x00000000006691d2 in RideFileCache::RideFileCache (this=0x7fffffffc940, main=0xebf2d0, fileName=,

passedride=, check=true) at RideFileCache.cpp:92
rideFileInfo = {d_ptr = {d = 0x11b6eb0}}
---Type to continue, or q to quit--
#2 Updated by Mark Liversedge over 1 year ago

The file in question has a huge (2hr) gap in recording and contains numerous negative values for power and cadence (to indicate sensor not present).

I will push a patch to handle these situations more gracefully (i.e. don't crash), but much of what is wrong with this ride file needs to be corrected manually I'm afraid.
#3 Updated by Mark Liversedge over 1 year ago

Status changed from New to Closed
% Done changed from 0 to 100
Applied in changeset 780ae99.

The disk timer isn't being enabled.

Here's a fix for the bug.

glonnon@825bdee

Associated revisions

Revision 8913b37
Added by Mark Liversedge almost 2 years ago

Fix 'Save data' in RealtimeWindow

A previous commit stopped disk updating from working, i.e. saving
workout data to a .csv file. This patch fixes that.

Fix supplied by Greg Lonnon, Fixes #254.

History
#1 Updated by Mark Liversedge almost 2 years ago

Status changed from New to Closed
Applied in changeset 8913b37

Placeholder bug report for UI nits that need to be resolved;

1. RideNavigator resize column sometimes results in a weird gap (on linux anyway)
2. RideImportWizard delayed refresh when opening a GTC "export" i.e. contains multiple files
3. Mouse over some charts in tile mode and the mouse cursor is left in wrong state
4. RideFileCache / CP plot should set cursor to busy when aggregating rides.

As more are found please add to the list above.

Add
Related issues

History
#1 Updated by Gareth Coco about 1 year ago

Train View Controls - When playing back video and you press the stop button, the pause button does not revert to a play button.
#2 Updated by Mark Liversedge about 1 year ago

Just fixed the train view controls thing with commit #2007759.
#3 Updated by Gareth Coco about 1 year ago

When in Train mode, you can select more than Device. Should only pick one at a time.
You can also select the headers - Devices and Workout Library which you probably shouldn't be able to do.
#4 Updated by Arturo Mac Dowell 12 months ago

Operating system changed from Linux to Win XP
Arch. changed from x86-64 bit to x86

Add an button as described in Feature #484 (closed by Jaimie). It should call the behaviour of the View>Show Sidebar toggle. The design is described in the closed case and would make this beahviour far more usable.
#5 Updated by Mark Liversedge 12 months ago

The show/hide button calls the same action to toggle showing the sidebar as the menu option does. Not sure what you are suggesting.
#6 Updated by Arturo Mac Dowell 12 months ago

My suggestion is that instead of clicking "View" and then checking or unchecking "Show Sidebar" (2 clicks) you also have the option of hiding and un-hiding the sidebar via a single click in a button on the Sidebar. Just as you would in the sidebar http://maps.google.com/. This is such a frequent operation that double-clicking is a pain. The visual design is described in Feature #484.

I would also like to add to this bug features #485 and #486 which could also be closed.
#7 Updated by Jamie Kimberley 12 months ago

There is a show/hide button for the sidebar. Perhaps my wording in #484 confused you. The button is located ABOVE the sidebar, not in the corner like you proposed. We may consider changing the icon and the location if we feel that it will be more in line with other applications, but I think it is pretty good for a first go.
This is also why i moved this to UI nits.
#8 Updated by Arturo Mac Dowell 12 months ago

I guess it is not in the latest build, at least the Windows 32 build. I haven't found it, which helped in the confussion. Thanks.
#9 Updated by Mark Liversedge 12 months ago

The hit area for buttons in the toolbar is way small .. you have to hit almost directly in the center to activate the button. This is a bug in QT (see https://bugreports.qt.nokia.com/browse/QTBUG-15936). This is exacerbated by the recent update to use a windows style to get the buttons to bounce when pressed. This update should be reverted until Nokia fix the QT bug.
#10 Updated by Gareth Coco 11 months ago

For me at least, I think that when you select the Train tab, the Workout Library section should be selected by default.
I also think that if possible the Workout Library section should not be displayed when in any other tab (Home, Diary & Analysis) and is has no relevance in these sections.
#11 Updated by Mark Liversedge 10 months ago

The hit area bug on mac is fixed in the current 4.8 RC. It needs a 64bit build environment.
#12 Updated by Mark Liversedge 9 months ago

The recent mods to the GC bubble to support imperial/metric and date formats have mucked up the alignment of the data being displayed - it looks amateurish and should be corrected.
#13 Updated by Mark Liversedge 15 days ago

the right side bar with the mini calendar doesn't show properly and its state should be saved too, so it opens with it active or not. also, not sure it is relevant outside of analysis mode?

How to reproduce:

1. open the ride editor
2. Highlight "half" the ride (left garmin on by accident).
3. Select either "Cut" or "Delete Rows"
4. Select Save
5. Exit GoldenCheetah
6. Start GoldenCheetah
7. Edited ride was not saved.

Other issues:
The Ride summary doesn't change on the edit, and the ride metrics are not updated.

This is occuring on V3, I don't know about V2.

note: I will look at this when I have time, just adding it to the tracker so we don't forgot about it.

Associated revisions

Revision 1d135ae
Added by Mark Liversedge over 1 year ago

Fix Save when old .bak exists

If you save a ride and then delete it. The re-import and save
you will end up with two copies of the ride in the ride list.

This is because when we save the first time the original file
is renamed to e.g. ride.tcx.bak and the new ride.json is then
created. All is well.

But then delete the ride and it will rename ride.json to
ride.json.bak. Again, All is well.

Now, re-import the ride. We now have; ride.tcx.bak and
ride.json.bak and ride.tcx. Again, all is well.

But now, if you make changes and save it will attempt to
rename ride.tcx to ride.tcx.bak AND FAIL. This is because
the old ride.tcx.bak file is there. It will then create
ride.json. All is NOT well, since we have two rides with
the same date and time but different extensions.

This patch fixes this by unlinking ride.ext.bak before
trying to rename the file.

Fixes #348.

History
#1 Updated by Jamie Kimberley over 1 year ago

Greg, Any chance this is related to #199? There the file was saved as duplicate, and the original file was left in the ride tree.
#2 Updated by Greg Lonnon over 1 year ago

There are three files with the same basename

2011_06_15_17_02_49.tcx
.json
.cpx
.tcx.bak

The date code looks like the tcx.bak was saved first, then the .tcx, then both the .cpx and .json.

Looking at the contents of the tcx file, it looks like the ride edit deleted the correct data in it.

But, the ride editor and the ride summary does not show the correct data. What priority of file extension do we use to calculate ride summary and other metrics.

Greg
#3 Updated by Mark Liversedge over 1 year ago

Priority changed from Low to High
This is a major bug -- changed to High Priority

It is caused by having multiple files with the same basename and different extensions.
#4 Updated by Mark Liversedge over 1 year ago

Status changed from New to Closed
% Done changed from 0 to 100
Applied in changeset 1d135ae

On compiled V3.0.0dev.

Attempt to drop Ride Summary or Ride Summary and Fields causes a crash. Critical Power, Weekly Summary and others. Is this a problem in choosing the ride date?

src/GoldenCheetah
Cannot open qollector_interpret program, available from http://opensource.quarq.us/qollector_interpret.
Bus::open: Can not get ibus-daemon's address.
IBusInputContext::createInputContext: no connection to ibus-daemon
glibc detected * src/GoldenCheetah: free(): invalid next size (fast): 0x000000000c6cb180 * ======= Backtrace: =========
/lib/libc.so.6(+0x774b6)[0x7f5e339894b6]
/lib/libc.so.6(cfree+0x73)[0x7f5e3398fc83]
/usr/lib/libQtGui.so.4(ZN11QTextEngine13clearLineDataEv+0x3d)[0x7f5e35725d3d]
/usr/lib/libQtGui.so.4(+0x47ac56)[0x7f5e35779c56]
/usr/lib/libQtGui.so.4(+0x64f8a1)[0x7f5e3594e8a1]
/usr/lib/libQtGui.so.4(_ZN9QTextEdit11resizeEventEP12QResizeEvent+0x3e)[0x7f5e3594ec8e]
/usr/lib/libQtGui.so.4(_ZN7QWidget5eventEP6QEvent+0x5d0)[0x7f5e3550cc60]
/usr/lib/libQtGui.so.4(_ZN6QFrame5eventEP6QEvent+0x26)[0x7f5e358d85e6]
/usr/lib/libQtCore.so.4(_ZN23QCoreApplicationPrivate29sendThroughObjectEventFiltersEP7QObjectP6QEvent+0x87)[0x7f5e34c9c507]
/usr/lib/libQtGui.so.4(_ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent+0x7c)[0x7f5e354b6fac]
/usr/lib/libQtGui.so.4(_ZN12QApplication6notifyEP7QObjectP6QEvent+0x14d)[0x7f5e354bcaed]
/usr/lib/libQtCore.so.4(_ZN16QCoreApplication14notifyInternalEP7QObjectP6QEvent+0x8c)[0x7f5e34c9ccdc]
/usr/lib/libQtGui.so.4(_ZN14QWidgetPrivate30sendPendingMoveAndResizeEventsEbb+0x19b)[0x7f5e3550bccb]
/usr/lib/libQtGui.so.4(_ZN14QWidgetPrivate11show_helperEv+0x23)[0x7f5e35510e23]
/usr/lib/libQtGui.so.4(_ZN14QWidgetPrivate12showChildrenEb+0xb1)[0x7f5e35511221]
/usr/lib/libQtGui.so.4(_ZN14QWidgetPrivate11show_helperEv+0x3f)[0x7f5e35510e3f]
/usr/lib/libQtGui.so.4(_ZN14QWidgetPrivate12showChildrenEb+0xb1)[0x7f5e35511221]
/usr/lib/libQtGui.so.4(_ZN14QWidgetPrivate11show_helperEv+0x3f)[0x7f5e35510e3f]
/usr/lib/libQtGui.so.4(_ZN7QWidget10setVisibleEb+0x1ba)[0x7f5e3551269a]
src/GoldenCheetah[0x45b010]
src/GoldenCheetah[0x538b9e]
/usr/lib/libQtGui.so.4(_ZN7QWidget5eventEP6QEvent+0x98c)[0x7f5e3550d01c]
/usr/lib/libQtGui.so.4(_ZN6QFrame5eventEP6QEvent+0x26)[0x7f5e358d85e6]
/usr/lib/libQtGui.so.4(_ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent+0xac)[0x7f5e354b6fdc]
/usr/lib/libQtGui.so.4(_ZN12QApplication6notifyEP7QObjectP6QEvent+0x3e2)[0x7f5e354bcd82]
/usr/lib/libQtCore.so.4(_ZN16QCoreApplication14notifyInternalEP7QObjectP6QEvent+0x8c)[0x7f5e34c9ccdc]
/usr/lib/libQtGui.so.4(+0x24ce8d)[0x7f5e3554be8d]
/usr/lib/libQtGui.so.4(+0x251763)[0x7f5e35550763]
/usr/lib/libQtGui.so.4(+0x251928)[0x7f5e35550928]
/usr/lib/libQtCore.so.4(_ZN23QCoreApplicationPrivate34sendThroughApplicationEventFiltersEP7QObjectP6QEvent+0x9b)[0x7f5e34c9c5cb]
/usr/lib/libQtGui.so.4(_ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent+0x26)[0x7f5e354b6f56]
/usr/lib/libQtGui.so.4(_ZN12QApplication6notifyEP7QObjectP6QEvent+0x96e)[0x7f5e354bd30e]
/usr/lib/libQtCore.so.4(_ZN16QCoreApplication14notifyInternalEP7QObjectP6QEvent+0x8c)[0x7f5e34c9ccdc]
/usr/lib/libQtGui.so.4(_ZN19QApplicationPrivate14sendMouseEventEP7QWidgetP11QMouseEventS1_S1_PS1_R8QPointerIS0_Eb+0x19e)[0x7f5e354bbdbe]
/usr/lib/libQtGui.so.4(+0x240345)[0x7f5e3553f345]
/usr/lib/libQtGui.so.4(_ZN12QApplication15x11ProcessEventEP7_XEvent+0x85c)[0x7f5e3553dc5c]
/usr/lib/libQtGui.so.4(+0x26b0e2)[0x7f5e3556a0e2]
/lib/libglib-2.0.so.0(g_main_context_dispatch+0x1f2)[0x7f5e31ce9342]
/lib/libglib-2.0.so.0(+0x442a8)[0x7f5e31ced2a8]
/lib/libglib-2.0.so.0(g_main_context_iteration+0x6c)[0x7f5e31ced45c]
/usr/lib/libQtCore.so.4(_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE+0x73)[0x7f5e34cc9193]
/usr/lib/libQtGui.so.4(+0x26aa4e)[0x7f5e35569a4e]
/usr/lib/libQtCore.so.4(_ZN10QEventLoop13processEventsE6QFlagsINS_17ProcessEventsFlagEE+0x32)[0x7f5e34c9ba02]
/usr/lib/libQtCore.so.4(_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE+0xdc)[0x7f5e34c9bdec]
/usr/lib/libQtGui.so.4(+0x25200b)[0x7f5e3555100b]
/usr/lib/libQtGui.so.4(_ZN5QDrag4execE6QFlagsIN2Qt10DropActionEES2+0x68)[0x7f5e354ccf78]
/usr/lib/libQtGui.so.4(_ZN17QAbstractItemView9startDragE6QFlagsIN2Qt10DropActionEE+0x166)[0x7f5e35a0f1d6]
/usr/lib/libQtGui.so.4(_ZN17QAbstractItemView14mouseMoveEventEP11QMouseEvent+0x32e)[0x7f5e35a0cb1e]
/usr/lib/libQtGui.so.4(_ZN7QWidget5eventEP6QEvent+0x61b)[0x7f5e3550ccab]
/usr/lib/libQtGui.so.4(_ZN6QFrame5eventEP6QEvent+0x26)[0x7f5e358d85e6]
/usr/lib/libQtGui.so.4(_ZN17QAbstractItemView13viewportEventEP6QEvent+0x3eb)[0x7f5e35a11a8b]
/usr/lib/libQtGui.so.4(_ZN9QTreeView13viewportEventEP6QEvent+0x135)[0x7f5e35a4fd65]
/usr/lib/libQtCore.so.4(_ZN23QCoreApplicationPrivate29sendThroughObjectEventFiltersEP7QObjectP6QEvent+0x87)[0x7f5e34c9c507]
/usr/lib/libQtGui.so.4(_ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent+0x7c)[0x7f5e354b6fac]
/usr/lib/libQtGui.so.4(_ZN12QApplication6notifyEP7QObjectP6QEvent+0x96e)[0x7f5e354bd30e]
/usr/lib/libQtCore.so.4(ZN16QCoreApplication14notifyInternalEP7QObjectP6QEvent+0x8c)[0x7f5e34c9ccdc]
/usr/lib/libQtGui.so.4(ZN19QApplicationPrivate14sendMouseEventEP7QWidgetP11QMouseEventS1_S1_PS1_R8QPointerIS0_Eb+0x19e)[0x7f5e354bbdbe]
/usr/lib/libQtGui.so.4(+0x240345)[0x7f5e3553f345]
/usr/lib/libQtGui.so.4(ZN12QApplication15x11ProcessEventEP7_XEvent+0x85c)[0x7f5e3553dc5c]
/usr/lib/libQtGui.so.4(+0x26b0e2)[0x7f5e3556a0e2]
/lib/libglib-2.0.so.0(g_main_context_dispatch+0x1f2)[0x7f5e31ce9342]
/lib/libglib-2.0.so.0(+0x442a8)[0x7f5e31ced2a8]
/lib/libglib-2.0.so.0(g_main_context_iteration+0x6c)[0x7f5e31ced45c] ======= Memory map: ========
00400000-0099c000 r-xp 00000000 08:05 22676995 /home/john/devel/GoldenCheetah/src/GoldenCheetah
00b9b000-00b9f000 r--p 0059b000 08:05 22676995 /home/john/devel/GoldenCheetah/src/GoldenCheetah
00b9f000-00ba4000 rw-p 0059f000 08:05 22676995 /home/john/devel/GoldenCheetah/src/GoldenCheetah
00ba4000-00ba7000 rw-p 00000000 00:00 0
00ebc000-0cfe4000 rw-p 00000000 00:00 0 [heap]
7f5e1671d000-7f5e1677d000 rw-s 00000000 00:04 9142302 /SYSV00000000 (deleted)
7f5e1677d000-7f5e16796000 r--p 00000000 08:05 27924485 /usr/share/fonts/truetype/ttf-gfs-didot/GFSDidotBold.otf
7f5e16796000-7f5e167b3000 r--p 00000000 08:05 27924452 /usr/share/fonts/truetype/ttf-gfs-artemisia/GFSArtemisiaBold.otf
7f5e167b3000-7f5e167fd000 r--p 00000000 08:05 27277102 /usr/share/fonts/truetype/ttf-dejavu/DejaVuSansMono-Bold.ttf
7f5e167fd000-7f5e16806000 r--p 00000000 08:05 27289532 /usr/share/fonts/type1/gsfonts/s050000l.pfb
7f5e16806000-7f5e1680c000 r--p 00000000 08:05 27676531 /usr/share/texmf/fonts/type1/public/lm/lmex10.pfb
7f5e1680c000-7f5e16b8f000 r--p 00000000 08:05 27282481 /usr/share/fonts/truetype/unfonts/UnBatang.ttf
7f5e16b8f000-7f5e16baa000 r--p 00000000 08:05 27677585 /usr/share/texmf/fonts/type1/public/tex-gyre/qagr.pfb
7f5e16baa000-7f5e16bc7000 r--p 00000000 08:05 27676527 /usr/share/texmf/fonts/type1/public/lm/lmcsc10.pfb
7f5e16bc7000-7f5e170b8000 r--p 00000000 08:05 27291142 /usr/share/fonts/truetype/wqy/wqy-microhei.ttc
7f5e170b8000-7f5e170d1000 r--p 00000000 08:05 27282355 /usr/share/fonts/truetype/ttf-indic-fonts-core/Kedage-n.ttf
7f5e170d1000-7f5e170ef000 r--p 00000000 08:05 27924517 /usr/share/fonts/truetype/ttf-gfs-neohellenic/GFSNeohellenic.otf
7f5e170ef000-7f5e17115000 r--p 00000000 08:05 27924451 /usr/share/fonts/truetype/ttf-gfs-artemisia/GFSArtemisia.otf
7f5e17115000-7f5e17132000 r--p 00000000 08:05 17956953 /usr/share/fonts/truetype/msttcorefonts/Webdings.ttf
7f5e17132000-7f5e17148000 r--p 00000000 08:05 27277528 /usr/share/fonts/truetype/thai/Sawasdee.ttf
7f5e17148000-7f5e171a1000 r--p 00000000 08:05 27923149 /usr/share/fonts/truetype/ttf-sil-gentium/GenR102.ttf
7f5e171a1000-7f5e171ee000 r--p 00000000 08:05 27264318 /usr/share/fonts/truetype/freefont/FreeMono.ttf
7f5e171ee000-7f5e1721a000 r--p 00000000 08:05 27263818 /usr/share/fonts/truetype/openoffice/opens.ttf
7f5e1721a000-7f5e1724a000 r--p 00000000 08:05 27282376 /usr/share/fonts/truetype/ttf-indic-fonts-core/Pothana2000.ttf
7f5e1724a000-7f5e17385000 r--p 00000000 08:05 27264326 /usr/share/fonts/truetype/freefont/FreeSerif.ttf
7f5e17385000-7f5e173a2000 r--p 00000000 08:05 17956935 /usr/share/fonts/truetype/msttcorefonts/Arial_Black.ttf
7f5e173a2000-7f5e173f3000 r--p 00000000 08:05 27277103 /usr/share/fonts/truetype/ttf-dejavu/DejaVuSerif.ttf
7f5e173f3000-7f5e17442000 r--p 00000000 08:05 27271989 /usr/share/fonts/truetype/ttf-dejavu/DejaVuSansMono.ttf
7f5e17442000-7f5e1748c000 r--p 00000000 08:05 17956941 /usr/share/fonts/truetype/msttcorefonts/Courier_New.ttf
7f5e1748c000-7f5e17a7f000 r--p 00000000 08:05 27291042 /usr/share/fonts/truetype/takao/TakaoPGothic.ttf
7f5e17a7f000-7f5e17add000 r--p 00000000 08:05 27282373 /usr/share/fonts/truetype/ttf-indic-fonts-core/Rachana_04.ttf
7f5e17add000-7f5e17af7000 r--p 00000000 08:05 27279078 /usr/share/fonts/truetype/thai/Norasi.ttf
7f5e17af7000-7f5e17b1e000 r--p 00000000 08:05 27282374 /usr/share/fonts/truetype/ttf-indic-fonts-core/utkal.ttf
7f5e17b1e000-7f5e17b33000 r--p 00000000 08:05 27271092 /usr/share/fonts/truetype/ttf-indic-fonts-core/Rekha.ttf
7f5e17b33000-7f5e17b45000 r--p 00000000 08:05 27271089 /usr/share/fonts/truetype/ttf-indic-fonts-core/gargi.ttf
7f5e17b45000-7f5e17b52000 r--p 00000000 08:05 27291120 /usr/share/fonts/truetype/ttf-kacst-one/KacstOne.ttf
7f5e17b52000-7f5e17bc3000 r--p 00000000 08:05 27264322 /usr/share/fonts/truetype/freefont/FreeSans.ttf
7f5e17bc3000-7f5e17c15000 r--p 00000000 08:05 27282372 /usr/share/fonts/truetype/ttf-indic-fonts-core/Meera_04.ttf
7f5e17c15000-7f5e17c26000 r--p 00000000 08:05 27282375 /usr/share/fonts/truetype/ttf-indic-fonts-core/lohit_ta.ttf
7f5e17c26000-7f5e17c2d000 r--p 00000000 08:05 27282477 /usr/share/fonts/truetype/ttf-punjabi-fonts/lohit_pa.ttf
7f5e17c2d000-7f5e17c41000 r--p 00000000 08:05 27271090 /usr/share/fonts/truetype/ttf-indic-fonts-core/lohit_hi.ttf
7f5e17c41000-7f5e17c55000 r--p 00000000 08:05 27271091 /usr/share/fonts/truetype/ttf-indic-fonts-core/lohit_gu.ttf
7f5e17c55000-7f5e17c78000 r--p 00000000 08:05 27271086 /usr/share/fonts/truetype/ttf-indic-fonts-core/lohit_bn.ttf
7f5e17c78000-7f5e17e94000 r--p 00000000 08:05 27282497 /usr/share/fonts/truetype/unfonts/UnDotum.ttfAborted
History
#1 Updated by Mark Liversedge almost 2 years ago

Status changed from New to Closed
% Done changed from 0 to 100
Applied in changeset commit:"3a801e27b52226a0d9f0b08aa5f02642c77cc63a".
#2 Updated by John Ehrlinger almost 2 years ago

FYI. My HomeWindow was not empty, and the crash persists after applying the git update.

It seems only related to the Ride Summary pages.
#3 Updated by Mark Liversedge almost 2 years ago

Status changed from Closed to Feedback
% Done changed from 100 to 50
I cannot recreate a crash on adding ride summary or the ride summary and metadata charts, for Linux or Mac anyway.

Which version of QT are you using?

Cheers,
Mark
#4 Updated by John Ehrlinger almost 2 years ago

Qt Version set to 4.7.0
Qt version 4.7.0
Ubuntu 10.10

It may be a user error. Either at compile or run time. I've had issues with the x86-64 versions in the past that have not shown on 32bit versions.

This is the latest console dump.

src/GoldenCheetah
Cannot open qollector_interpret program, available from http://opensource.quarq.us/qollector_interpret.
Bus::open: Can not get ibus-daemon's address.
IBusInputContext::createInputContext: no connection to ibus-daemon
glibc detected * src/GoldenCheetah: free(): invalid next size (fast): 0x00007fca5d8983a0 * ======= Backtrace: =========
/lib/libc.so.6(+0x774b6)[0x7fca68b6e4b6]
/lib/libc.so.6(cfree+0x73)[0x7fca68b74c83]
/usr/lib/libQtGui.so.4(ZN11QTextEngine13clearLineDataEv+0x3d)[0x7fca6a90ad3d]
/usr/lib/libQtGui.so.4(+0x47ac56)[0x7fca6a95ec56]
/usr/lib/libQtGui.so.4(+0x64f8a1)[0x7fca6ab338a1]
/usr/lib/libQtGui.so.4(_ZN9QTextEdit11resizeEventEP12QResizeEvent+0x3e)[0x7fca6ab33c8e]
/usr/lib/libQtGui.so.4(_ZN7QWidget5eventEP6QEvent+0x5d0)[0x7fca6a6f1c60]
/usr/lib/libQtGui.so.4(_ZN6QFrame5eventEP6QEvent+0x26)[0x7fca6aabd5e6]
/usr/lib/libQtCore.so.4(_ZN23QCoreApplicationPrivate29sendThroughObjectEventFiltersEP7QObjectP6QEvent+0x87)[0x7fca69e81507]
/usr/lib/libQtGui.so.4(_ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent+0x7c)[0x7fca6a69bfac]
/usr/lib/libQtGui.so.4(_ZN12QApplication6notifyEP7QObjectP6QEvent+0x14d)[0x7fca6a6a1aed]
/usr/lib/libQtCore.so.4(_ZN16QCoreApplication14notifyInternalEP7QObjectP6QEvent+0x8c)[0x7fca69e81cdc]
/usr/lib/libQtGui.so.4(_ZN14QWidgetPrivate30sendPendingMoveAndResizeEventsEbb+0x19b)[0x7fca6a6f0ccb]
/usr/lib/libQtGui.so.4(_ZN14QWidgetPrivate11show_helperEv+0x23)[0x7fca6a6f5e23]
/usr/lib/libQtGui.so.4(_ZN14QWidgetPrivate12showChildrenEb+0xb1)[0x7fca6a6f6221]
/usr/lib/libQtGui.so.4(_ZN14QWidgetPrivate11show_helperEv+0x3f)[0x7fca6a6f5e3f]
/usr/lib/libQtGui.so.4(_ZN14QWidgetPrivate12showChildrenEb+0xb1)[0x7fca6a6f6221]
/usr/lib/libQtGui.so.4(_ZN14QWidgetPrivate11show_helperEv+0x3f)[0x7fca6a6f5e3f]
/usr/lib/libQtGui.so.4(_ZN7QWidget10setVisibleEb+0x1ba)[0x7fca6a6f769a]
src/GoldenCheetah[0x45b010]
src/GoldenCheetah[0x538b9e]
/usr/lib/libQtGui.so.4(_ZN7QWidget5eventEP6QEvent+0x98c)[0x7fca6a6f201c]
/usr/lib/libQtGui.so.4(_ZN6QFrame5eventEP6QEvent+0x26)[0x7fca6aabd5e6]
/usr/lib/libQtGui.so.4(_ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent+0xac)[0x7fca6a69bfdc]
/usr/lib/libQtGui.so.4(_ZN12QApplication6notifyEP7QObjectP6QEvent+0x3e2)[0x7fca6a6a1d82]
/usr/lib/libQtCore.so.4(_ZN16QCoreApplication14notifyInternalEP7QObjectP6QEvent+0x8c)[0x7fca69e81cdc]
/usr/lib/libQtGui.so.4(+0x24ce8d)[0x7fca6a730e8d]
/usr/lib/libQtGui.so.4(+0x251763)[0x7fca6a735763]
/usr/lib/libQtGui.so.4(+0x251928)[0x7fca6a735928]
/usr/lib/libQtCore.so.4(_ZN23QCoreApplicationPrivate34sendThroughApplicationEventFiltersEP7QObjectP6QEvent+0x9b)[0x7fca69e815cb]
/usr/lib/libQtGui.so.4(_ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent+0x26)[0x7fca6a69bf56]
/usr/lib/libQtGui.so.4(_ZN12QApplication6notifyEP7QObjectP6QEvent+0x96e)[0x7fca6a6a230e]
/usr/lib/libQtCore.so.4(_ZN16QCoreApplication14notifyInternalEP7QObjectP6QEvent+0x8c)[0x7fca69e81cdc]
/usr/lib/libQtGui.so.4(_ZN19QApplicationPrivate14sendMouseEventEP7QWidgetP11QMouseEventS1_S1_PS1_R8QPointerIS0_Eb+0x19e)[0x7fca6a6a0dbe]
/usr/lib/libQtGui.so.4(+0x240345)[0x7fca6a724345]
/usr/lib/libQtGui.so.4(_ZN12QApplication15x11ProcessEventEP7_XEvent+0x85c)[0x7fca6a722c5c]
/usr/lib/libQtGui.so.4(+0x26b0e2)[0x7fca6a74f0e2]
/lib/libglib-2.0.so.0(g_main_context_dispatch+0x1f2)[0x7fca66ece342]
/lib/libglib-2.0.so.0(+0x442a8)[0x7fca66ed22a8]
/lib/libglib-2.0.so.0(g_main_context_iteration+0x6c)[0x7fca66ed245c]
/usr/lib/libQtCore.so.4(_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE+0x73)[0x7fca69eae193]
/usr/lib/libQtGui.so.4(+0x26aa4e)[0x7fca6a74ea4e]
/usr/lib/libQtCore.so.4(_ZN10QEventLoop13processEventsE6QFlagsINS_17ProcessEventsFlagEE+0x32)[0x7fca69e80a02]
/usr/lib/libQtCore.so.4(_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE+0xdc)[0x7fca69e80dec]
/usr/lib/libQtGui.so.4(+0x25200b)[0x7fca6a73600b]
/usr/lib/libQtGui.so.4(_ZN5QDrag4execE6QFlagsIN2Qt10DropActionEES2+0x68)[0x7fca6a6b1f78]
/usr/lib/libQtGui.so.4(_ZN17QAbstractItemView9startDragE6QFlagsIN2Qt10DropActionEE+0x166)[0x7fca6abf41d6]
/usr/lib/libQtGui.so.4(_ZN17QAbstractItemView14mouseMoveEventEP11QMouseEvent+0x32e)[0x7fca6abf1b1e]
/usr/lib/libQtGui.so.4(_ZN7QWidget5eventEP6QEvent+0x61b)[0x7fca6a6f1cab]
/usr/lib/libQtGui.so.4(_ZN6QFrame5eventEP6QEvent+0x26)[0x7fca6aabd5e6]
/usr/lib/libQtGui.so.4(_ZN17QAbstractItemView13viewportEventEP6QEvent+0x3eb)[0x7fca6abf6a8b]
/usr/lib/libQtGui.so.4(_ZN9QTreeView13viewportEventEP6QEvent+0x135)[0x7fca6ac34d65]
/usr/lib/libQtCore.so.4(_ZN23QCoreApplicationPrivate29sendThroughObjectEventFiltersEP7QObjectP6QEvent+0x87)[0x7fca69e81507]
/usr/lib/libQtGui.so.4(_ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent+0x7c)[0x7fca6a69bfac]
/usr/lib/libQtGui.so.4(_ZN12QApplication6notifyEP7QObjectP6QEvent+0x96e)[0x7fca6a6a230e]
/usr/lib/libQtCore.so.4(ZN16QCoreApplication14notifyInternalEP7QObjectP6QEvent+0x8c)[0x7fca69e81cdc]
/usr/lib/libQtGui.so.4(ZN19QApplicationPrivate14sendMouseEventEP7QWidgetP11QMouseEventS1_S1_PS1_R8QPointerIS0_Eb+0x19e)[0x7fca6a6a0dbe]
/usr/lib/libQtGui.so.4(+0x240345)[0x7fca6a724345]
/usr/lib/libQtGui.so.4(ZN12QApplication15x11ProcessEventEP7_XEvent+0x85c)[0x7fca6a722c5c]
/usr/lib/libQtGui.so.4(+0x26b0e2)[0x7fca6a74f0e2]
/lib/libglib-2.0.so.0(g_main_context_dispatch+0x1f2)[0x7fca66ece342]
/lib/libglib-2.0.so.0(+0x442a8)[0x7fca66ed22a8]
/lib/libglib-2.0.so.0(g_main_context_iteration+0x6c)[0x7fca66ed245c] ======= Memory map: ========
00400000-0099c000 r-xp 00000000 08:05 22676995 /home/john/devel/GoldenCheetah/src/GoldenCheetah
00b9b000-00b9f000 r--p 0059b000 08:05 22676995 /home/john/devel/GoldenCheetah/src/GoldenCheetah
00b9f000-00ba4000 rw-p 0059f000 08:05 22676995 /home/john/devel/GoldenCheetah/src/GoldenCheetah
00ba4000-00ba7000 rw-p 00000000 00:00 0
00bd0000-01314000 rw-p 00000000 00:00 0 [heap]
7fca4b43e000-7fca4b450000 r--p 00000000 08:05 27289567 /usr/share/fonts/type1/gsfonts/n019004l.pfb
7fca4b450000-7fca4b4b0000 rw-s 00000000 00:04 12779545 /SYSV00000000 (deleted)
7fca4b4b0000-7fca4b4c9000 r--p 00000000 08:05 27924485 /usr/share/fonts/truetype/ttf-gfs-didot/GFSDidotBold.otf
7fca4b4c9000-7fca4b4e6000 r--p 00000000 08:05 27924452 /usr/share/fonts/truetype/ttf-gfs-artemisia/GFSArtemisiaBold.otf
7fca4b4e6000-7fca4b530000 r--p 00000000 08:05 27277102 /usr/share/fonts/truetype/ttf-dejavu/DejaVuSansMono-Bold.ttf
7fca4b530000-7fca4b539000 r--p 00000000 08:05 27289532 /usr/share/fonts/type1/gsfonts/s050000l.pfb
7fca4b539000-7fca4b53f000 r--p 00000000 08:05 27676531 /usr/share/texmf/fonts/type1/public/lm/lmex10.pfb
7fca4b53f000-7fca4b8c2000 r--p 00000000 08:05 27282481 /usr/share/fonts/truetype/unfonts/UnBatang.ttf
7fca4b8c2000-7fca4b8dd000 r--p 00000000 08:05 27677585 /usr/share/texmf/fonts/type1/public/tex-gyre/qagr.pfb
7fca4b8dd000-7fca4b8fa000 r--p 00000000 08:05 27676527 /usr/share/texmf/fonts/type1/public/lm/lmcsc10.pfb
7fca4b8fa000-7fca4bdeb000 r--p 00000000 08:05 27291142 /usr/share/fonts/truetype/wqy/wqy-microhei.ttc
7fca4bdeb000-7fca4be04000 r--p 00000000 08:05 27282355 /usr/share/fonts/truetype/ttf-indic-fonts-core/Kedage-n.ttf
7fca4be04000-7fca4be22000 r--p 00000000 08:05 27924517 /usr/share/fonts/truetype/ttf-gfs-neohellenic/GFSNeohellenic.otf
7fca4be22000-7fca4be48000 r--p 00000000 08:05 27924451 /usr/share/fonts/truetype/ttf-gfs-artemisia/GFSArtemisia.otf
7fca4be48000-7fca4be65000 r--p 00000000 08:05 17956953 /usr/share/fonts/truetype/msttcorefonts/Webdings.ttf
7fca4be65000-7fca4be7b000 r--p 00000000 08:05 27277528 /usr/share/fonts/truetype/thai/Sawasdee.ttf
7fca4be7b000-7fca4bed4000 r--p 00000000 08:05 27923149 /usr/share/fonts/truetype/ttf-sil-gentium/GenR102.ttf
7fca4bed4000-7fca4bf21000 r--p 00000000 08:05 27264318 /usr/share/fonts/truetype/freefont/FreeMono.ttf
7fca4bf21000-7fca4bf4d000 r--p 00000000 08:05 27263818 /usr/share/fonts/truetype/openoffice/opens.ttf
7fca4bf4d000-7fca4bf7d000 r--p 00000000 08:05 27282376 /usr/share/fonts/truetype/ttf-indic-fonts-core/Pothana2000.ttf
7fca4bf7d000-7fca4c0b8000 r--p 00000000 08:05 27264326 /usr/share/fonts/truetype/freefont/FreeSerif.ttf
7fca4c0b8000-7fca4c0d5000 r--p 00000000 08:05 17956935 /usr/share/fonts/truetype/msttcorefonts/Arial_Black.ttf
7fca4c0d5000-7fca4c126000 r--p 00000000 08:05 27277103 /usr/share/fonts/truetype/ttf-dejavu/DejaVuSerif.ttfAborted
#5 Updated by John Ehrlinger almost 2 years ago

This seems to be a 64bit linux compile issue only. I was able to build a 32bit and it works as expected.
#6 Updated by Mark Liversedge over 1 year ago

I have tried to recreate on Linux x64, using latest head (20e1ba6) with QT 4.7 (sdk 1.1) and could not recreate this issue.

Any chance of getting a stack trace from gdb ? (bt full)
#7 Updated by John Ehrlinger over 1 year ago

You can leave this as closed, it's pretty old and not really valid now.

I have found that instabilities are sometimes corrected by doing a clean build

make clean;
make

Not sure why that should matter, unless source code dependencies are not entirely correct though. I don't have specifics on this, but I recall that this problem dissappeared when I did the clean build.
#8 Updated by Mark Liversedge over 1 year ago

It is a real bug.

I think it is a "sizeof()" issue. If you run a 32-bit binary on a 64-bit host you get problems.

Am trying to fix it now.
#9 Updated by John Ehrlinger over 1 year ago

Well, I don't run 32bit code on 64bit machines, but I do run the same athlete data on both architectures. The builds are separate, but the data is shared. Would that matter?
#10 Updated by Mark Liversedge over 1 year ago

Yes - i should have been more explicit in previous comments.

I'm looking at how compatible the 'derived' file formats are -- i.e. we cache data/settings in local endian and local datatypes. This potentially applies to;
metric database
ride file cache (cpx)
LTM settings on home window
There may be others, am currently looking at that. Not sure if it is an issue for all the above, doing desk check of the code.
#11 Updated by Mark Liversedge over 1 year ago

Status changed from Feedback to Closed
Target version set to 3.0
I fixed the file format for the cpx in the end. :)

Ale's patch for v2 showed the way, but v3 needs to adopt something similar.

This is a significant error and will require considerable effort.

1. update codebase to use tr for all constant strings we want translated
2. bring translations in from 2.1
3. adjust code to allow metric translation
4. adjust code to allow metadata special field translation
5. Get translating!!

I figure this can be classified as either a bug (oversight) or a feature request.

When adding columns to the Activity history, we have 96 options. Unless I'm missing this (in which case, it must not be obvious) we can not sort on the exercise time... we have Date, distance and duration but not "time of day" or "start time".

Quite often I get an error saying 'lap 1 has invalid start time' when importing .fit files from my Edge 500/800. This disables interval data for the affected lap/interval.

Two sample files are attached. Both V2.1 and 3.0 development build share the behaviour.

2012_05_16_09_23_54.fit - 1-lap file with invalid start time (82.9 kB) Juha Tiihonen, 05/30/2012 02:34 pm
2012_05_06_10_15_49.fit - 4-lap file with 1 lap that is about zero length - accidental two consequtive lap presses (372.5 kB) Juha Tiihonen, 05/30/2012 02:34 pm
Add
Related issues

History
#1 Updated by Gareth Coco 4 months ago

Tracker changed from Bug to Feature
Subject changed from Garmin Edge 800 .fit import reports 'lap 1 has invalid start time' to Garmin Edge .fit import reports 'lap 1 has invalid start time' - Calculate actual start time
Priority changed from Normal to High
Target version set to 3.0

I have changed this into a feature request as it is something that people often have issues with.

If you have a Garmin GPS device that creates .fit files, if you start recording before the unit has time to sync to the GPS then the time of the PS unit may be updated to a GPS synced time. If the time that the unit had before syncing was actually ahead of real time (From GPS) then GC will error with the 'lap 1 has an invalid start time.'

It would be good if GC saw this happening that it would recalculate the actual start time based on the new time and how long the interval had been recording before the time change.

Update Watch Copy Delete

Hi everyone. I tried importing the file attached that has come from an athlete who has recently gotten an SRM. Don't know if it's new or old, but I get the following error message when opening the file. Once I've tried to open the file, the same error message comes up and I have to rename the athlete's folder in my GC folder to get it to open again. It could be that it's a problem with this person's computer or something in transmission, but I have no idea.

email me at mike_at_podiumbound_dot_ca if I can be any help.

Mike

A210711.srm (113.1 kB) Mike Patton, 22/07/2011 12:53 pm
A210711-fixed.srm (113.1 kB) Rainer Clasen, 22/07/2011 03:27 pm
History
#1 Updated by Rainer Clasen over 1 year ago

File A210711-fixed.srm added
Status changed from New to Resolved
Assignee set to Rainer Clasen
% Done changed from 0 to 100
Hi Mike,

this file isn't what I'd call bad ... it's just quite unusual. Actually it's the first of this kind.

It's a perfectly fine SRM7 file ... but it lacks the "block" entries as with SRM5 files. The official 2.0 release won't handle this, but this was already addressed in Issue #208 / 57b9e28.

I'm attaching a "fixed" version of this file - in case you don't want to play with a "development version".

Rainer
#2 Updated by Mark Liversedge over 1 year ago

Status changed from Resolved to Closed
Target version set to 3.0
Fixed in v3.

When importing a json ride file in v3 GC will crash after RideItem::freeMemory is called. This may also occur for .gc files.

Associated revisions

Revision 4c6d926
Added by Mark Liversedge over 1 year ago

Fix First Ride File Import Crashes

When you import the very first ride into V3 it will cause
a SEGV crash when attempting to freeMemory. This is because
the first entry added to a list does not cause any selection
to be made.

This means that the very first time someone tries to use GC
version 3 it will crash! Not the best of starts.

This bug was previously reported as being related to importing
json ride files, it occurs for ANY ride file type.

Fixes #328.

History
#1 Updated by Mark Liversedge over 1 year ago

Status changed from New to Closed
% Done changed from 0 to 100
Applied in changeset 4c6d926.

The timer that changes the load during an erg file is not accurate.

For example, while riding a 3x10 erg file, I notice that each 10 minute interval lasts 10:08, and each 5 minute rest interval lasts 5:04 on my machine.

0001-fix-realtime-mode-load-timer-and-lcd-sig.-digit-disp.patch - patch for #262 and #263 (4.7 kB) Eric Brandt, 12/02/2011 07:56 am
Associated revisions

Revision 6815fe0
Added by Eric Brandt over 1 year ago

fix realtime mode load timer and lcd sig. digit display issues

The load timer was simply being accumulated with each firing
of the timer. This resulted in inaccuracies. The fix is to
accumulate using a timer that measures the duration between loadUpdate
calls.

The speed, average speed, gradient, and distance LCDs ought to always
display 1 significant digit to avoid bouncing. This is now fixed.

This commit fixes #262 and fixes #263.

History
#1 Updated by Eric Brandt over 1 year ago

File 0001-fix-realtime-mode-load-timer-and-lcd-sig.-digit-disp.patch added
Patch Attached changed from No to Yes
#2 Updated by Eric Brandt over 1 year ago

Status changed from New to Closed
% Done changed from 90 to 100
Applied in changeset 6815fe0.

The "device name" field in the ride summary is currently populated with a mix of actual devices and file types. Historically the file types and devices were linked, but we now have several file formats that support many different physical devices (e.g. .fit files can come from several Garmin devices).

I propose that we move to having two fields
Device: Specify the physical device type if possible
File Format: Define the file format (FIT, TCX, GC, Powertap raw, cycleops .bin...)

Goldencheetah crashes whenever I select "Critical Power Plot" tab. I use two different MAC (Mac Book Pro and Mac Pro both with OSX 10.6.4) and crash happens only with Mac Pro.
I am using same data from Polar hrm files. I cant figure out what is reason for these crashes; display adapter?

Goldencheetah_crashreportfile.txt - Crashreport file (29.9 kB) Pertti Sirén, 24/07/2010 09:33 am
10050202.hrm (112.9 kB) Pertti Sirén, 24/07/2010 11:08 am
10071001.hrm (36.9 kB) Pertti Sirén, 24/07/2010 11:08 am
History
#1 Updated by Justin Knotzke over 2 years ago

Would you happen to have the file is is trying to process that crashes GC ?

If so, could you please add it to the Bug Report ? Thanks
#2 Updated by Pertti Sirén over 2 years ago

File 10050202.hrm added
File 10071001.hrm added
Added some HRM files, all of my HRM files will crash golden cheetah on my Mac Pro.
#3 Updated by Mark Liversedge over 1 year ago

Status changed from New to Closed
Target version set to 3.0
Patch Attached set to No
Tried files with the new 3.0 cpx based CP plots and its fine.

The number of significant digits diplayed for the speed, average speed, gradient, and distance LCD's varies is not consistent. For example, a speed of 19.1 is shown as "19.1", but a speed of 19.0 is shown as "19". These four fields should always format to show 1 significant digit so that the display doesn't 'bounce' between two and three digits being displayed as the rider hovers around, say, 20.0 mph.

0001-fix-realtime-mode-load-timer-and-lcd-sig.-digit-disp.patch - patch for #262 and #263 (4.7 kB) Eric Brandt, 12/02/2011 07:57 am
Associated revisions

Revision 6815fe0
Added by Eric Brandt over 1 year ago

fix realtime mode load timer and lcd sig. digit display issues

The load timer was simply being accumulated with each firing
of the timer. This resulted in inaccuracies. The fix is to
accumulate using a timer that measures the duration between loadUpdate
calls.

The speed, average speed, gradient, and distance LCDs ought to always
display 1 significant digit to avoid bouncing. This is now fixed.

This commit fixes #262 and fixes #263.

History
#1 Updated by Eric Brandt over 1 year ago

File 0001-fix-realtime-mode-load-timer-and-lcd-sig.-digit-disp.patch added
Patch Attached changed from No to Yes
#2 Updated by Greg Lonnon over 1 year ago

Eric,

Are you sure your patch is based on the most recent V3. The avg speed and speed LCD issues were fixed.

https://github.com/srhea/GoldenCheetah/commit/dff06db88d80b8d709c2dfc9d4685315a489b209

Greg
#3 Updated by Eric Brandt over 1 year ago

Status changed from New to Closed
% Done changed from 90 to 100
Applied in changeset 6815fe0.