Opened 7 years ago

Last modified 3 years ago

#8944 assigned bug

[Tracker] Triggers debugger assert on quit with debug builds

Reported by: x-ist Owned by: nobody
Priority: low Milestone: R1
Component: Applications/Tracker Version: R1/Development
Keywords: debug assert Cc:
Blocked By: Blocking:
Has a Patch: no Platform: All

Description

Tested on hrevr1alpha4-44586. Works reliably. (will add more info later today)

Attachments (1)

HeyTrackerCrash.png (93.8 KB ) - added by x-ist 7 years ago.
DebuggerStacktrace

Download all attachments as: .zip

Change History (13)

comment:1 by diver, 7 years ago

Can't reproduce in hrev44620.

by x-ist, 7 years ago

Attachment: HeyTrackerCrash.png added

DebuggerStacktrace

comment:2 by anevilyak, 7 years ago

That assert should only be getting tripped on a debug build of libtracker. Are you saying you see the same behavior with a release build?

in reply to:  2 ; comment:3 by x-ist, 7 years ago

I tried debug build only, so I guess yes. :)

in reply to:  3 ; comment:4 by anevilyak, 7 years ago

Replying to x-ist:

I tried debug build only, so I guess yes. :)

"Release" build generally implies without debugging. In any case in future it'd be helpful if you could be a bit more explicit about the fact that you're building with custom changes, as the ticket sounds as if you're encountering this on a plain nightly image, which isn't the case.

comment:5 by umccullough, 7 years ago

Version: R1/alpha4R1/Development

in reply to:  4 ; comment:6 by x-ist, 7 years ago

Replying to anevilyak:

"Release" build generally implies without debugging. In any case in future it'd be helpful if you could be a bit more explicit about the fact that you're building with custom changes, as the ticket sounds as if you're encountering this on a plain nightly image, which isn't the case.

Sorry for that! I made a debug build of libtracker.so and Tracker. I thought it's clear from the screenshot. Otherwise Debugger couldn't refer the source code.

in reply to:  6 comment:7 by anevilyak, 7 years ago

Replying to x-ist:

Sorry for that! I made a debug build of libtracker.so and Tracker. I thought it's clear from the screenshot. Otherwise Debugger couldn't refer the source code.

It was obvious that the screenshot was taken with a debug build, yes. That didn't in any way clarify that the crash occurred exclusively with a debug build, i.e. that you didn't actually try if it crashed with a regular one, which is what the ticket description initially sounded like.

comment:8 by anevilyak, 7 years ago

Keywords: debug assert added
Priority: normallow
Summary: [Tracker] Crash on "hey Tracker quit"[Tracker] Triggers debugger assert on quit with debug builds

comment:9 by x-ist, 7 years ago

You're right! However my opinion was that if there's something wrong in the debug build, it concerns the release build as well - well could be I'm wrong.

in reply to:  9 comment:10 by anevilyak, 7 years ago

Replying to x-ist:

You're right! However my opinion was that if there's something wrong in the debug build, it concerns the release build as well - well could be I'm wrong.

ASSERT()s compile to a no-op in a release build, therefore they won't be hit there. Whether they're actually correctly pointing out a problem or not isn't quite as cut and dried, particularly in Tracker where quite a number are left over from back in Be's day and haven't really been reevaluated to see if they're still correct after all the rewrites that have happened over the years.

TL;DR: That's not a good assumption to make.

Last edited 7 years ago by anevilyak (previous) (diff)

comment:11 by axeld, 7 years ago

In any case, if it is only hit on quit, and there is no visible problem in the release build, it's not an urgent problem. It's something that should be looked into in any case, though.

comment:12 by axeld, 3 years ago

Owner: changed from axeld to nobody
Status: newassigned
Note: See TracTickets for help on using tickets.