Closed marilmanen closed 3 years ago
Getting warmer, but that doesn't fully explain this:
woz$ ls src/*.h | wc -l
104
woz$ nc-ng src/*.h # Just "Untitled"
Socket Error State: 1
Socket Error String: QLocalSocket: Remote closed
woz$ ls src/*.cpp | wc -l
69
woz$ nc-ng src/*.cpp # Just "Untitled"
Socket Error State: -1
Socket Error String: Unknown error
woz$ nc-ng client/nc.cpp # Opened properly
Socket Error State: -1
NEdit: client request packet received:
[
{
"create": 0,
"geometry": "",
"iconic": 0,
"is_tabbed": -1,
"langMode": "",
"line_number": 0,
"path": "/Users/anj/Software/other/nedit-ng/client/nc.cpp",
"read": 0,
"toDoCommand": "",
"wait": false
}
]
Socket Error String: Unknown error
I did just trigger these too, which are a bit different:
woz$ nc-ng src/*.h
QAbstractSocket::waitForBytesWritten() is not allowed in UnconnectedState
Socket Error State: 1
Socket Error String: QLocalSocket: Remote closed
woz$ nc-ng src/*.cpp
QAbstractSocket::waitForBytesWritten() is not allowed in UnconnectedState
Socket Error State: 1
Socket Error String: QLocalSocket: Remote closed
@anjohnson I think/hope that my next push to master will address the "just seeing Untitled" issue when opening large sets of files. It also will fix the fact that release builds had all log output effectively disabled. That wasn't intentional :-P.
OK, @anjohnson pushed to master. I believe that this will fix half of your issue :-). And you should see better feedback when something goes wrong ;-P
@marilmanen reproduced! XFce does indeed seem to be a factor, I'll do my best to resolve this ASAP!
@marilmanen perhaps fixed in master?!?
~NOTE, now that I've fixed debug logging, on some platforms we get "Warning: QCoreApplication::postEvent messages".~
I am going to look into that, but it seems mostly harmless for now aside from cluttering the console.|
EDIT: Fixed that in master too!
Great, it seems to work or at least no more crashes with the simple ways I had previously.
@marilmanen FANTASTIC!
I can say that I snuck in a quick context menu fix after my last comment. So if you're not QUITE up to date, it is recommended to update (sorry for the rapid-fire commits, but when I'm in a groove I tend to just bang out code).
I'm going to close this issue! Please re-open/open a new issue if a similar problem occurs.
@anjohnson I think we should track your issue with a new issue. I'll create it and tag you in it!
Unfortunately it's me again. I have started getting daily crashes (yesterday and today), but I have not yet figured out what triggers the crash. I have removed some of the files that are open in nedit-ng, so maybe there's still something wrong in that area.... This crash happened when I tried to run a macro.