How can I find the bug indicated by Xojo?

I am developing an application.
When I run it, a tab appears along the top showing a little symbol of a bug.
Although the program runs fine without problems, Xojo thinks there is a bug somewhere.
Note: It doesn’t make any difference whether I have “Break on exception” enabled or not.

I could go thru the code, and use breakpoints, etc, to try and find where the “bug” is, but is there a simpler way of just going to where the line is that Xojo doesn’t like?

You are seeing the Debugger tab, nothing to worry about


1 Like

I found that confusing from the beginning. To run the app we click on a button with a “play” icon and that creates a tab with a bug icon?! Who had this idea, why not repeat the play icon in the corresponding tab? Xojo has invested so much time in API 2 to make things clearer and left such a bug in the UI.

1 Like

And labelled “Run”. That’s clear enough.

There are Pause and Stop buttons in that tab. If you Pause the app, the icon becomes Run. The tab is labelled with the name of your app.

1 Like

Thanks for everyone for answering so quickly.

So there is no bug at all!
Well that explains why the program runs without problems.

Yes, this is really a confusing element of the GUI design.


What you should now do is run it with a bug to see what happens. Something like:

Var i, arr(5) as Integer

i = 10
arr(i) = 0

should do nicely.

I never liked that the tab for the debugger is the right most and not the left most one (next to the main one). It should be easier to identify than the measly bug icon.


You can slide the tabs along the tab bar, to rearrange them.

My guess is the bug represents the debugger window. But it could be confusing, especially for someone new to Xojo. This is one of those design things that we all overlook - it’s been that way for so long we’re used to it. It takes a fresh and objective view to point out that there might be a better way.

That said, all software has it’s quirks. Sometimes we just need to learn how it works. But if it were my software, I would change the bug icon to something else.

I know that. But I don’t want to move the tab dozens of times a day.

I wondered about trhat. But that tab is for debugging in the app you’re running. Or pausing it and examining its variables to see whether they are what they should be. How else do you indicate that this is a tab for debugging, without using the bug icon?

1 Like

With a “debug” icon instead of a “bug” icon? F.e. a “play” icon and then just label as “Debugger”. :sweat_smile:


And another color like white or black. I usually have half a dozen tabs open.

1 Like

What is the “debug” icon?

I was joking @TimStreater :hugs:

1 Like

I can’t tell you how many times my heart has skipped a beat when I catch that little bug icon out of the corner of my eye - “What’s gone wrong?!?!?!?” Terrible piece of UI design.

1 Like

Maybe like RealStudio did.


Ha well mebbe so but still if people are complaining about what we have now they should propose an alternativve.

I happen to think there are some good suggestions that have been brought up here. I’ve created a Feedback case:



I was not disturbed by the bug icon but maybe the Play icon is more clear.