FLTK logo

RE: [fltk.general] Linux and FLTK in a Virtual Machine

FLTK matrix user chat room
(using Element browser app)   FLTK gitter user chat room   GitHub FLTK Project   FLTK News RSS Feed  
  FLTK Apps      FLTK Library      Forums      Links     Login 
 All Forums  |  Back to fltk.general  ]
 
Previous Message ]New Message | Reply ]Next Message ]

RE: Linux and FLTK in a Virtual Machine "MacArthur, Ian (Selex ES, UK)" Jan 14, 2014  
 
> > I'm trying to run a piece of software that uses FLTK so I've build
> FLTK
> > from scratch and the other software from scratch and it compiles with
> no
> > errors. When I try to run it, it fires up ok unti l start trying to
> > interact with the FLTK based GUI, at which point it locks up. I've
> > occasionally seen it do a repaint if I leave it for 10 minutes or so.
> 
> That's weird.
> 
> > The exact same binaries work fine on a physical machine when I've
> copied
> > them over to try them out.
> 
> So the binaries seem to be okay.


Oh! 
Now, that just reminded me... (Caution: Probably pointless anecdote coming up!)

I did once see something that might be similar. Maybe...

Questions: How many CPU cores does the VM have? How many cores does the "real" machine you tested on have?

The reason I'm asking is that I once had to help debug a bit of code that "ran perfectly" on a real machine, where it had been developed, but would not work at all well on a VM, where it was deployed.

So it turned out that the key was that the "real" machine had 2 HT cores (so looked like 4 cores to the OS) whereas the VM was a single core machine.

This mattered because the code was multi-threaded and *quite badly written* and some of the many, many, child threads were spinning, and never blocking or yielding.

On the multi-core CPU that just pegged some of the CPU's, but the rest of the program continued running on the other CPU's and "all was well".

On the VM, the "bad threads" pegged the single CPU and made the rest of the program run *really badly* - though it did still run, albeit slowly. Not 10-mins slowly, mind you, but much slower that it ought to.

Once we fixed the bad threads, all was well.

Of course, if your code is not threaded at all, this is unlikely to be a useful story...




Selex ES Ltd
Registered Office: Sigma House, Christopher Martin Road, Basildon, Essex SS14 3EL
A company registered in England & Wales.  Company no. 02426132
********************************************************************
This email and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
You should not copy it or use it for any purpose nor disclose or
distribute its contents to any other person.
********************************************************************

-- 
You received this message because you are subscribed to the Google Groups "fltk.general" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fltkgeneral+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Direct Link to Message ]
 
     
Previous Message ]New Message | Reply ]Next Message ]
 
 

Comments are owned by the poster. All other content is copyright 1998-2024 by Bill Spitzak and others. This project is hosted by The FLTK Team. Please report site problems to 'erco@seriss.com'.