What to do if Xojo does not tell a problem

I am unable to debug a part of my program because the program simply crashes and Xojo does not give me any idea as to what is causing the bug. It switches over to Xojo and it just says ‘event loop’ in the stack trace and nothing in the code. When I set the HTMLViewer I have to a different renderer, the behaviour changes unexpectedly.

For ‘Native’ it just does as I have just described. For ‘WebKit’, it highlights a piece of code within a timer on a different window and it does not tell me what kind of error and I cannot work it out.

Is it a bug in Xojo or the OS or does Xojo not detect the problem behind more complicated bugs? Either way, Xojo is clearly not behaving correctly.

Thanks

It sounds like a Framework issue with WebKit. Submit a Feedback report with the project along with details on how to reproduce including which OS, version, etc.

I don’t want to upload my project, thanks.

I will see what I can do to reproduce the bug.

Thanks

Fill a bug report, include a crash log from Apple. Maybe it helps finding it.
And post feedback ID here, so we can look.

[quote=146128:@Christian Schmitz]Fill a bug report, include a crash log from Apple. Maybe it helps finding it.
And post feedback ID here, so we can look.[/quote]
What do I do to share the crash log on Windows 7?

Thanks