Edit/split one dive computer in a merged dive

156 views

mac-issues

Skip to first unread message

Celia Marlowe

unread,

Mar 30, 2019, 2:33:42 AM3/30/19

to Subsurface Divelog

Subsurface 4.8.4-347

MacOS Mojave 10.14.3

Multiple dive computers

Hi,

I'm not sure whether to post this as one or two questions as they are linked but possibly only in my usage rather than technically. I can make separate posts if it makes more sense.

1) Is it possible to extract one (or more) dive computer profiles from an automatically (or manually) merged dive - i.e. make stand alone? I've dives that have ended up merged into dives they shouldn't be in. I couldn't find a way to edit the time for just one computer to make it a standalone dive, or find another way to separate them, but I wanted to verify that...

I can of course address this by reimporting everything, or separate dive logs etc but hoped there was a quicker/easier way.

2) Related to this is the split function in certain circumstances.

The scenario:

A dive with multiple ascents from around 17m to near surface ( less than 1 metre so from my understanding the split function should work). N.B This is research not my usual diving practice!

Subsurface has a merged dive across multiple dive computers. Some computer models register all three ascents as one dive, and others separated. So I end up with a merged dive which for some computers has three ascents, and others has two, with the third ascent as a separate dive. The split function is not working on dives like this (seems to work on dives where there is only one dive computer). Ultimately I want to split into single descent/ascents.

I'd like to find a ways to work with individual computers profiles and/or split in these circumstances if possible.

Many thanks,

Linus Torvalds

unread,

Mar 30, 2019, 3:12:14 PM3/30/19

to subsurfac...@googlegroups.com, Berthold Stoeger

On Fri, Mar 29, 2019 at 11:33 PM 'Celia Marlowe' via Subsurface
Divelog <subsurfac...@googlegroups.com> wrote:
>
> 1) Is it possible to extract one (or more) dive computer profiles from
> an automatically (or manually) merged dive - i.e. make stand alone?
> I've dives that have ended up merged into dives they shouldn't be
> in. I couldn't find a way to edit the time for just one computer to
> make it a standalone dive, or find another way to separate them,
> but I wanted to verify that...

Right now we don't have an interface to do that.

If you want to work with individual dive computers, right now you just
have to disable the merging at import time (for example, bu checking
the "import into new trip" thing, which keeps all the newly imported
dives nicely separate from everything else).

> I can of course address this by reimporting everything, or separate dive logs etc but hoped there was a quicker/easier way.

We probably *should* have a way to do it.

We have a way to delete the current dive computer (and to re-order the
list), but we don't have a way to split the current dive computer into
a new dive. Hmm.

> 2) Related to this is the split function in certain circumstances.
>
> The scenario:
>
> A dive with multiple ascents from around 17m to near surface ( less
> than 1 metre so from my understanding the split function should
> work). N.B This is research not my usual diving practice!
>
> Subsurface has a merged dive across multiple dive computers. Some
> computer models register all three ascents as one dive, and others
> separated. So I end up with a merged dive which for some computers
> has three ascents, and others has two, with the third ascent as a
> separate dive. The split function is not working on dives like this
> (seems to work on dives where there is only one dive computer).
> Ultimately I want to split into single descent/ascents.
>
> I'd like to find a ways to work with individual computers profiles
> and/or split in these circumstances if possible.

Yes, the above would be possible if we just had a "split current dive
computer into a dive of its own", and then you can further split that
dive computer into multiple dives, and then pick the dives to be
re-merged.

