Alan W. Irwin wrote:
> Hazen, Andrew, and I have worked on this issue off list and
> here is the current status:
> Hazen gets inconsistently bad results for qt devices for Qt-4.5.1 and also
> for Qt-4.6.2. The inconsistency is that the errors do not appear for the
> same C
> examples for repeat runs of test_noninteractive. Later, Hazen used this
> script to test just the one qt device:
> for((a=1; a<= LIMIT; a++))
> rm *.pngqt
> make test_c_pngqt
> echo -n "$a"
Following your suggestion I simplified the test to the following:
for((a=1; a<= LIMIT; a++))
examples/c/x10c -dev pngqt -o test.png
# examples/c/x26c -dev pngqt -o test.png -fam
echo -n "$a"
This pretty consistently locks up before a reachs 1000.
By sprinkling printf statements through the code I've determined that
the lock up occurs here:
new QApplication( argc, argv, isGUI );
in the file qt.cpp.
I also tried with DYN_DRIVERS=OFF, but the same thing happens.
Note that when it locks up I can see (using top) that x-session-manager
is running at 75% and gdm at 25%. Once this happens I cannot start any
other programs and I have to restart my computer.