Here's my observations and specs:
I'm running Lubuntu 14.04 64bit (with lots of fluff removed to create a netbootable image, long story) on an AMD E-350 Processor and PicoScope 18.104.22.168 from the repository. Other than occasional, and very annoying, GUI hangs, the application runs fairly well. However, it will occasionally lock up. The first time this happened Mono reported an error I failed to write down - something about a SIGABRT.
My second run from commandline resulted in the following:
- Code: Select all
...Lots of the glib error...
(PicoScope.GTK:10613): GLib-CRITICAL **: Source ID 1306987 was not found when attempting to remove it
*** Error in `/usr/bin/mono': corrupted double-linked list: 0x00007f97dc0858d0 ***
at <unknown> <0xffffffff>
I know the glib error is a "known bug", but it is interesting that from the above error and from a quick google of the possible meanings of an error about SIGABRT, it seems that there's a problem either in Mono, the library, or in the GUI code itself with how memory is being handled.
It may be just a bad observation, but it seems like if I leave the window in the foreground it stays stable, but it crashes some time after switching desktops or foregrounding (focusing) another window. Or the memory corruption is just a little chaotic about when it decides to make a hash of in-use memory!
Willing to run test executables or libraries!
Running with --trace=program, will report the results when it crashes again.