Let me look at how nasty it would be. I think Berthold knows that code
better than I do by now (with all his cleanups and fixes to make undo
possible. But maybe I can at least write something that he can then
fix up to actually work right.

Linus

Linus Torvalds

unread,

Mar 30, 2019, 3:35:32 PM3/30/19

to subsurfac...@googlegroups.com, Berthold Stoeger

On Sat, Mar 30, 2019 at 12:11 PM Linus Torvalds
<torv...@linux-foundation.org> wrote:
>
> Let me look at how nasty it would be. I think Berthold knows that code
> better than I do by now (with all his cleanups and fixes to make undo
> possible. But maybe I can at least write something that he can then
> fix up to actually work right.

So the attached patch worked for the one simple test I did on it. It
adds a "split this dive computer into a dive of its own" menu entry
when mousing over the dive computer name, and you can actually choose
it and it does something that mostly works.

It re-uses a lot of our existing infrastructure, which is why the
patch isn't actually all that big. That part is nice.

BUT! It's almost certainly complete garbage. In particular, it doesn't
participate in the nice undoi/redo logic that the real dive list
operations participate in (but neither does the dive computer delete
stuff seem to do).

But it also doesn't insert the dive in the right place, it just
inserts the new dive at the end of the dive list.

So this is not useful as-is, but I know for a fact that I won't get
the undo/redo right, so I think I'll just post this patch in the hope
that Berthold goes "yeah, I see what you're trying to do, and you're
doing it all wrong, here's the *real* patch".

Berthold?

Linus

patch.diff

Linus Torvalds

unread,

Mar 30, 2019, 3:55:44 PM3/30/19

to Berthold Stoeger, subsurfac...@googlegroups.com

Test data sent in private.

Linus

On Sat, Mar 30, 2019 at 12:49 PM Berthold Stoeger
<bsto...@mail.tuwien.ac.at> wrote:
>
> I will have a go at it tomorrow. Could someone send me a test file?

Celia Marlowe

unread,

Apr 5, 2019, 2:48:20 AM4/5/19

to Subsurface Divelog

Hi both, I wondered how this was looking? I don't meant to sound like I'm chasing, just if it's something that is looking easy to solve in the next few days I'll wait for a bit, otherwise I'll crack on with reimporting everything. Many thanks! Celia

Dirk Hohndel

unread,

Apr 5, 2019, 10:15:57 AM4/5/19

to 'Celia Marlowe' via Subsurface Divelog

The code has landed in our development line, but won't make it into a public release until Subsurface 4.9.

What OS are you running? I could likely make a test binary available for you...

/D

--
From my phone

Celia Marlowe

unread,

Apr 7, 2019, 6:47:10 AM4/7/19

to Subsurface Divelog

I'm on macOS Mojave 10.14.3 - it would be amazing if you could! Thanks,C

Dirk Hohndel

unread,

Apr 10, 2019, 12:07:33 PM4/10/19

to 'Celia Marlowe' via Subsurface Divelog

Sorry this took a couple of days. I'm traveling.

Here's a DMG of something that is TRULY work in progress - the very
leading edge of our development. So there is a certain risk that using
this might have unintended side effects. I'm not aware of anything that
would break, but it's possible.

https://subsurface-divelog.org/downloads/test/Subsurface-4.8.4-453-g20e28ee4dcb8.dmg

Thanks

/D

On Sun, Apr 07, 2019 at 03:47:10AM -0700, 'Celia Marlowe' via Subsurface Divelog wrote:
> I'm on macOS Mojave 10.14.3 - it would be amazing if you could! Thanks,C
>
> On Friday, April 5, 2019 at 4:15:57 PM UTC+2, Dirk wrote:
> >
> > The code has landed in our development line, but won't make it into a
> > public release until Subsurface 4.9.
> >
> > What OS are you running? I could likely make a test binary available for
> > you...
> >
> > /D
> >
> > On April 4, 2019 11:48:19 PM PDT, 'Celia Marlowe' via Subsurface Divelog <

Celia Marlowe

unread,

Apr 11, 2019, 4:07:55 AM4/11/19

to Subsurface Divelog

Thanks Dirk,

Hugely appreciated! I've had a very brief play for the last hour or so. As I've mentioned before, I completely appreciate that I'm a) trying to use this in a way that is really out of main scope, and b) I'm sharing in the hope the issues I've seen might be helpful rather than anything, as I'm aware is work in progress, so you may well be aware of them already. I've attached a Subsurface file with an example dive that is exhibiting the issues below, but if I can help in any way, then please let me know. My coding skills aren't going to be sufficient to help on that front, but I'd like to give something back to the community if I can.

N.B The issue with changing the date not working correctly seems to be back in this version.

The split this dive computer into a dive of it's own is working great, thanks!

The split selected dive function isn't playing ball at all.

1) Split selected dives from the dive list more often that not crashes Subsurface (just closes down completely) for dives with both multiple computers and a single computer.

- shuts down for dives where there are more than two ascents.

- shuts down dives with single dive computer and two ascents

- when it doesn't shut down (I'm haven't narrowed down the differentiating factors, whether it's particular dives I have that it is complaining about), if there is just one dive computer in the dive, it seems to split a two ascent dive correctly.

