> Out of curiosity: > Why use a QShardPointer and not directly allocate the object on the stack? > Would do the same.
You're probably right. I was staring at the code too long to recognize such simplicity. Reworked patch attached. E -- Erik Hovland [email protected] http://hovland.org/
0001-Fix-memory-leak-in-sort-widget.patch
Description: Binary data
_______________________________________________ Amarok-devel mailing list [email protected] https://mail.kde.org/mailman/listinfo/amarok-devel
