User forums > Help

wxsmith crashing after upgrade to Ubuntu 17.04

<< < (6/9) > >>

oBFusCATed:
Can you show me a screenshot of the broken rendering of the frame?
I don't get any crashes with your project. :(

awake:
Here is a screen shot of the incomplete rendering of the frame - you can see in the explorer on the left that there ought to be radio buttons, spin control, etc. - but on the right, only the first set of in-most sizer boxes are rendering, a static sizer box with a list box that also contains a horizontal sizer with a couple of buttons.

The second screen shot shows what it looks like when it freezes on trying to close the project. Interestingly, it doesn't always freeze - the first time today, it let me close out the project, asking if I wanted to save changes. The second time, the empty dialog box as shown is the first and only thing that appears on trying to close the project.

oBFusCATed:
For me everything renders fine. :(

Can someone with ubuntu try to reproduce the problem?

awake:
Trying a couple of new things to see if they shed any light.


* I set up a virtual machine on another computer, one that is using a 4th generation Core i5 rather than the 7th generation Core i5 that is in my laptop - just in case the difference in the CPU was affecting things. I installed Ubuntu 17.04, did all updates, and installed the repository version of C:B 16.01. I opened it and tried wxsmith on the project. Good news: I never got a freeze or a crash when closing the project, though only half-a-dozen tries - possible it would have frozen eventuall - ??. Bad news: wxsmith still did not render the frames correctly, did not show its toolbar, etc. When I tried building a new project, I was able to use wxsmith to create a frame ... up to a point. Once it got complex enough, again it starting acting wonky, and thereafter when I opened that project, again it showed only part of the frame, and did not show its toolbar. So ... does seem like there *could* be some issue related to the CPU, but overall the basic problem remains.

* I tried building C:B against wxWidgets 2.8.12. I started by uninstalling and thoroughly cleaning up any traces of wxWidgets-3 development files. Then I downloaded the latest wxGTK-2.8 source and compiled it as a monolithic library. To do so I had to include CXXFLAGS='-Wno-error=narrowing'. After that, it compiled and I was able to install it.

* Then I compiled the release version of C:B 16.01, downloaded as a .tar archive from www.codeblocks.org, using the new wx-2.8 monolithic library. I had to add CXXFLAGS='-I<codeblocks src/include directory>' to get some of the plugins to compile - this is perhaps because I was building from a subdirectory rather than directly in the codeblocks directory. This compiled fine, but when I ran it, it did not think ANY plugins were installed - even though I can see them in the /usr/local/lib/etc. directories.

* So I uninstalled this version, again making sure all traces were cleaned up, and downloaded the trunk from svn. I bootstrapped, configured --with-contrib-plugins=all, make, make install. Clean make, AND THIS VERSION WORKS!!! Now it renders the frames of the existing projects successfully, and it doesn't seem to crash as complexity is added to the frames. Note that as I use it more, we will see if that crash-free status continues ...So, at this point, I have a working version of C:B. I don't know if building it against wx-2.8 will have any limitations - ? But so glad to be able to get back to work on some projects!

oBFusCATed, thank you, thank you, thank you again for all of your help. I hope that the data I've provided will help narrow the focus to fix future versions of the Ubuntu version of C:B.

oBFusCATed:
The problem is not in the CPU, but I guess in the GPU drivers. Or it might be something that is happening only on ubuntu.

If you just open the attached project does it render correctly or it is always broken?

Navigation

[0] Message Index

[#] Next page

[*] Previous page