- in a two ascent dive with multiple dive computers, the first computer seems to split correctly, but later computers seem to have a weird profile (see next comment for more detail)

- correctly splits the third ascent from a three ascent dive where there are multiple dive computers in the same dive, the third dive now split into a single dive seems correct across all dive computers. This leaves us with a two ascent dive - the first computer has the two descent/ascents correct but subsequent computers have a strange single dive profile which doesn't seem to bear resemblance to the real profile. This appears to be a consistent incorrect profile across different tests/dives/dive computers if that makes sense.

3) Split dive into two from the hover menu in the profile area is not separating into different descent/ascents for the same dives as above, but splitting in odd ways, i.e not into full dives, but at random depths. I haven't looked into this in more depth, I'm not sure what the expected behaviour is, whether it is the same as split selected dives.

I'll revert back to previous version (although will be sad to lose the split computer into separate dive function!) for now. I don't want to impose on your development plans or expect you to focus on this over other things you're working on, but it would be great to have a vague idea of when the next official release might be?

Many thanks as usual,

Celia

narrow_test_split.ssrf

Linus Torvalds

unread,

Apr 13, 2019, 12:38:29 PM4/13/19

to subsurfac...@googlegroups.com

On Thu, Apr 11, 2019 at 1:08 AM 'Celia Marlowe' via Subsurface Divelog
<subsurfac...@googlegroups.com> wrote:
>
> The split selected dive function isn't playing ball at all.

Hmm. It doesn't get used very often most of the time, so I'm not
entirely shocked.

That said, I tried to reproduce it here, to fix it, and I don't see
the problem. I do find your test data very amusing though: 24 dive
computers on one dive seems excessive even by *our* standards ;)

I did notice that if you split the dive at a point that many dive
computers don't even have (because they disagree about how long the
dive is), you get some odd behavior, but it didn't crash for me, and
even running it under valgrind (to find bad memory accesses) didn't
show anything.

I also note that I think I've mostly done the "split dives" only with
a single dive computer. With multiple dive computers, it gets a bit
confusing, since trying to split at the same point in the dive then
splits the dive computers slightly differently (because they all have
slightly different notiones of when the dive started).

So it's possible that we should limit the "split dive at XYZ" to just
work for the single-computer case, but you say that crashes for you
too, so..

I'll see about fixing the thing I did notice, but if you could
describe exactly what you did with that test ssrf file you posted that
caused problems, I'd really like to reproduce the crash...

Or maybe the crash was from some other data set, and the one you
posted was just the successful "split off one dive computer" example
and doesn't show the issue?

Linus

Celia Marlowe

unread,

Apr 13, 2019, 1:13:23 PM4/13/19

to Subsurface Divelog

Thanks so much for your reply Linus, I'm always hesitant to post for exactly that reason. I have 28 computers in my research... and am very aware it's kind of stretching things to ask for features to cater to that! The ability to separate dive computers out has been an absolute godsend, thank you.

