[Qt-creator] App crashes if signals come to fast in debug mode?

[Murphy, Sean]

> > When debugging an application within Qt Creator, is there any reason
> > that an application would crash by sending signals to a
> > QProgressDialog too quickly?
> 
> Depends on context, but, sure, it's imaginable.
> 
> An "Evaluated Expression"  malloc(100....) + possibly actually
> writing to the memory would happily leak until the process
> runs out of memory.

I don't think I have anything like that going on other than the addition
of emitting that signal from a block of code in the programming thread
where I wasn't previously emitting it. So the difference between crashing 
and not crashing is simply whether or not the emit statement is commented
in or out in the pseudo code below, the <do some stuff> block below is being 
called always, only the addition of the signal emission causes the crash.

if(pageIsEmpty)
{
  <do some stuff>
  emit sigPageProgrammed(currentPageNum, totalNumPages); 
}

> > If I rebuild the application in release mode, and run it either from
> > within Qt Creator (using CTRL+R) or run it outside Qt Creator
> > altogether it runs just fine without crashing, only crashing inside Qt
> > Creator and only in debug mode.
> 
> When debugging or running the application when compiled in debug mode?

The crash definitely occurs when debugging, no breakpoints are set though. I didn't 
attempt running the application outside of Creator/debugger with a debug build 
though. I'll try that tomorrow.

> 
> > So the only real difference I see is
> > that for the first 17% of programming, the signals are coming out
> > fairly slowly, after that, the next clump of signals are going to come
> > out much faster based on how quickly that programming thread can
> > determine that each of the remaining pages are empty.
> >
> > Any ideas?
> 
> Open an issue on bugreports.qt-project.org and attach a debugger log
> (contents of right pane of Windows->Views->Debugger Log) there.

I'll poke around some more tomorrow and see what I can turn up and if 
there's anything issue-worthy.

> 
> PS:
> 
> > tHIS MEssage has been scanned for malware by Forcepoint.
> 
> And what was the result?

No idea, but I'm guessing this message will be scanned too!


This message has been scanned for malware by Forcepoint. www.forcepoint.com