This small patch applies cleanly to 4.8.5 : https://bugs.kde.org/show_bug.cgi?id=261538#c31 and solves the issue Reproducible: Always
Thanks for reporting. Is this patch about to reduce a warning only?
(In reply to comment #1) > Thanks for reporting. Is this patch about to reduce a warning only? I'd say - mostly. OTOH one comment son the origin reports says : >I wrote "this will leak" for a good reason. It does leak, forgetClient() can >only do some basic cleanup (forgetting this client, like the name says) but not >delete associated containers, that caused crashes (e.g. when they were being >deleted already).
Thanks for reporting, this is fixed in CVS now. + 18 Aug 2012; Johannes Huber <johu@gentoo.org> + +files/okular-4.9.0-memory-corruption-warning.patch, +okular-4.8.5-r1.ebuild, + +okular-4.9.0-r1.ebuild, -okular-4.8.5.ebuild, -okular-4.9.0.ebuild: + Backport upstream patch fixes a to early destructed object, which produces a + ugly warning. This will leak standalone popupmenus and could lead to crashes. + Spotted by Toralf Förster <toralf.foerster@gmx.de>, bug #431126.