In the meantime, I've used the new version to split dive computers out into separate dives, then reverted to the previous version to merge and split what I can, which mostly works. I *think* I was being a twit, and the instances when it wouldn't split was when a dive computer hadn't registered as getting close enough to the surface so wasn't hitting the cut level as it has worked for me now on the others that I've just tried.

I've tried splitting single computer dives again on narrow_test_split.ssrf to double check. It does give me the split issues still. If I try to split the dive with the single Mares computer, Subsurface instantly closes and I get the 'Subsurface quit unexpectedly report to Apple or ignore' pop up. I've tried taking a different dive computer into it's own dive and splitting that, same thing happens. Same on the multiple dive computer dive. It occurs to me that I've just been installing over the top of the older version, should I be uninstalling in a more thorough way first somehow and then installing?

I can understand the difficulties of splitting multiple dive computer dives, I'm quite happy to split them all individually and then merge again later!

Best, Celia

Linus Torvalds

unread,

Apr 13, 2019, 1:35:22 PM4/13/19

to subsurfac...@googlegroups.com

On Sat, Apr 13, 2019 at 10:13 AM 'Celia Marlowe' via Subsurface
Divelog <subsurfac...@googlegroups.com> wrote:
>
> I have 28 computers in my research... and am very aware it's kind of stretching things to ask for features to cater to that!

Oh, that part is lovely. Most people dive with just one, so getting
more testing of the multi-computer case is always good. And the more,
the merrier.

> I've tried splitting single computer dives again on
> narrow_test_split.ssrf to double check. It does give me the split
> issues still. If I try to split the dive with the single Mares
> computer, Subsurface instantly closes and I get the 'Subsurface quit
> unexpectedly report to Apple or ignore' pop up. I've tried taking a
> different dive computer into it's own dive and splitting that, same
> thing happens. Same on the multiple dive computer dive. It occurs to
> me that I've just been installing over the top of the older version,
> should I be uninstalling in a more thorough way first somehow and then
> installing?

That really shouldn't be a problem.

It's more likely that this is just some difference between our setups.
I'm not using the exact same version you are, and I'm running on
Linux, not OS X.

I just wanted to confirm what you did - it sounds like you're not
doing anything odd, and it just crashes for you for even the simple
case. I was thinking that maybe you did something else first to
trigger the problem.

I'll look more into it.

> I can understand the difficulties of splitting multiple dive computer dives, I'm quite happy to split them all individually and then merge again later!

We may make that the preferred model, just because otherwise we'd
either get odd splits (a time offset that is at the surface for one
dive computer might not be at the surface for another), or we'd have
to try to do some magical (and likely very complex and fragile) "try
to match the dive offset on one dive computer with the dive offset on
another".

But I'll try to figure out the crash first. Since an older version
works for you, it's clearly something introduced recently, and it
might just be that the code I was testing (which was my original
simplistic "split dive computer into dive of its own") doesn't show
the problem because we've had other things go on lately too..

Linus

Dirk Hohndel

unread,

Apr 13, 2019, 1:43:15 PM4/13/19

to 'Celia Marlowe' via Subsurface Divelog

When you get that report screen, can you open the report and copy all of this in a post here. It will contain a stack trace that should help us figure out what's wrong...

/D

--
From my phone

Linus Torvalds

unread,

Apr 13, 2019, 5:56:42 PM4/13/19

to subsurfac...@googlegroups.com

On Sat, Apr 13, 2019 at 10:43 AM Dirk Hohndel <di...@hohndel.org> wrote:
>
> When you get that report screen, can you open the report and copy all of this in a post here. It will contain a stack trace that should help us figure out what's wrong...

Yeah, that would be lovely. I've tried to repro it with the current
sources (rather than my hacked-up ones from a couple of weeks ago),
and am still failing to see the problem, even with valgrind.

Could easily be some library difference or other.

