This repository has been archived by the owner. It is now read-only.

MTX crash after moving appended tracks #2009

Closed
hubblec4 opened this Issue Jun 11, 2017 · 10 comments

Comments

2 participants
@mbunkus

This comment has been minimized.

Show comment
Hide comment
@mbunkus

mbunkus Jun 18, 2017

Owner

At the moment I cannot reproduce such a crash, even though I've tried to create similar files regarding the number of tracks and their types. Can you please upload the first 20 MB of both VOB files to my FTP server, please? Thanks.

Owner

mbunkus commented Jun 18, 2017

At the moment I cannot reproduce such a crash, even though I've tried to create similar files regarding the number of tracks and their types. Can you please upload the first 20 MB of both VOB files to my FTP server, please? Thanks.

@hubblec4

This comment has been minimized.

Show comment
Hide comment
@hubblec4

hubblec4 Jun 18, 2017

Yes I will do this at night.

hubblec4 commented Jun 18, 2017

Yes I will do this at night.

@mbunkus

This comment has been minimized.

Show comment
Hide comment
@mbunkus

mbunkus Jun 19, 2017

Owner

Thanks, but I cannot reproduce it with those files either, neither on Linux nor on Windows (I'm following the steps you've shown in your video as closely as possible). Means fixing it will be next to impossible for the time being.

Owner

mbunkus commented Jun 19, 2017

Thanks, but I cannot reproduce it with those files either, neither on Linux nor on Windows (I'm following the steps you've shown in your video as closely as possible). Means fixing it will be next to impossible for the time being.

@mbunkus

This comment has been minimized.

Show comment
Hide comment
@mbunkus

mbunkus Jun 20, 2017

Owner

We've discussed this via email and agree to close the issue for the time being as I cannot reproduce it at all and hubblec4 can only reproduce it with one particular installation but not with others.

Owner

mbunkus commented Jun 20, 2017

We've discussed this via email and agree to close the issue for the time being as I cannot reproduce it at all and hubblec4 can only reproduce it with one particular installation but not with others.

@hubblec4

This comment has been minimized.

Show comment
Hide comment
@hubblec4

hubblec4 Jun 25, 2017

I have used the MTX 13 for a new test.
In a fresh extracted folder, open MTX and there is no Drag-Drop issue.
Now I have copied my "old" mtx-gui.ini in the new fresh folder and the Drag-Drop issue is there again.

Ini is uploaded to your ftp.

hubblec4 commented Jun 25, 2017

I have used the MTX 13 for a new test.
In a fresh extracted folder, open MTX and there is no Drag-Drop issue.
Now I have copied my "old" mtx-gui.ini in the new fresh folder and the Drag-Drop issue is there again.

Ini is uploaded to your ftp.

@mbunkus

This comment has been minimized.

Show comment
Hide comment
@mbunkus

mbunkus Jun 25, 2017

Owner

Interesting. I can reproduce the issue with your configuration file. Thanks.

Owner

mbunkus commented Jun 25, 2017

Interesting. I can reproduce the issue with your configuration file. Thanks.

@mbunkus

This comment has been minimized.

Show comment
Hide comment
@mbunkus

mbunkus Jun 26, 2017

Owner

Basically I'm convinced that this is actually a bug inside Qt where internal state is somehow corrupted during drag & drop operations if one or more columns are hidden. I've implemented something of a workaround that seems to fix the internal state.

That being said, I haven't debugged Qt itself, and therefore I don't really understand the nature of the corruption, nor why my workaround seems to work. I'm happy enough to leave the workaround in place as it seems to work on both Linux (Qt 5.8) and Windows (Qt 5.7), but I cannot in good conscience claim that this has really been fixed.

Maybe I'll find some more time to create a small test program and to file a bug against Qt.

Owner

mbunkus commented Jun 26, 2017

Basically I'm convinced that this is actually a bug inside Qt where internal state is somehow corrupted during drag & drop operations if one or more columns are hidden. I've implemented something of a workaround that seems to fix the internal state.

That being said, I haven't debugged Qt itself, and therefore I don't really understand the nature of the corruption, nor why my workaround seems to work. I'm happy enough to leave the workaround in place as it seems to work on both Linux (Qt 5.8) and Windows (Qt 5.7), but I cannot in good conscience claim that this has really been fixed.

Maybe I'll find some more time to create a small test program and to file a bug against Qt.

@mbunkus

This comment has been minimized.

Show comment
Hide comment
@mbunkus
Owner

mbunkus commented Jun 26, 2017

@hubblec4

This comment has been minimized.

Show comment
Hide comment
@hubblec4

hubblec4 Jun 26, 2017

I can totally understand you, a bug of a compontent and a workaround for that is nothing what let me good sleep.

I will test the new pre-build.

hubblec4 commented Jun 26, 2017

I can totally understand you, a bug of a compontent and a workaround for that is nothing what let me good sleep.

I will test the new pre-build.

@hubblec4

This comment has been minimized.

Show comment
Hide comment
@hubblec4

hubblec4 Jun 26, 2017

It works. Thanks Mosu.

hubblec4 commented Jun 26, 2017

It works. Thanks Mosu.

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