StyledEdit sometimes does not open because it's already running without a window

[Kev]

Disclaimer: I know this won't be too useful yet since I can't reproduce it, but it has now happened to me twice since upgrading, so I wanted to open this ticket in case I could add more info later.

On nightlies about a month ago, StyledEdit worked normally, but I just did a clean install of hrev46922, and now none of the following do anything:

1) clicking StyledEdit on the Haiku menu 2) double-clicking a text file 3) trying to launch it from a Terminal window:

~> /boot/system/apps/StyledEdit 
~> 

There is no delay, but no window appears.

Oh, I just found it was already running in processcontroller. I killed it, and now it opens fine.

[Kev]

More specifically, StyledEdit wasn't exhibiting this behaviour under hrev46756.

[diver]

Do you have "Translate application and folder names..." in Locale->Options checked by any chance?

[Kev]

debug report

[Kev]

Replying to diver:

Do you have "Translate application and folder names..." in Locale->Options checked by any chance?

Nope.

Also I had it happen again just now, so in processcontroler this time I debugged it and saved the report. Also at the time it was not taking any CPU.

[anevilyak]

Unfortunately, that debug report doesn't really yield anything helpful, since the main thread was still in a running state, and consequently has no stack trace. If/when it occurs again, please pick "Debug" on that thread first, prior to asking to save a report in order to stop it.

[Kev]

Oddly, this time when I chose "debug" to open the debugger, StyledEdit ended up opening the file I had double-clicked. (It's not a big file at 3 kb, so I had expected it to open instantly, given that I had no other programs running at the time.) So I still hit "debug" within the debugger to make the report just attached, but it may not be the exact same situation as before.

[anevilyak]

This case does indeed appear to be a bit different, and the backtrace in the report shows the app thread in pretty much its normal state, which is to say the app looper's message loop waiting to receive the next message to handle, nothing unusual.

[Kev]

Argh! Not only that, it turns out tha the file it ended up opening, it corrupted the last two thirds or so of it (truncated it and replaced it with a line or two of garbage characters), and of course I had not backed it up just yet. That's too bad...I had found StyledEdit rock-solid up until this issue, and had never had data corruption issues with it.