That said, I'm still not testing exactly the same thing as Dirk
uploaded, which apparently has some local patch in it. At least his
dmg upload had version hash "4.8.4-453-g20e28ee4dcb8", which isn't
something I see in the mainline repo (I'm on v4.8.4-476-g5966a74ae,
and I don't have that 20e28ee commit at all). I suspect Dirk had some
temporary thing in his tree when he was building it.

I don't see how that could possibly impact dive splitting, though. Dirk?

Linus

Celia Marlowe

unread,

Apr 14, 2019, 3:30:29 AM4/14/19

to Subsurface Divelog

Here you go:

Process: Subsurface [9845]

Path: /Applications/Subsurface.app/Contents/MacOS/Subsurface

Identifier: org.subsurface-divelog

Version: 4.8.4-453-g20e28ee4dcb8 (4.8.4-453-g20e28ee4dcb8)

Code Type: X86-64 (Native)

Parent Process: ??? [1]

Responsible: Subsurface [9845]

User ID: 502

Date/Time: 2019-04-14 09:28:30.266 +0200

OS Version: Mac OS X 10.14.3 (18D109)

Report Version: 12

Anonymous UUID: 4F7B5434-99D4-46C9-E214-FA0989EC7187

Sleep/Wake UUID: F645ACAD-1E2F-4440-9D57-08B241AA11C2

Time Awake Since Boot: 66000 seconds

Time Since Wake: 2700 seconds

System Integrity Protection: enabled

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

Exception Type: EXC_BAD_ACCESS (SIGSEGV)

Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000130

Exception Note: EXC_CORPSE_NOTIFY

Termination Signal: Segmentation fault: 11

Termination Reason: Namespace SIGNAL, Code 0xb

Terminating Process: exc handler [9845]

VM Regions Near 0x130:

-->

__TEXT 0000000107ac0000-0000000107f29000 [ 4516K] r-x/rwx SM=COW /Applications/Subsurface.app/Contents/MacOS/Subsurface

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

0 org.subsurface-divelog 0x0000000107ad9303 Command::SplitDivesBase::SplitDivesBase(dive*, std::__1::array<dive*, 2ul>) + 131

1 org.subsurface-divelog 0x0000000107ad9971 Command::SplitDives::SplitDives(dive*, duration_t) + 81

2 org.subsurface-divelog 0x0000000107ad26fb Command::splitDives(dive*, duration_t) + 43

3 org.subsurface-divelog 0x0000000107b3100d DiveListView::splitDives() + 365

4 org.qt-project.QtCore 0x000000010c29579a QMetaObject::activate(QObject*, int, int, void**) + 2954

5 org.qt-project.QtWidgets 0x000000010ac5b7f5 QAction::activate(QAction::ActionEvent) + 309

6 org.qt-project.QtWidgets 0x000000010adde33f 0x10ac55000 + 1610559

7 org.qt-project.QtWidgets 0x000000010addb8f4 0x10ac55000 + 1599732

8 org.qt-project.QtWidgets 0x000000010ac9f230 QWidget::event(QEvent*) + 496

9 org.qt-project.QtWidgets 0x000000010ade35f2 QMenu::event(QEvent*) + 1106

10 org.qt-project.QtWidgets 0x000000010ac64f12 QApplicationPrivate::notify_helper(QObject*, QEvent*) + 306

11 org.qt-project.QtWidgets 0x000000010ac67d6d QApplication::notify(QObject*, QEvent*) + 7357

12 org.qt-project.QtCore 0x000000010c26454f QCoreApplication::notifyInternal2(QObject*, QEvent*) + 159

13 org.qt-project.QtWidgets 0x000000010ac65840 QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool) + 896

14 org.qt-project.QtWidgets 0x000000010acbf581 0x10ac55000 + 435585

15 org.qt-project.QtWidgets 0x000000010acbe040 0x10ac55000 + 430144

16 org.qt-project.QtWidgets 0x000000010ac64f12 QApplicationPrivate::notify_helper(QObject*, QEvent*) + 306

