wxpython 2.6.3.2

wxPython Users
1

Hi Robin,

Not sure if you remember me, but I am developer here
at LLNL. Anyhow I built new RPMS for x86_64 nodes
with your new version and this seems to blow the nodes
up (immediately eats all available memory on the node and causes
the program thrash constantly reading/writing to swap)

wxPython-common-gtk2-unicode-2.6.3.2-1_py2.3
wxPython2.6-devel-gtk2-unicode-2.6.3.2-1_py2.3
wxPython2.6-gtk2-unicode-2.6.3.2-1_py2.3

If I downgrade back to 2.6.1.0
my application works fine.

2

Herb Wartens wrote:

Hi Robin,

Not sure if you remember me, but I am developer here
at LLNL. Anyhow I built new RPMS for x86_64 nodes
with your new version and this seems to blow the nodes
up (immediately eats all available memory on the node and causes
the program thrash constantly reading/writing to swap)

Does the wxPython Demo (or any part of it) behave this way as well? If not can you narrow down your app to try and find the part of the code that causes it?

···

--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!

3

Hi Robin,
Its been a while since I looked into this issue. I just tried
it on the newer code 2.6.3.3 and the problem still exists there
on x86_64 nodes....
I tracked it down to a call in

wx.grid.Grid
the AutoSize function as well as the AutoSizeRows cause x86_64 nodes to
consume all available memory on a node, rendering it useless. Once I removed
this call from my code things are much better on x86_64...
Could you look into this issue...?
Thanks...

-Herb

Herb Wartens wrote:

···

Hi Robin,

Not sure if you remember me, but I am developer here
at LLNL. Anyhow I built new RPMS for x86_64 nodes
with your new version and this seems to blow the nodes
up (immediately eats all available memory on the node and causes
the program thrash constantly reading/writing to swap)

wxPython-common-gtk2-unicode-2.6.3.2-1_py2.3
wxPython2.6-devel-gtk2-unicode-2.6.3.2-1_py2.3
wxPython2.6-gtk2-unicode-2.6.3.2-1_py2.3

If I downgrade back to 2.6.1.0
my application works fine.

4

Herb Wartens wrote:

Hi Robin,
Its been a while since I looked into this issue. I just tried
it on the newer code 2.6.3.3 and the problem still exists there
on x86_64 nodes....
I tracked it down to a call in

wx.grid.Grid
the AutoSize function as well as the AutoSizeRows cause x86_64 nodes to
consume all available memory on a node, rendering it useless. Once I removed
this call from my code things are much better on x86_64...
Could you look into this issue...?

I don't currently have a 64-bit machine to test this on...

How many rows/cols does your grid have? Do you use a custom table class? Can you reproduce the problem with the Grid samples in the demo?

···

--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!