#77 voyager: memory fault on fc12

admin
closed-fixed
5
2010-06-08
2010-05-08
No

The voyager GUI is giving seg faults (memory violations) on fc12 with KDE, not sure which it might be related to as I don't have either of these. The fault can be seen on startup and debuged with

startBristol -libtest -voyager -console -exec -valgrind

The current error is as below (this has now been fixed but the root cause is still not understood):

==2965== Thread 2:
==2965== Invalid write of size 4
==2965== at 0x352BC0B693: brightonDevUndraw (brightonPanelMgt.c:60)
==2965== by 0x352BC122CF: displaytouch (brightonTouchpanel.c:54)
==2965== by 0x352BC1257C: configure (brightonTouchpanel.c:198)
==2965== by 0x352BC0BE7D: configurePanel (brightonPanelMgt.c:234)
==2965== by 0x352BC0EF00: brightonWorldChanged (brightonRender.c:199)
==2965== by 0x352BC08D6F: brightonEnterNotify (brightonEventHandlers.c:303)
==2965== by 0x352BC08EE8: brightonFocusIn (brightonEventHandlers.c:390)
==2965== by 0x352BC0836B: brightonEventLoop (brightonEventHandlers.c:835)
==2965== by 0x404976: eventMgr (brighton.c:1720)
==2965== by 0x3529C06A39: start_thread (pthread_create.c:297)
==2965== by 0x35290DE62C: clone (clone.S:112)
==2965== Address 0x4ec7750 is 0 bytes after a block of size 336 alloc'd
==2965== at 0x4A0515D: malloc (vg_replace_malloc.c:195)
==2965== by 0x352BC05B15: brightonmalloc (brightonC.c:44)
==2965== by 0x352BC04A0E: brightonCreateBitmap (brightonBitmaps.c:40)
==2965== by 0x352BC04A89: brightonCreateNamedBitmap (brightonBitmaps.c:63)
==2965== by 0x352BC0ECAB: brightonWorldChanged (brightonRender.c:118)
==2965== by 0x352BC08D6F: brightonEnterNotify (brightonEventHandlers.c:303)
==2965== by 0x352BC08EE8: brightonFocusIn (brightonEventHandlers.c:390)
==2965== by 0x352BC0836B: brightonEventLoop (brightonEventHandlers.c:835)
==2965== by 0x404976: eventMgr (brighton.c:1720)
==2965== by 0x3529C06A39: start_thread (pthread_create.c:297)
==2965== by 0x35290DE62C: clone (clone.S:112)
==2965==

The interesting thing is that the bitmap area at fault here is just 336 bytes which implies just 84 pixels - 7x12, this seems small but its size could be irrelevant, this is just a device undraw operation and it may be a small window already.

Discussion

  • Andrew C

    Andrew C - 2010-05-09

    I'm not getting this oddly enough and the voyager seems to work fine for me. I'd suspect it's a problem with the window manager. Perhaps a different window manager would yield different results?

    On a related note, is it just the voyager that's segfaulting?
    I know you fixed a bug where for some reason all the dual manual emulators were seg-faulting...

    Andrew.

     
  • Nick Copeland

    Nick Copeland - 2010-05-13

    The above issue has been fixed along with some other anomalies from KDE and delivery of ConfigureNotify for very small window sizes. This is the 'PostageStamp' effect. The fix/wordaround for these is to ignore ludicrously small requests and to resize the window to 'nominal'. These fixes were tested against KDE4.3.

    The report is going to stay open until KDE4.4 can be tested presently.

     
  • Frank

    Frank - 2010-05-13

    I can confirm that the problems with KDE 4.4 seem to be fixed, tested on KDE 4.4.3. I was looking for my report for that in the tracker but didn't find it...
    Many thanks for the fixes

     
  • Nick Copeland

    Nick Copeland - 2010-05-17

    The crash is now erradicated and the postage stamp effect no longer happens. The remaining issue for the Voyager is that it needs notes to be played in the GUI before the it will respond to events from the MIDI interface. That may end up as another case as the whole debuging process will be distinct.

     
  • Nick Copeland

    Nick Copeland - 2010-06-08

    This was fixed in a recent upload, the case is going to be closed. The remaining issues with KDE 4.4 will have to wait until I can get it installed as the current procedure was really messy.

     
  • Nick Copeland

    Nick Copeland - 2010-06-08
    • status: open --> closed-fixed
     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.





No, thanks