User forums > General (but related to Code::Blocks)

Windows Vista: Hunting bugs...

<< < (2/2)

killerbot:
could you try with the latest nightly ? Todays.

See if the file associations issues turn up.

Propagator:
Just downloaded the latest nightly (SVN 4681). Completely removed old CodeBlocks folder, unpacked latest nightly, wx dll, and mingwm10.dll into new CodeBlocks folder.

Start page still works. File associations still starts CodeBlocks. However, to check the file associations, I just double-clicked a random .cpp file. This launches CodeBlocks -> Tip of the day -> close. Then I'm left with an empty workspace (i.e. double-clicked item does not show up). If I then exit CodeBlocks it asks to save the changed layout. While the changed layout message is shown, the double-clicked item suddenly (with some delay) appears in the background. If I don't wait for this delay to pass (immediately press No in the save layout message), CodeBlock crashes on exit.

Hmmm, wait, just tried to reproduce the above behavior: I have to say, the double-clicked item does not always appear during the changed layout dialog. But CodeBlocks always crashes on exit when the item didn't show up.

If I can find some systematic thing that triggers the double-clicked item to show up, I'll post again...

Propagator:
Okay, found some systematics: A double-clicked item just takes a huge amount of time to open (on the order of one minute). If one exits CodeBlocks before this has happened, it crashes. If one waits, everything is fine. Once CodeBlocks is open after such a waiting period, double-clicking additional items works as it should (i.e. no additional waiting times).

Edit: double-clicking additional itmes already works as it should when the initial item did not yet show up...

The waiting time isn't affected by whether I just leave the computer alone during the wait or I continue to work with some other (at least low CPU load) program.

This behavior is the same whether the double-clicked item is a .cbp file or a .cpp file. Opening files via file dialog or start page works as it's supposed to (i.e. no unusual delays or crashes on exit).

Navigation

[0] Message Index

[*] Previous page