I getting strange message. Some times it appear at the launching, very often it appear after pressing "exit" button.
I observed this behavior with TXS 2.9.2, 2.9.4 (all portable versions)
The error-code some times equal to 6eafab, 75729b60, 89cfa8, 4cd496
After pressing "kill":
System is Win7x64.
With WinXPx86 TXS works good (another my computer).
EXCEPTION_ACCESS_VIOLATION at 68a6cdcd (TXS-Version 5006:b43062855b2d R )
[bt] 00548830 ??? error: 487
[bt] 68a6cdcd ZN7QObjectD1Ev+941
[bt] 006ffe08 ??? error: 487
[bt] 0070043b ??? error: 487
[bt] 005c963c ??? error: 487
[bt] 00471747 ??? error: 487
[bt] 0048adb4 ??? error: 487
[bt] 0048ae8d ??? error: 487
%-----other file--------------
EXCEPTION_ACCESS_VIOLATION at 75729b60 (TXS-Version 5006:b43062855b2d R )
[bt] 00548830 ??? error: 487
[bt] 75729b60 memcpy+592
[bt] 688f2129 ZN7QString11reallocDataEjb+121
[bt] 006faa35 ??? error: 487
[bt] 006fbd62 ??? error: 487
[bt] 006c7cc8 ??? error: 487
[bt] 004830a0 ??? error: 487
[bt] 004896cb ??? error: 487
[bt] 68a64e31 ZN11QMetaObject8activateEP7QObjectiiPPv+1745
[bt] 0076eea4 ??? error: 487
[bt] 005d11b2 ??? error: 487
[bt] 00471b00 ??? error: 487
[bt] 004831f7 ??? error: 487
[bt] 004896cb ??? error: 487
[bt] 68a64e31 ZN11QMetaObject8activateEP7QObjectiiPPv+1745
[bt] 0076eea4 ??? error: 487
[bt] 005cc035 ??? error: 487
[bt] 005cc365 ??? error: 487
[bt] 005cd2b8 ??? error: 487
[bt] 00471b00 ??? error: 487
[bt] 004831f7 ??? error: 487
[bt] 0048e9cd ??? error: 487
[bt] 0040419a ??? error: 487
[bt] 0040464b ??? error: 487
[bt] 00788b8b ??? error: 487
Last edit: sergiokapone 2015-04-03
This seems to depend on the document you are using. The backtrace indicates that you are using a multi-file document and
% TeX root = ...
. Can you either provide the document you were working on at that time, or even better try to reproduce the bug with the document and then reduce it to a minimal example showing the bug. Please try to find a way to reliably reproduce the crash. Without such a description we cannot track it down. Note: The startup bug seems to appear when loading a specific document by passing it as command line argument. This may include double-clicking a file in the explorer.For internal reference, here are the resolved tracebacks:
1.
2.
Last edit: Tim Hoffmann 2015-04-06
Unfortunately (or for luck), after updating windows 7, the bug is lost.
I doubt, that the update itself fixed the bug. It's probably other circumstances that changed as well (possibly unnoticed).
Since we cannot reproduce the bug, I'll mark this as "works-for-me". You may come back should the bug reappear.