There are a million possibilities. You could have the wrong mob, you could have the wrong window names, you could be reversing the winshow() elsewhere, blah blah blah. If you want to submit a bug report, then you need to REPRODUCE the bug in an isolated environment.

If you hate admins deleting your bug reports, maybe you shouldn't be submitting so many dubious reports?

GrimmJore wrote:

(...)i know all other possibility.

A rather bold claim.


GrimmJore wrote:

I know this is a bug because it happens randomly.Its fine one sec and BAM..it goes nuts the next.I dont think i have been submitting dubious reports i think i have made myself clear..this winshow() is not working for me.

That is indeed not a clear bug report and would likely be deleted. Obviously something isn't working the way you expect it to when you file a report, so that's a given. The real task of a detailed, useful report is to narrow down the problem to a reproducible core, which should contain as few non relevant code as possible (e.g. not your whole game's source code).
So, as you say winshow does not work for you, I compiled a test case for you.
Run this and see if it yields the desired effect.
If it does indeed open and close the window properly and reliably, then you have to find a minimum environment where this is no longer the case by adding to this line by line and compile/testing after each new element. The very moment you can reproduce the problem, you can file a decent bug report that won't be deleted, given that you provide proper information.