User forums > Nightly builds
The 09 March 2019 build (11579) is out.
raynebc:
I went into "Plugins>Manage plugins", selected all plugins (since all were enabled by default) and clicked Disable. After it spent several seconds disabling them one by one, the program crashed. I tried the process again and it crashed immediately after the dialog displays that it is disabling FortranProject. So I decided to open C::B, disable a set of 10 plugins at a time, use "Save everything" and restart the IDE just so I could make progress. After disabling the first couple sets this way I saw the number of failed assertion messages had decreased. Ultimately, I found that attempting to disable the "FortranProject", "Symbol Table Plugin" or "Thread Search" plugins (even individually) causes the IDE to immediately crash, so I skipped them. I was able to disable all plugins other than those 3. After doing so, I only have to click Continue 16 times to get into the IDE when I open it during a Remote Desktop session.
Miguel Gimenez:
The Thread Search crash is known (ticket 777) and linked to the Reopen Editor crash in ticket 807.
The Fortran Project crash has the same origin (use-after-free), but in this case the solution is easy: remove the call to Destroy() in FortranProject::RemoveLogWindow(bool appShutDown). I will try to report this to Darmar.
At least three plugins fail due to this use-after-free issue; Probably in old SDK code the cbEVT_REMOVE_LOG_WINDOW event didn't delete the window, but now it does and this plugins are not aware of the change.
EDIT: I can't reproduce the Symbol Table plugin crash.
oBFusCATed:
raynebc: What are the exact steps to reproduce the asserts? Start codeblocks from a rdesktop terminal?
raynebc:
All I have to do is remote desktop from computer A to computer B, and while remotely operating computer B, launch this nightly release of Code::Blocks on computer B. Both computers in this scenario are running Windows 7 x64 Pro, although I'm not sure if that's relevant. Most of the time, when I run into problems with programs not working in a Remote Desktop session it's involving limitations with the session's display such as no support for hardware acceleration (Mozilla Firefox has had problems with this off and on).
oBFusCATed:
Can you try older night builds and 17.12? The goal is to see if this issue is caused by the switch to wx3.1 and 64bits.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version