17 org.qt-project.QtWidgets 0x000000010ac662ed QApplication::notify(QObject*, QEvent*) + 573

18 org.qt-project.QtCore 0x000000010c26454f QCoreApplication::notifyInternal2(QObject*, QEvent*) + 159

19 org.qt-project.QtGui 0x000000010b60e90c QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) + 3484

20 org.qt-project.QtGui 0x000000010b5f68bb QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 155

21 libqcocoa.dylib 0x000000010ec2ac91 0x10ec00000 + 175249

22 com.apple.CoreFoundation 0x00007fff38c54395 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17

23 com.apple.CoreFoundation 0x00007fff38c5433b __CFRunLoopDoSource0 + 108

24 com.apple.CoreFoundation 0x00007fff38c37dd1 __CFRunLoopDoSources0 + 195

25 com.apple.CoreFoundation 0x00007fff38c3737a __CFRunLoopRun + 1219

26 com.apple.CoreFoundation 0x00007fff38c36c64 CFRunLoopRunSpecific + 463

27 com.apple.HIToolbox 0x00007fff37ecdab5 RunCurrentEventLoopInMode + 293

28 com.apple.HIToolbox 0x00007fff37ecd6f4 ReceiveNextEventCommon + 371

29 com.apple.HIToolbox 0x00007fff37ecd568 _BlockUntilNextEventMatchingListInModeWithFilter + 64

30 com.apple.AppKit 0x00007fff36188363 _DPSNextEvent + 997

31 com.apple.AppKit 0x00007fff36187102 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1362

32 com.apple.AppKit 0x00007fff36181165 -[NSApplication run] + 699

33 libqcocoa.dylib 0x000000010ec29a8d 0x10ec00000 + 170637

34 org.qt-project.QtCore 0x000000010c2600a2 QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 418

35 org.qt-project.QtWidgets 0x000000010ade17ab QMenu::exec(QPoint const&, QAction*) + 107

36 org.subsurface-divelog 0x0000000107b32277 DiveListView::contextMenuEvent(QContextMenuEvent*) + 1479

37 org.qt-project.QtWidgets 0x000000010ac9f76c QWidget::event(QEvent*) + 1836

38 org.qt-project.QtWidgets 0x000000010ad48a6d QFrame::event(QEvent*) + 45

39 org.qt-project.QtWidgets 0x000000010ad4bd89 QAbstractScrollArea::viewportEvent(QEvent*) + 57

40 org.qt-project.QtWidgets 0x000000010aecb80e QAbstractItemView::viewportEvent(QEvent*) + 1502

41 org.qt-project.QtWidgets 0x000000010af37455 QTreeView::viewportEvent(QEvent*) + 517

42 org.qt-project.QtWidgets 0x000000010ad4ca44 0x10ac55000 + 1014340

43 org.qt-project.QtCore 0x000000010c264832 QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) + 210

44 org.qt-project.QtWidgets 0x000000010ac64efd QApplicationPrivate::notify_helper(QObject*, QEvent*) + 285

45 org.qt-project.QtWidgets 0x000000010ac672fb QApplication::notify(QObject*, QEvent*) + 4683

46 org.qt-project.QtCore 0x000000010c26454f QCoreApplication::notifyInternal2(QObject*, QEvent*) + 159

47 org.qt-project.QtWidgets 0x000000010acbfa18 0x10ac55000 + 436760

48 org.qt-project.QtWidgets 0x000000010acbe040 0x10ac55000 + 430144

49 org.qt-project.QtWidgets 0x000000010ac64f12 QApplicationPrivate::notify_helper(QObject*, QEvent*) + 306

50 org.qt-project.QtWidgets 0x000000010ac662ed QApplication::notify(QObject*, QEvent*) + 573

51 org.qt-project.QtCore 0x000000010c26454f QCoreApplication::notifyInternal2(QObject*, QEvent*) + 159

