https://bugs.kde.org/show_bug.cgi?id=436350
--- Comment #41 from Vaclav Masin <[email protected]> --- (In reply to Konrad Materka from comment #40) > Created attachment 138114 [details] > testVector.zip > > So the problem is around: > m_items.append(item); > when QVector changes capacity beyond 6... After this operation QString in > old items is empty. I don't know why this happens :( > > I attached very simple test application that does similar thing. I guess it > will work correctly but worth a try. > I'm going to attach output of that test application below. There were none of those "something went wrong" messages so I guess it worked correctly? > Does your problem happen if you remove second system tray? Removing the second system tray didn't change anything - I still get those empty system tray items once I startup an extra app. > Or on entirely fresh user? I was able to reproduce it (after some persuading) even for a fresh user. > Can you try different scenarios? I'm completely out of clues :( Don't worry about it. I've been thinking... would it make any sense for me to try to debug it myself? I mean going step by step over the code, watching the data structure that holds the systray data along the way and waiting for it to get broken at some point? I'd obviously need a nudge in the right direction from you as to where in the code to start etc. But I'm a bit of a developer myself (mostly just PHP these days), even though I haven't touched c/c++ in a quite some time and don't believe I've ever done any sort of debugging in gdb yet. So I thought this might work. What do you think - does it sound feasible to you? Or way too much effort and skill required? Or not even possible to do it like this? -- You are receiving this mail because: You are watching all bug changes.
