Author Topic: The 13 April 2009 build (5535) is out.  (Read 102205 times)

Offline ollydbg

  • Developer
  • Lives here!
  • *****
  • Posts: 5910
  • OpenCV and Robotics
    • Chinese OpenCV forum moderator
Re: The 13 April 2009 build (5535) is out.
« Reply #15 on: April 17, 2009, 09:37:33 am »
@dk.
In my windows system, I always get crash when I drag the toolbar.
See my post here, Is it related issue?
http://forums.codeblocks.org/index.php/topic,9648.msg67823.html#msg67823

Someone suggests using a old wxWidgets library. :D
If some piece of memory should be reused, turn them to variables (or const variables).
If some piece of operations should be reused, turn them to functions.
If they happened together, then turn them to classes.

Offline thomas

  • Administrator
  • Lives here!
  • *****
  • Posts: 3979
Re: The 13 April 2009 build (5535) is out.
« Reply #16 on: April 17, 2009, 11:45:08 am »
I've got a crash of Code::Blocks last nightly , when moving toolbars or other windows.
Yes, I've seen this happen under Ubuntu (using the official build bundled with Jaunty Jackalope) too, but only when running Code::Blocks on a remote X server. On top of that, Code::Blocks is practically unusable in that environment, as it takes between half a second and two seconds before a mouse click is realized (1000 MBit network with about 3 meters total cable length). It takes about 20 seconds just to start up, as well.
The same copy of Code::Blocks started locally on the same machine fires up in little over a second, runs perfectly reliably, and exposes the same perceived speed as the Windows build. All other applications that I'm using work seemingly the same whether run locally or via network (no noticeable difference at all).

Not sure what it is, but I guess wxGTK is having an issue there, somehow the event loop not coping well with network, or whatever...?
"We should forget about small efficiencies, say about 97% of the time: Premature quotation is the root of public humiliation."

Offline mmkider

  • Almost regular
  • **
  • Posts: 150
Re: The 13 April 2009 build (5535) is out.
« Reply #17 on: April 17, 2009, 12:08:22 pm »
I've got a crash of Code::Blocks last nightly , when moving toolbars or other windows.
Yes, I've seen this happen under Ubuntu (using the official build bundled with Jaunty Jackalope) too, but only when running Code::Blocks on a remote X server. On top of that, Code::Blocks is practically unusable in that environment, as it takes between half a second and two seconds before a mouse click is realized (1000 MBit network with about 3 meters total cable length). It takes about 20 seconds just to start up, as well.
The same copy of Code::Blocks started locally on the same machine fires up in little over a second, runs perfectly reliably, and exposes the same perceived speed as the Windows build. All other applications that I'm using work seemingly the same whether run locally or via network (no noticeable difference at all).

