Using Valgrind with Qt from command line to debug memory error

Question

I'm having a memory error in my Qt-based application, I'm trying to use the Valgrind tool to detect the error but unfortunately when using Valgrind with my executable it runs and finishes without opening the GUI.

My command used is: valgrind --track-origin=yes executable_path

The output is:

==4982== Memcheck, a memory error detector
==4982== Copyright (C) 2002-2012, and GNU GPL'd, by Julian Seward et al.
==4982== Using Valgrind-3.8.1 and LibVEX; rerun with -h for copyright info
==4982== Command: executable_path
==4982== 
==4982== HEAP SUMMARY:
==4982==     in use at exit: 2,661,594 bytes in 33,665 blocks
==4982==   total heap usage: 36,967 allocs, 3,302 frees, 3,228,496 bytes allocated
==4982== 
==4982== LEAK SUMMARY:
==4982==    definitely lost: 0 bytes in 0 blocks
==4982==    indirectly lost: 0 bytes in 0 blocks
==4982==      possibly lost: 1,962,915 bytes in 27,027 blocks
==4982==    still reachable: 698,679 bytes in 6,638 blocks
==4982==         suppressed: 0 bytes in 0 blocks
==4982== Rerun with --leak-check=full to see details of leaked memory
==4982== 
==4982== For counts of detected and suppressed errors, rerun with: -v
==4982== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 10 from 6)

My expectation is that this command will open the GUI and I'll do the steps for reproducing the issue then when I close the tool the report is written in the terminal, so what is wrong with the command that causes Valgrind to finish before even opening the tool.