52 org.qt-project.QtGui 0x000000010b60e90c QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) + 3484

53 org.qt-project.QtGui 0x000000010b5f68bb QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 155

54 libqcocoa.dylib 0x000000010ec2ac91 0x10ec00000 + 175249

55 com.apple.CoreFoundation 0x00007fff38c54395 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17

56 com.apple.CoreFoundation 0x00007fff38c5433b __CFRunLoopDoSource0 + 108

57 com.apple.CoreFoundation 0x00007fff38c37dd1 __CFRunLoopDoSources0 + 195

58 com.apple.CoreFoundation 0x00007fff38c3737a __CFRunLoopRun + 1219

59 com.apple.CoreFoundation 0x00007fff38c36c64 CFRunLoopRunSpecific + 463

60 com.apple.HIToolbox 0x00007fff37ecdab5 RunCurrentEventLoopInMode + 293

61 com.apple.HIToolbox 0x00007fff37ecd6f4 ReceiveNextEventCommon + 371

62 com.apple.HIToolbox 0x00007fff37ecd568 _BlockUntilNextEventMatchingListInModeWithFilter + 64

63 com.apple.AppKit 0x00007fff36188363 _DPSNextEvent + 997

64 com.apple.AppKit 0x00007fff36187102 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1362

65 com.apple.AppKit 0x00007fff36181165 -[NSApplication run] + 699

66 libqcocoa.dylib 0x000000010ec29a8d 0x10ec00000 + 170637

67 org.qt-project.QtCore 0x000000010c2600a2 QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 418

68 org.qt-project.QtCore 0x000000010c264c62 QCoreApplication::exec() + 402

69 org.subsurface-divelog 0x0000000107ac9ebd main + 4445

70 libdyld.dylib 0x00007fff65e84ed9 start + 1

Thread 1:: Dispatch queue: com.apple.root.user-interactive-qos

0 libsystem_kernel.dylib 0x00007fff65fbe17a mach_msg_trap + 10

1 libsystem_kernel.dylib 0x00007fff65fbe6d0 mach_msg + 60

2 com.apple.QuartzCore 0x00007fff43c5696d CA::Render::Fence::wait(unsigned int, unsigned long) + 169

3 com.apple.QuartzCore 0x00007fff43bedabe CA::Context::commit_transaction(CA::Transaction*) + 1842

4 com.apple.QuartzCore 0x00007fff43becda8 CA::Transaction::commit() + 576

5 com.apple.AppKit 0x00007fff361c1b94 NSPerformVisuallyAtomicChange + 154

6 com.apple.AppKit 0x00007fff3647870a __42-[NSAnimation(NSInternal) _runInNewThread]_block_invoke + 80

7 libdispatch.dylib 0x00007fff65e35d53 _dispatch_call_block_and_release + 12

8 libdispatch.dylib 0x00007fff65e36dcf _dispatch_client_callout + 8

9 libdispatch.dylib 0x00007fff65e44e80 _dispatch_root_queue_drain + 671

10 libdispatch.dylib 0x00007fff65e454bd _dispatch_worker_thread2 + 90

11 libsystem_pthread.dylib 0x00007fff660776dd _pthread_wqthread + 619

12 libsystem_pthread.dylib 0x00007fff66077405 start_wqthread + 13

Thread 2:

0 libsystem_pthread.dylib 0x00007fff660773f8 start_wqthread + 0

1 ??? 0x0000000054485244 0 + 1414025796

Thread 3:

0 libsystem_pthread.dylib 0x00007fff660773f8 start_wqthread + 0

1 ??? 0x0000000054485244 0 + 1414025796

Thread 4:

0 libsystem_kernel.dylib 0x00007fff65fc17de __psynch_cvwait + 10

1 libsystem_pthread.dylib 0x00007fff6607b593 _pthread_cond_wait + 724

2 libc++.1.dylib 0x00007fff63559bda std::__1::condition_variable::wait(std::__1::unique_lock<std::__1::mutex>&) + 18

