Segmentation Fault when accesing more than once

[KillGabio]

OK i dont know if it is the hour or what but this lines cause the program to finish unexpectedly, only if the process is called more than once. I mean everything goes fine when i click the button for the first time but if I click it again bamm app exits:

QPixmap bg;
    RandomInfo *randurl = new RandomInfo ();
    if (url.contains (QString ("ya_cerramos")))
        bg = QPixmap (url);
    else{
        bg = QPixmap (randurl->getRandomUrl ());
    }
    this->ui->label_imagen->setPixmap (bg);
QStringList frase_autor = QStringList ();
    frase_autor = randurl->getFraseRandom ();

QPixmap bg;
    RandomInfo *randurl = new RandomInfo ();
    if (url.contains (QString ("ya_cerramos")))
        bg = QPixmap (url);
    else{
        bg = QPixmap (randurl->getRandomUrl ());
    }
    this->ui->label_imagen->setPixmap (bg);
QStringList frase_autor = QStringList ();
    frase_autor = randurl->getFraseRandom ();

To copy to clipboard, switch view to plain text mode 

PS: this is the code of the method that returns the list, just in case:

QStringList frase_autor;
        frase_autor << query->value (1).toString ().trimmed ()<< query->value (2).toString ().trimmed ();
        return frase_autor;

QStringList frase_autor;
        frase_autor << query->value (1).toString ().trimmed ()<< query->value (2).toString ().trimmed ();
        return frase_autor;

To copy to clipboard, switch view to plain text mode 

BTW i dont get any error while executing this, the list is returned...the problem is when I assign the return list to the list of the mainclass...

[mvuori]

First thing to do would obviously be to find out where is crashes...
Success of all 'new's shoud always be checked. If the second time return null, of course the application crashes.

[ChrisW67]

Success of all 'new's shoud always be checked.

C++ new either returns successfully with memory allocated or throws a bad_alloc exception which will generally terminate the program unless you have coded to catch it. Checking the return value is largely unneeded.

KillGabio: If this is the same program you had the other day, where the ui was hacked about to replace the main window central widget, then my money is on the ui->label_imagen pointer being invalid the second time. Put:

Q_ASSERTX(ui->label_imagen, "This code", "UI is mangled :(");

Q_ASSERTX(ui->label_imagen, "This code", "UI is mangled :(");

To copy to clipboard, switch view to plain text mode 

before line 8.

BTW: Do you deallocate the RandomInfo object every time or are you leaking memory? Does this object need to be on the heap?