> Hi Ben,
Hi Tony,
Lot’s of questions here! Let’s see:
> There may indeed be an issue with fonts being tied to having at least one
> window present, which causes you grief when you delete the main window.
>
> Have you tried the suggestion from your other thread to just hide the main
> window
Hi Ben,
There may indeed be an issue with fonts being tied to having at least
one window present, which causes you grief when you delete the main window.
Have you tried the suggestion from your other thread to just hide the
main window instead?
Where is the tick font used? Does your main m
I have just filed bugs on the two problems discovered here:
QTBUG-86874
QTBUG-86875
I have not found a way to get menu item relocation in the global menubar to
work properly on macOS without triggering a crash on quit as a side effect, and
I think I’m going to give up on it for the time being.
Sorry for all the emails; this is proving to be quite a difficult problem and
I’m really hoping somebody has insight into it.
This code also produces the same crash as the static QFont usage I posted in my
previous email, and this code seems very clearly innocent:
QFont tickFont;
#ifd
Hi all. I’m starting a new thread since the focal question has completely
changed. I’ve tracked down the cause of the crash that I discussed in the
previous thread, to a specific bit of code:
static QFont *tickFont = nullptr;
if (!tickFont)
{
tickFont = new QFont();
> Sent: Tuesday, September 22, 2020 at 12:46 PM
> From: "Tino Pyssysalo"
> To: "Jason H" , "giuseppe.dang...@kdab.com"
>
> Cc: "interest@qt-project.org"
> Subject: Re: [Interest] Help with maintenance tool
>
> On 22.9.2020, 16.19, "Interest on behalf of Jason H"
> wrote:
>
> > Thanks, I
AddressSanitizer. (Except on macOS it will not find memory leaks) You should be
able to find the double free quite quickly. You do NOT Have to rebuild Qt with
the address sanitizer flags, just your own codes. We just got done using ASAN
on our own code base and it was able to pinpoint the same k
Thanks Giuseppe; this looks very interesting. I’d love to be able to run
Valgrind.
Thanks also to Mitch; I see your email now, and it also looks very useful. To
avoid spamming the list with thank-yous, I’ll just say in advance, thanks to
all others who might respond with helpful suggestions.
Il 23/09/20 14:08, Ben Haller via Interest ha scritto:
Thanks for the suggestion. However, this problem is only on macOS, and
Valgrind doesn’t appear to run on any macOS later than 10.12 (“preliminary”
support for 10.13, according to their website; I’m not sure what that means).
I’m on macOS
(To be more clear: my hardware, a “Late 2019” MacBook Pro, can’t even run macOS
10.13 – or 10.14, for that matter. 10.15 is required on my hardware, so
Valgrind is out of the question, at least on this machine. If I can find
hardware that can run 10.13, then I can see whether Valgrind’s “preli
Thanks for the suggestion. However, this problem is only on macOS, and
Valgrind doesn’t appear to run on any macOS later than 10.12 (“preliminary”
support for 10.13, according to their website; I’m not sure what that means).
I’m on macOS 10.15.6, and I’m using Qt 5.14.2 which has a minimum mac
Valgrind.
> -Original Message-
> From: Interest On Behalf Of Ben Haller via
> Interest
> Sent: Wednesday, September 23, 2020 7:50 AM
> To: qt qt
> Subject: [Interest] Debugging a double dealloc
>
> [External]
>
> Hi all. I’m trying to figure out what appears to be a double dealloc pro
Hi all. I’m trying to figure out what appears to be a double dealloc problem
of some sort. I’m sure the actual bug is in my code (I’m trying to get a
window with complex subsidiary windows, etc., to disassemble and free the
things it owns, without freeing itself), but the backtrace at the poin
13 matches
Mail list logo
