So this should be good test, if it doesn't trigger a crash on your machine, you are probably safe from this. I have been able to reduce the actions required to reproduce the crash to a few steps with 100%. So it is probably not a TeXmacs issue or build issue, but an issue of interaction of Qt with the particular windows machine at hand. However it is still particular to one PC, and does not occur on another PC I have tried (both Win 10 64 Bit latest). ![]() The bad news: The table crash issue is still existent. I assume that Qt manages the main event loop of TeXmacs so the cpu issue and the table issue might both be related to Qt. When the CPU issue has been fixed in the slowphil build I could test whether this also eliminates the table issue. So I moved over to 1.99.18 official build. So probable conclusion: since the code base is identical there must be differences in the compile process and the libraries linked in between the official build chain and slowphil's. The cpu issue was there, and I could reproduce the table crash.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |