I use TeXstudio 2.12.6 (hg 6632:7777b2b8a906) win portable on Win10 (old ini)
backtrace is:
EXCEPTION_ACCESS_VIOLATION at 70c303
[bt] 00527ea0 ??? error: 487
[bt] 0070c303 ??? error: 487
[bt] 007302fa ??? error: 487
[bt] 0044b722 ??? error: 487
[bt] 00461e89 ??? error: 487
[bt] 00740d44 ??? error: 487
[bt] 68c7b152 ZN11QMetaObject8activateEP7QObjectiiPPv+1986
[bt] 00744db4 ??? error: 487
[bt] 00489e30 ??? error: 487
[bt] 0048a30d ??? error: 487
[bt] 0045b92c ??? error: 487
[bt] 00475b42 ??? error: 487
[bt] 00740f2c ??? error: 487
[bt] 68c7b152 ZN11QMetaObject8activateEP7QObjectiiPPv+1986
[bt] 61fc3e01 ZN7QAction8activateENS_11ActionEventE+289
[bt] 0131cb70 ??? error: 126
so it works without that old ini ?
Yes, without ini it's work fine
the remove "centralVSplitterState=@ByteArray(\0\0\0\xff\0\0\0\x1\0\0\0\x2\0\0\x1\x84\0\0\x1\x17\0\xff\xff\xff\xff\x1\0\0\0\x2\0)" from that ini.
see also: https://sourceforge.net/p/texstudio/bugs/2191/
Unfortunantly, it does not helped me.
I found the crush appear (not often, just time to time) when I change the file at the compilation time
EXCEPTION_ACCESS_VIOLATION at 77028e64 (TXS-Version 6632:7777b2b8a906 R )
[bt] 00527ea0 ??? error: 487
[bt] 77028e64 RtlFreeHeap+2532
[bt] 77028bd8 RtlFreeHeap+1880
[bt] 764477c5 free+101
[bt] 70543302 ZN9GooStringD1Ev+18
[bt] 705d8e15 ZN6PDFDocD2Ev+117
[bt] 019a28ac ZN7Poppler21setDebugErrorFunctionEPFvRK7QStringRK8QVariantES5_+2700
[bt] 68db98e0 ZN10QArrayData11shared_nullE+0
Current: 8/8
0:
INSERT COMMAND: 18:0
Inserted text: "с"
1:
ERASE COMMAND: 18:0 to 18:-1
Erased text: "с", ""
2:
INSERT COMMAND: 18:0
Inserted text: "в"
3:
ERASE COMMAND: 18:0 to 18:-1
Erased text: "в", ""
4:
INSERT COMMAND: 18:0
Inserted text: "ч"
5:
ERASE COMMAND: 18:0 to 18:-1
Erased text: "ч", ""
6:
INSERT COMMAND: 18:0
Inserted text: "я"
7:
ERASE COMMAND: 18:0 to 18:-1
Erased text: "я", ""
Last edit: sergiokapone 2017-08-04
I found the crush EXCEPTION_ACCESS_VIOLATION at 77028e64 (TXS-Version 6632:7777b2b8a906 R ) appear spontaneosly, and I do not see the pattern of its appearance. After crush if I check continue of work the internal PDF Viewer show a blank pages. It seems it depend on some OS features.
Last edit: sergiokapone 2017-08-05
I had try
texstudio-2.12.6-win-portable-qt5.6.2andtexstudio-2.12.6-win-portable-qt5.9.1onWin 10 (1607 and on 1703). In all cases I use new and old.iniThe causes of crush still unknown for me. I returned to 2.12.5 (hg 6603:4d08f18b7de5) qt5.9.0 which is stable for me.Last edit: sergiokapone 2017-08-09
Since the issue was apparently introduced between hg6603 and hg6632, it's just a couple of possible changes. I propose that we gradually step up from the working hg6603 to see when the issues start.
Here es a binary of hg6610: https://sourceforge.net/projects/texstudio/files/texstudio/TeXstudio%20debug/texstudio_hg6610.exe/download
Just copy it into the folder of your 2.12.5 (hg 6603:4d08f18b7de5) qt5.9.0 installation and execute it instead of the original texstudio.exe. Is is still stable?
Now I testing TeXstudio 2.12.6 (hg 6632:7777b2b8a906) Qt 5.9.1 R (Win 10 1703)
It seems to me, with a some ~20% probability of occurrence it is possible to reproduce a bug.
root.texinput iteach
fileN.texhas magic comments likeroot.texroot.tex.fileN.texfileN.tex)root.tex. (PDF Viewer does not change the page!!! and still showfileN.tex)Or you can chaotically change tabs and close PDF Viewer.
I can attach my project, if one needed.
Last edit: sergiokapone 2017-08-09
2.12.5 ( hg6603 and hg6610)
With this versions, after doing above algorithm in 6th step **PDF Viewer changing the page!!! ** And no crush happen. But, if it happens that both
root.texandfileN.texwill refer to the same place (due to synctex) in PDF page I get a crush!Last edit: sergiokapone 2017-08-09
Now I testing TeXstudio 2.12.6 (hg 6632:7777b2b8a906) Qt 5.9.1 R (Win 10 1703)
With 100% probality the bug is related to TeXLive's SYNCTEX option (last update)
With TeXLive
-synctex=1I get the crush. Without TeXLive-synctex=1I get no crush.I had changed TeX distributive from TeXLive to MikTex
With MikTeX's
-synctex=1options a get no crush anymore.I found
TeXLile: SyncTeX command line utility, version 1.3
MiKTeX: does not shiped such utility.
It seems
-synctex=1does not relates to synctex.exe utility. Or it does? What can cause the crush with TeXLile, such utility or lua/pdf/xelatex .exe's with an argument-synctex=1?Last edit: sergiokapone 2017-08-10
Also getting crashes on linux.
Here's a stack trace which also mentions synctex: (no debug symbols sorry)
Last edit: Jean-Michaël Celerier 2017-08-20
Did a debug build:
synctex is not written by us.
You could try to copy the current synctex code from https://github.com/jlaurens/synctex and compile again, to see whether that fixes the issue.
If not you shoukld start discussing with them ...
we have updated synctex, no way of saying that it fixed any problem