Bug 147247

I can reproduce this bug in a current KDE4 SVN build. (kdelibs r766524, kdebase r766781). However, there may be multiple instances of konqueror running. And note that the timing is really important. The right click has to happen within a very short timespan after you closed the konqueror window. If you click too late, it won't crash. 
Below you can find a GDB backtrace for this crash.

GDB:
Program received signal SIGABRT, Aborted.
[Switching to Thread 0xb63c9a10 (LWP 4467)]
0xffffe410 in __kernel_vsyscall ()
#0  0xffffe410 in __kernel_vsyscall ()
#1  0xb65eb1f1 in *__GI_raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#2  0xb65ec9b8 in *__GI_abort () at abort.c:88
#3  0xb65e47d5 in *__GI___assert_fail (assertion=0xb4ad5519 "!s_refcnt", 
    file=0xb4ad5474 "/var/tmp/portage/kde-base/kdelibs-9999.4/work/kdelibs-9999.4/khtml/khtml_global.cpp", line=244, 
    function=0xb4ad56a0 "static void KHTMLGlobal::finalCheck()") at assert.c:78
#4  0xb48776b7 in KHTMLGlobal::finalCheck ()
    at /var/tmp/portage/kde-base/kdelibs-9999.4/work/kdelibs-9999.4/khtml/khtml_global.cpp:244
#5  0xb4bfb305 in ~KHTMLFactory (this=0x8407b10)
    at /var/tmp/portage/kde-base/kdelibs-9999.4/work/kdelibs-9999.4/khtml/khtml_factory.cpp:35
#6  0xb72e356d in QObjectCleanupHandler::clear (this=0x81f2618) at kernel/qobjectcleanuphandler.cpp:133
#7  0xb72e3600 in ~QObjectCleanupHandler (this=0x81f2618) at kernel/qobjectcleanuphandler.cpp:79
#8  0xb7babe1b in destroy ()
    at /var/tmp/portage/kde-base/kdelibs-9999.4/work/kdelibs-9999.4/kdecore/util/kpluginfactory.cpp:29
#9  0xb7a8edbb in ~KCleanUpGlobalStatic (this=0xb7be4554)
    at /var/tmp/portage/kde-base/kdelibs-9999.4/work/kdelibs-9999.4/kdecore/kernel/kglobal.h:65
#10 0xb7babd80 in __tcf_0 ()
    at /var/tmp/portage/kde-base/kdelibs-9999.4/work/kdelibs-9999.4/kdecore/util/kpluginfactory.cpp:29
#11 0xb65eddbc in *__GI_exit (status=0) at exit.c:75
#12 0xb65d7fe4 in __libc_start_main (main=0x80487c0 <main>, argc=1, ubp_av=0xbf9b8e14, init=0x8048810 <__libc_csu_init>, 
    fini=0x8048800 <__libc_csu_fini>, rtld_fini=0xb7f70100 <_dl_fini>, stack_end=0xbf9b8e0c) at libc-start.c:261
#13 0x08048731 in _start ()

The description there is a completely different one, but this bug has the same backtrace as bug #156172. Maybe the two are related / are the same after all.

I vote dup.

*** This bug has been marked as a duplicate of 156172 ***

I think it's technically not the same, this is relatively minor, though.

Is it  possible to reproduce in curren trunk?

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!