|
Artur Hefczyc opened 3 years ago
|
|
@kobit Could you check (if/when this happens again) if the conversation searches text entry field looks like on the attached screenshot? Suggestion view is displayed as a window that could be there (hiding part of the chats list) but being transparent and causing this issue. If you confirm that field is not as on the screenshot then we will have a confirmation that something is wrong. During the issue, could you check if all "chats" are not clickable? (or just a few from the top). Also, it would be good to know what you did before this happened, ie. disconnected/connected external screen, maximized/minimized window, etc. As for the actual crash, it happens inside AppKit in the code which should work (and works normally) and due to that, it is impossible to fix it. I suppose that solving "hidden window" catching events may solve this issue as well. |
|
|
Next time this happens I will check all the points mentioned and will let you know. I have another crash for version 5.0 (121) but I am not sure if you need this. This happened just a few hours after start. |
|
|
Please attach any crashes as they may be related to how you use the client and I may never encounter them |
|
|
Crash from my current version 5.0 (121) |
|
|
Weird, it is still from b120 but it looks slightly different. I’ll try to apply a fix for that tomorrow. |
|
|
Hm, maybe it is from b120 after all. The client crashes every day but crash windows are often hidden under other apps windows. I try to find the crash window and close it but not always I can find it right away. So it is possible that this crash window is a few days old. |
|
|
I've reviewed this code and improved its performance (maybe this will solve the hanging issue) and make a few small fixes. Those changes are part of 5.0-b122 |
|
|
Ok, the problem with focus happened again. Actually, this happened right after first start of 5.0-b122. I did not do anything, I was not able to. It happened right after the app start. Focus and blinking cursor was in the "Chat with..." search field. And when I click on any chat, the content of the chat does not show. I attached 2 screenshot, on one the first chat is highlighted and on the second, the last chat it highlighted. In neither case, I can see chat content or chat input line. To be honest I do not understand what you mean in your second paragraph, so I cannot provide any more information. After one more app restart, the "Chat with..." field was not in focus, no blinking cursor in the field and I can now switch between chats normally. CleanShot 2021-04-01 at 20.22.58@2x.png CleanShot 2021-04-01 at 20.25.59@2x1617333965511.png |
|
|
Thanks, your screenshots added one more detail. I was testing with a single list while you use split list (separate 1-1 chats from group chats). I’ll look into that |
|
|
I think I've replicated the issue. Today I've received a lot of spam messages and requests. The "X" button stopped responding after a few times I've closed "items" on the list very fast. I think this may be some kind of concurrency issue. Will look into it. |
|
|
@kobit I've made a few tests and the are only a few things which could be causing an issue like that:
I'll try to make Beagle crash when the view could not be loaded (it should always load so, we can crash for testing). This will help with analysis and might confirm case no. 3. Could you confirm that SHIFT/COMMAND was not pressed? (I suppose so, but there are things like "sticky" keys, so I prefer to ask about it). |
|
|
I confirm I do not press any keys while clicking time and do not use sticky keys. I was going to give a good news that BeagleIM is still running since yesterday update and startup without a crash, which is unusual for me. However, when attempting to open About window to check the build number, the About window did not open or I cannot see it. And again I have the "focus" problem and cannot switch between windows. And there is one more thing I noticed. As in the attached screenshot. Question marks next to menu items. |
|
|
@kobit Those questions marks should present a shortcut and its presentation fully relay on the macOS (it is not part of the app, as the app only defines symbols and macOS handles presentation). I'm starting to think that this is some macOS issue as from what I've seen here you have encountered:
I've checked on my iMac with macOS 10.15.7 and on MBA with macOS 11.2.3 (same as yours) and BeagleIM is working fine in my tests on both systems. However, you mentioned that issues like that happen from time to time (and not always) and if I'm correct are related to loading data (symbols or definitions of a views), so I'm wondering if that is not caused by limited resources available to the OS at that time? ie. low amount of free memory or something like that. I would like to ask you to check amount of free memory but as you have 64GB of RAM. That should not be an issue but I cannot pinpoint any other source of the issue. Maybe something is using too much memory? Please check also usage of RAM by BeagleIM when the issue appears. Checking with Activity Monitor should be enough. If you can, please attach screens from Activity Monitor and I will look for differences and possible causes of the issue. I would not suggest that this is caused by OS version (or caused by upgrade from older OS) as the issue appears from time to time and is not persistent, so most likely something triggers it. |
|
|
Another question would be: "Do you have crashes in other apps (or issue with other apps)?". It could be some HW issue (I know your hardware is rather new, but I cannot come up with any other explanation). |
|
|
@kobit there is a new beta of BeagleIM 5.0-b123. Could you update to the newest version and launch the app from the terminal? There will be additional debug entries about opening a chat. If you encounter issues with opening a conversation, please attach 100-200 last entries (or more) so I will be able to review what is going on. |
|
|
Updated and started. Search chat was in focus but I had no problem switching between chats. So far so good. I will let you know once something new comes up. |
|
|
As for the other questions/suggestion. No other apps crash or give me any problems. I am at about 50% of RAM usage. The only non-standard usage pattern I can think of is that I never turn my computers off. They are always ON. Only screen is turned off. Plus, I have XMPP clients running on many mobile devices connecting to the same accounts as BeagleIM. Ah, one more maybe non-standard use is that I have 9 active accounts in BeagleIM. Much less on mobile devices. |
|
|
@kobit I'm using BeagleIM and I'm also not shutting down iMac (just suspending). My current uptime of iMac is:
It may be connected to a number of used accounts. I would suggest checking |
|
|
I am not even suspending my Macs. I only turn the screen off. |
|
|
Focus problem again. App did not crash but I cannot switch between chats. Actually I can highlight the chat on the left hand side list but the chat window does not change. Tried to open preferences as suggested but the preferences window does not open. Here is output from the console: |
|
|
@kobit I've published new version 5.0-b124 with increased logging level. Please run it from them command line and attach output when the issue appears (just as the last time). I was not able to fix the issue but hopefully with increased logging I'll be able to fix it. |
|
|
@kobit Do you still experience this issue? or it is "OK" for now? |
|
|
Did not have much opportunity to use Beagle last week. Will confirm next week. |
|
|
Unfortunately I have focus problem again. Here is the dump from the terminal output: |
|
|
I've reviewed this log and from what I can see that in there is a block of code that is executed only from a single thread and it is executed only partially. The second part (after a call to the AppKit - part of the macOS) is not called and it does not return an error. That is the same line that was throwing an exception and causing crashes when you initially reported this issue. From that, I can just assume that this method from the AppKit throws some kind of exception that is not being reported to Swift at all (some very low-level error). I know there are ObjectiveC exceptions and most likely it is one of them but I do not know what is causing it or even how to handle the exception correctly. Moreover, in the logs there are following lines: that are related to AppKit (once again AppKit) having an issue reading/parsing a system file from macOS. That was not seen in the previous logs, but we had an issue with loading view definition out of a file, so it looks it could be related to our issue. As we have now a new macOS and this issue appeared at some point (could be after the previous macOS release), I would suggest trying to upgrade macOS and keep an eye on this issue. Maybe Apple found this issue and fixed it |
|
|
I have the most recent MacOS updated yesterday (04/26/2021) and unfortunately, I experienced yet another crash today. Attaching stack trace and terminal output below. |
|
|
That is the same issue as you reported some time ago (crash when accessing database file), but it starts to look like a temporary issue with accessing files (Storyboard file to access view or database to query/insert data). I'll look into that but it is hard to replicate the issue as I was not able to replicate it. |
|
|
I am now, (most recent MacOS and most recent BeagleIM Beta build) experiencing the focus problem practically all the time. Restarting the app and few minutes later I can no longer switch between chats. At this moment the app is practically unusable for me. Not to put pressure on you or anything. Just so you know that the problem is very apparent. I do not know if it affects only me though. |
|
|
I've asked (some time ago) at our support channel if anyone had a similar issue (to see how widespread is this issue), but until now no one else reported this issue. I've updated to the newest version of macOS and still was not able to replicate the issue. However, Wojciech reported an issue with the invalid ordering of chats that (in theory) could be related to your issue. A new build of BeagleIM (5.0-b125) contains a fix for that. |
|
I ran into the issue (it's been happening quite often in the recent days tbh): can't switch to the chat by clicking on it; I was able to click on "Chat with...", type in it and select contact and at that time Beagle (Version 5.3.5 (178)) crashed with: |
|
|
It looks like NSViewController cannot load storyboard, that is almost impossible, as it work normally in typical usecase, so I wonder what actually is happening that macOS fails to load storyboard (embedded within the app). I'll review the code, but I'm not sure what we can do to fix that. |
|
|
OK, I'm not sure what's happening but right now I'm getting the issue (not able to switch chat or complete crash) couple of times a day... |
| Type |
Bug
|
| Priority |
Normal
|
| Assignee | |
| Spent time |
11h 30m
|
Issue Votes (0)
Watchers (0)
Sometimes I have a problem with the client that it runs and shows new messages but I cannot switch to a different chat. It's like there is a modal dialog open and I cannot get focus on a chat view. This time, this happened when a new spam subscription request and new spam message arrived. I could not switch to presence view to block the contact but when I clicked on the cross icon to close the spam chat the client crashed.