3 org.qt-project.QtWebKit 0x000000010a347b4c 0x108749000 + 29354828

4 org.qt-project.QtWebKit 0x000000010a347acb 0x108749000 + 29354699

5 org.qt-project.QtWebKit 0x000000010a347999 0x108749000 + 29354393

6 org.qt-project.QtWebKit 0x000000010a347c4d 0x108749000 + 29355085

7 libsystem_pthread.dylib 0x00007fff66078305 _pthread_body + 126

8 libsystem_pthread.dylib 0x00007fff6607b26f _pthread_start + 70

9 libsystem_pthread.dylib 0x00007fff66077415 thread_start + 13

Thread 5:: Qt bearer thread

0 libsystem_kernel.dylib 0x00007fff65fc62ee poll + 10

1 org.qt-project.QtCore 0x000000010c2b9090 qt_safe_poll(pollfd*, unsigned int, timespec const*) + 112

2 org.qt-project.QtCore 0x000000010c2ba8c9 QEventDispatcherUNIX::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 857

3 org.qt-project.QtCore 0x000000010c2600a2 QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 418

4 org.qt-project.QtCore 0x000000010c0aa101 QThread::exec() + 113

5 org.qt-project.QtCore 0x000000010c0b3657 0x10c086000 + 185943

6 libsystem_pthread.dylib 0x00007fff66078305 _pthread_body + 126

7 libsystem_pthread.dylib 0x00007fff6607b26f _pthread_start + 70

8 libsystem_pthread.dylib 0x00007fff66077415 thread_start + 13

Thread 6:

0 libsystem_pthread.dylib 0x00007fff660773f8 start_wqthread + 0

1 ??? 0x0000000054485244 0 + 1414025796

Thread 7:

0 libsystem_pthread.dylib 0x00007fff660773f8 start_wqthread + 0

1 ??? 0x0000000054485244 0 + 1414025796

Thread 8:: QQmlThread

0 libsystem_kernel.dylib 0x00007fff65fc62ee poll + 10

1 org.qt-project.QtCore 0x000000010c2b9240 qt_safe_poll(pollfd*, unsigned int, timespec const*) + 544

2 org.qt-project.QtCore 0x000000010c2ba8c9 QEventDispatcherUNIX::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 857

3 org.qt-project.QtCore 0x000000010c2600a2 QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 418

4 org.qt-project.QtCore 0x000000010c0aa101 QThread::exec() + 113

5 org.qt-project.QtQml 0x000000010bd3bed9 0x10bb0b000 + 2297561

6 org.qt-project.QtCore 0x000000010c0b3657 0x10c086000 + 185943

7 libsystem_pthread.dylib 0x00007fff66078305 _pthread_body + 126

8 libsystem_pthread.dylib 0x00007fff6607b26f _pthread_start + 70

9 libsystem_pthread.dylib 0x00007fff66077415 thread_start + 13

Thread 9:: com.apple.NSEventThread

0 libsystem_kernel.dylib 0x00007fff65fbe17a mach_msg_trap + 10

1 libsystem_kernel.dylib 0x00007fff65fbe6d0 mach_msg + 60

2 com.apple.CoreFoundation 0x00007fff38c37fde __CFRunLoopServiceMachPort + 337

3 com.apple.CoreFoundation 0x00007fff38c3752d __CFRunLoopRun + 1654

4 com.apple.CoreFoundation 0x00007fff38c36c64 CFRunLoopRunSpecific + 463

5 com.apple.AppKit 0x00007fff36190f89 _NSEventThread + 160

6 libsystem_pthread.dylib 0x00007fff66078305 _pthread_body + 126

7 libsystem_pthread.dylib 0x00007fff6607b26f _pthread_start + 70

8 libsystem_pthread.dylib 0x00007fff66077415 thread_start + 13

Thread 10:: QNetworkAccessManager thread