Comment 10 for bug 135228

you didn't describe a sequence of action leading to the bug on an another computer or included a debugging information or what code logic is wrong so it's not really possible for somebody else to work on the issue without those details