Not sure what it is, but I guess wxGTK is having an issue there, somehow the event loop not coping well with network, or whatever...?
See my post(Sorry, I lost the  password of mmkider :( ), and add one line code.
I always  "never" get crash when I drag the toolbar. :lol:
 
http://wxforum.shadonet.com/viewtopic.php?t=23624&highlight=bug+wxmsw

« Last Edit: April 17, 2009, 12:10:30 pm by mmkider »

Offline pasgui

  • Almost regular
  • **
  • Posts: 165
    • LGP
Re: The 13 April 2009 build (5535) is out.
« Reply #18 on: April 17, 2009, 01:21:23 pm »
I am running on Ubuntu 64-bit.  It is not a file permission access problem (they are under my home directory).

Which version of Ubuntu ?

Best regards, pasgui

Offline Xaviou

  • Regular
  • ***
  • Posts: 402
    • X@v's wxStuff
Re: The 13 April 2009 build (5535) is out.
« Reply #19 on: April 17, 2009, 01:35:16 pm »
Since updating to SVN 5534 none of my projects will open on Code::Blocks.  Was there a change that requires me to do something to the project files?

I get the SVN updates via Ubuntu package manager updates as third party updates which has always worked before. I notice the build number is one less than this message thread title. Does that have something to do with my issue?

The About dialog says I am running: svn build rev 5534 (2009-04-13 14:47:54) gcc 3.1.2 Linux/unicode

I get a dialog saying - "Can't open file. Do you want to remove if from the recent file list?"

I am running on Ubuntu 64-bit.  It is not a file permission access problem (they are under my home directory).

I confirm this.
As I am the one who made the deb files, I'll try to make a full rebuild, to see if it works better.

About the rev number : I don't know why, but after a checkout to rev 5535, the build gives a 5534 (it happens on Linux and on Windows). Is it a known behaviour ? Can someone explain this ?

For the moment, I'll tell Ubuntu amd64 users to not do the update, until the package hasn't been rebuild.

Sorry for the inconvenience.

Regards
Xav'
The french wxWidgets site : http://www.wxdev.fr
My wxWidgets's stuff : https://wxstuff.xaviou.fr/

Offline dk

  • Multiple posting newcomer
  • *
  • Posts: 55
    • Code::Blocks for ALT Linux Sisyphus
Re: The 13 April 2009 build (5535) is out.
« Reply #20 on: April 17, 2009, 02:47:23 pm »
@dk.
In my windows system, I always get crash when I drag the toolbar.
See my post here, Is it related issue?
http://forums.codeblocks.org/index.php/topic,9648.msg67823.html#msg67823

Someone suggests using a old wxWidgets library. :D

Looks like I have another problem. I've downgraded to the old (2.8.6) version og wxGTK, аnd C::B still crashes with the old wxGTK.

Also I've applied that patch to wxAuiManager::OnFloatingPaneMoveStart on wxGTK 2.8.9, аnd it doesn't help.

« Last Edit: April 17, 2009, 02:48:57 pm by dk »
Denis Kirienko
C::B maintainer for ALT Linux distribution (http://www.sisyphus.ru/srpm/codeblocks)

Offline dk

  • Multiple posting newcomer
  • *
  • Posts: 55
    • Code::Blocks for ALT Linux Sisyphus
Re: The 13 April 2009 build (5535) is out.
« Reply #21 on: April 17, 2009, 02:52:06 pm »
Also I've found, that it isn't a new problem - C::B SVN 5382 also crashes.
And version 8.02 looks to be more stable, but sometimes also crashes when moving toolbars.
« Last Edit: April 17, 2009, 02:56:48 pm by dk »
Denis Kirienko
C::B maintainer for ALT Linux distribution (http://www.sisyphus.ru/srpm/codeblocks)

Offline Jenna

  • Administrator
  • Lives here!
  • *****
  • Posts: 7255
Re: The 13 April 2009 build (5535) is out.
« Reply #22 on: April 17, 2009, 04:08:12 pm »
About the rev number : I don't know why, but after a checkout to rev 5535, the build gives a 5534 (it happens on Linux and on Windows). Is it a known behaviour ? Can someone explain this ?

That's because r5535 is a commit against wxAui-test branch and r5534 was the last commit in trunk before the nightly.

By the way, I do not have crashes when dragging toolbars on debian unstable 64-bit build against wx2.8.9.

Offline wagb278

  • Single posting newcomer
  • *
  • Posts: 6
Re: The 13 April 2009 build (5535) is out.
« Reply #23 on: April 17, 2009, 04:32:11 pm »
@pasgui - I am running Ubuntu (64-bit) 8.04 LTS

I looked at the update manager settings and I (think) my place of origin for Code::Blocks is LPG (http://lgp203.free.fr/ubuntu/ hardy universe)

I also show http//apt.wxwidgets.org/ hardy-wx main (but that appears to be just for WxWidgets.

My first version of Code::Blocks was SVN:5432.  My system auto-updated to SVN 5456 a few days after I started using Code::Blocks and I think there have been two or three updates since.

I tried to create a new project and that caused Code::Blocks to crash.  It created an exception file which I presume got sent to where ever problems get reported.

How can I revert back to the previous version?
« Last Edit: April 17, 2009, 05:11:44 pm by wagb278 »

Offline Xaviou

  • Regular
  • ***
  • Posts: 402
    • X@v's wxStuff
Re: The 13 April 2009 build (5535) is out.
« Reply #24 on: April 17, 2009, 06:27:25 pm »
Hi

How can I revert back to the previous version?
I've rebuild the packages, so you don't have to revert back to an old version. Just uninstall all Code:Blocks 's packages (via synaptic).

If you can't wait that pasqui updates its repository, you can re_install it manually :
- Download the complete archive (the link provided here will give you the updated version)
- Decrompress the archive : you'll get a folder containing some deb files
- Open a terminal window, and go to this folder
- Install all the packages with the following command : sudo dpkg -i *.deb

Then, you will be able to re-open your projects and work with Code::Blocks.

I apologize for the inconvenience

Regards

Xav'

The french wxWidgets site : http://www.wxdev.fr
My wxWidgets's stuff : https://wxstuff.xaviou.fr/

Offline wagb278

  • Single posting newcomer
  • *
  • Posts: 6
Re: The 13 April 2009 build (5535) is out.
« Reply #25 on: April 17, 2009, 07:17:57 pm »
THANKS Xaviou

Worked like a charm.

While using the new Code::Blocks - I got a notice from the update manager that an update is available for codeblocks-dbg.  What should I do with this update - NOT install it?  There is no version or date info for the available codeblocks-dbg update (because it's a third party source, presumably).

Thanks again for the quick fix.
« Last Edit: April 17, 2009, 07:46:24 pm by wagb278 »

Offline pasgui

  • Almost regular
  • **
  • Posts: 165
    • LGP
Re: The 13 April 2009 build (5535) is out.
« Reply #26 on: April 17, 2009, 10:08:07 pm »
I've rebuild the packages, so you don't have to revert back to an old version. Just uninstall all Code:Blocks 's packages (via synaptic).

I've updated the repository.

Best regards, pasgui

Offline ollydbg

  • Developer
  • Lives here!
  • *****
  • Posts: 5910
  • OpenCV and Robotics
    • Chinese OpenCV forum moderator
Re: The 13 April 2009 build (5535) is out.
« Reply #27 on: April 19, 2009, 05:51:50 am »
I've got a crash of Code::Blocks last nightly , when moving toolbars or other windows.
Yes, I've seen this happen under Ubuntu (using the official build bundled with Jaunty Jackalope) too, but only when running Code::Blocks on a remote X server. On top of that, Code::Blocks is practically unusable in that environment, as it takes between half a second and two seconds before a mouse click is realized (1000 MBit network with about 3 meters total cable length). It takes about 20 seconds just to start up, as well.
The same copy of Code::Blocks started locally on the same machine fires up in little over a second, runs perfectly reliably, and exposes the same perceived speed as the Windows build. All other applications that I'm using work seemingly the same whether run locally or via network (no noticeable difference at all).

Not sure what it is, but I guess wxGTK is having an issue there, somehow the event loop not coping well with network, or whatever...?
See my post(Sorry, I lost the  password of mmkider :( ), and add one line code.
I always  "never" get crash when I drag the toolbar. :lol:
 
http://wxforum.shadonet.com/viewtopic.php?t=23624&highlight=bug+wxmsw



Thank you very much!
I changed the code in AUI as you mentioned, and rebuilt wxmsw28u_gcc_custom.dll.
After that, the "drag toolbar" problems disappeared! :D
If some piece of memory should be reused, turn them to variables (or const variables).
If some piece of operations should be reused, turn them to functions.
If they happened together, then turn them to classes.

Offline geiermeier

  • Multiple posting newcomer
  • *
  • Posts: 19
Re: The 13 April 2009 build (5535) is out.
« Reply #28 on: April 20, 2009, 09:01:46 am »
I'm experiencing the toolbar-drag crashes with the current nightly and the library versions given in the opening post under XP SP3.

Offline mmkider

  • Almost regular
  • **
  • Posts: 150
Re: The 13 April 2009 build (5535) is out.
« Reply #29 on: April 20, 2009, 09:48:05 am »
I'm experiencing the toolbar-drag crashes with the current nightly and the library versions given in the opening post under XP SP3.

Download this wxmsw2.8.10 with my patch.

http://mmkider.googlepages.com/wxmsw28u_gcc_cb_wx2810.7z

Code
void wxAuiManager::OnFloatingPaneMoveStart(wxWindow* wnd)
{
    // try to find the pane
    wxAuiPaneInfo& pane = GetPane(wnd);
    wxASSERT_MSG(pane.IsOk(), wxT("Pane window not found"));

   //patch there.
   if(!pane.frame)
        return;
       
    if (m_flags & wxAUI_MGR_TRANSPARENT_DRAG)
        pane.frame->SetTransparent(150);
}

« Last Edit: April 21, 2009, 08:48:08 am by mmkider »