Skip to content

Screen corruption  #920

Closed
Closed

Description

@jlmcgraw

screenshot at 2017-01-04 18-44-52

Details for the issue

Screen corruption in Database Schema view

Sample database that shows the problem is included in this archive https://www.dropbox.com/s/j018ph69x9nduv4/data.tar.xz

Useful extra information

I'm opening this issue because:

  • DB4S is crashing
  • DB4S has a bug
  • DB4S needs a feature
  • DB4S has another problem

I'm using DB4S on:

  • Windows: ( version: ___ )
  • Linux: ( _distro:_Ubuntu Mate 16.10 ___ )
  • Mac OS: ( version: ___ )
  • Other: ___

I'm using DB4S version:

  • 3.9.1
  • 3.9.0
  • Other: ___3.9.99 from PPA

I have also:

Activity

  1. justinclift commented on Jan 5, 2017

    @justinclift
    Member

    Well, that's different. 😉

    Doing some searching online shows various issues with screen corruption in VirtualBox, and also some with AMD cards.

    Does either of that apply to you? 😄

  2. justinclift commented on Jan 5, 2017

    @justinclift
    Member

    Hmmm, also wondering if it's maybe a Qt thing. Hmmm....

  3. justinclift commented on Jan 5, 2017

    @justinclift
    Member

    Next thought, does it start out looking like that, or is the corruption triggered by something? eg it starts out looking ok, but corruption happens when making the window bigger (for example)

    Trying to make a mental picture here of what the cause could be. 😄

  4. jlmcgraw commented on Jan 5, 2017

    @jlmcgraw
    Author
  5. vtronko commented on Jan 5, 2017

    @vtronko
    Member

    I don't think it's DB B related issue, seriously.

  6. justinclift commented on Jan 5, 2017

    @justinclift
    Member

    @jlmcgraw Has that link changed? Just tried it and got a 404. 😉

    I'm kind of thinking it's likely a bug in VirtualBox that's being triggered by some weird edge case.

    Random things to try, that might start to show the shape of the problem:

    • In the VirtualBox settings, see if changing graphics related things helps. eg Try different video memory sizes
    • Also in VirtualBox, do you have the Guest Addons loaded for the VM? Not sure if it'll make a difference but try changing this (if possible for MATE 16.10)

    On a different tangent, are you ok with compiling things from source code? It'd be interesting to see if using a version compiled locally in the VM itself has the same problem. Just in case it's caused by some weird mismatch in (for example) the Qt libraries on your VM vs the system it was compiled on.

    I guess it comes down to... how much effort are you willing to spend to investigate? 😀

  7. jlmcgraw commented on Jan 5, 2017

    @jlmcgraw
    Author
  8. justinclift commented on Jan 5, 2017

    @justinclift
    Member

    @innermous Yeah, it's more likely a Qt issue related to some weird virtualbox bug. It doesn't mean we should ignore it though, as it is obviously affecting DB4S.

  9. justinclift commented on Jan 5, 2017

    @justinclift
    Member

    @jlmcgraw Definitely try compiling DB4S (our abbreviation for sqlitebrowser) on the VM. I'm hoping 😄 it's a weird interaction between VirtualBox and the Qt libraries of the system it was compiled on. If that's the case, then using a version built on the VM has a reasonable chance of working.

  10. justinclift commented on Jan 5, 2017

    @justinclift
    Member

    @jlmcgraw It's very late in my TZ, so I'm hitting the sack in the next few minutes. I'll take a look at this issue again tomorrow and see if you've made any progress.

    Btw, the new download link worked fine. Haven't investigated the data set yet (a tomorrow task). 😄

  11. jlmcgraw commented on Jan 5, 2017

    @jlmcgraw
    Author
  12. jlmcgraw commented on Jan 5, 2017

    @jlmcgraw
    Author
  13. vtronko commented on Jan 5, 2017

    @vtronko
    Member

    Use hastebin or alternatives for such long outputs next time, please :)

  14. jlmcgraw commented on Jan 5, 2017

    @jlmcgraw
    Author
  15. 7 remaining items

  16. jlmcgraw commented on Jan 6, 2017

    @jlmcgraw
    Author
  17. justinclift commented on Jan 6, 2017

    @justinclift
    Member

    Well, (to me) it seems like a Qt bug that there's not much we can do about until the Qt library in Ubuntu is updated. It's probably going to be triggered by all kinds of weird stuff, and isn't really worth the time to investigate more as we're already kind of overloaded with things.

    Note - It's not a complete loss, people will be able to find the details in this issue here with some simple searching. 😄

  18. justinclift commented on Jan 6, 2017

    @justinclift
    Member

    @jlmcgraw With the spatial56day.db database, it seems good for testing our SQLite parser with (an area of things we're working on).

    Is it ok with you if we hang onto it and use it for development stuff?

  19. jlmcgraw commented on Jan 6, 2017

    @jlmcgraw
    Author
  20. justinclift commented on Jan 6, 2017

    @justinclift
    Member

    Awesome @jlmcgraw, thanks. 😄

    @MKleusberg The archive here has a database in it (/databases/spatial56.db) that seems useful for your parser testing:

        https://www.dropbox.com/s/fk1uup3zx7sb8r0/data.tar.xz?dl=0

  21. chrisjlocke commented on Jan 6, 2017

    @chrisjlocke
    Member

    ...and that hasn't been stored on dbhub.io because..... ;)

  22. vtronko commented on Jan 6, 2017

    @vtronko
    Member

    @chrisjlocke nice catch

  23. justinclift commented on Jan 6, 2017

    @justinclift
    Member

    @chrisjlocke Good point. I haven't created any real reference data sets on the dev1 server yet mainly because I've been working on the visualisation stuff.

    But yeah, it doesn't hurt to upload it there to make things easier. 😉

  24. justinclift commented on Jan 6, 2017

    @justinclift
    Member

    @chrisjlocke It's on DBHub now:

        https://dev1.dbhub.io/justinclift/spatial56day.db 😄

    It's over 200MB in size... that's the first one of largish size I've tried btw. Kind of surprised it uploaded and downloaded without issues, though it did. Upload was a bit slow, but that's probably because it's not a beefy server at the moment.

    Did a binary compare of the database file downloaded from DBHub, to the original... it's bit perfect. Yay. 😉

  25. chrisjlocke commented on Jan 6, 2017

    @chrisjlocke
    Member

    Always good to test 'real data'. ;)
    200 MB for a database (uncompressed) is quite minimal really....

  26. jlmcgraw commented on Jan 6, 2017

    @jlmcgraw
    Author
  27. justinclift commented on Jan 6, 2017

    @justinclift
    Member

    Heh Heh Heh, good points. 😄

  28. mgrojo commented on Aug 13, 2019

    @mgrojo
    Member

    I was able to reproduce this under Ubuntu 18.04 with the database provided in #1965. Qt version is 5.9.5. It is only reproduced if the QT_QPA_PLATFORMTHEME environment value is set and with value gtk2. This isn't the Ubuntu default, I set it in my profile, so that DB4S looks the same as other applications in the desktop (default dark theme), otherwise it uses a clear theme, with which this problem is not reproduced. I guess that using QT_QPA_PLATFORMTHEME=gtk2 is buggy and Ubuntu does not use it, although it has the effect of Qt applications having a different look than other desktop applications.

    I don't open this issue again, because it seems a pure Qt bug, but I felt like it was a good idea to record this information here.

  29. mgrojo commented on Aug 13, 2019

    @mgrojo
    Member

    It is possible to fix the display problem using qt5c and setting a font with size 12, but there is still a performance problem and the CPU usage of sqlitebrowser and Xorg are very high.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions