Since v2.19.1 (b173), Rainlendar has started to freeze then unexpectedly quit after every 24-48 hours. When it runs, all is fine, but then after this timeframe the system tray icon is replaced with a blank space (see screen grab). When I right click on the tray icon, the menu that appears is blank. Then the application crashes.
You can see that all is normal until about line 2037, when there are lots of 'ASSERT’s.
My PC is running Windows 11 64 bit. I tried uninstalling completely and removing all data files, then reinstalling, but no change. Also installed on a different laptop (Win 10 64 bit) - same issue.
That’s a weird issue. Seems that all the images get invalidated for some reasons. Unfortunately I have no idea what could be causing this. I have not seen such myself or heard that anyone else has a similar problem (if someone has, please tell here).
Hmm. The other thing I should mention is that it seems to happen after the PC has been in hibernate mode. This may be a coincidence as I hibernate my computer at night and if it crashes after 24 hours or more, then it may have happened anyway (whether hibernated or not). Also, it doesn’t happen straight after waking up, but sometimes hours later.
OK - nothing to do with hibernate - it’s just done it again. This time it’s only been about 6 hours and the computer has been switched on the whole time.
I find that installing Rainlendar (or any other open source program) in a different directory (I created and use C:\Programs_OS) makes a lot of permission problems go away.
I’m having the same problem as the OP but on Windows 10 64bit. After a couple of days (approximately) the program will either close or when I right-click on the calendar, to create a new event, there is a white rectangle where the menu should be. Within a minute the program then crashes and closes.
I’ve been experiencing this behavior for many months. Prior to that the program was very stable.
I’m also running it on an older computer, running Windows 10, and have no problems at all.
I checked from the framework library’s source code and the warning text seems to be related to the mouse cursor. So, I wonder if it’s somehow related to the resize or click cursors.
If you move the mouse to the edge of the calendar do you get the resize cursor and will that add the asserts to the log? How about if you hover the mouse over a button on the calendar?
I have the option selected to lock the windows in place and don’t have resize because of that. Just deselected the option and only have one resize cursor available to extend the lower edge of the calendar. The width isn’t resizable. I’m only using two windows, calendar and events. Even when I deselect the fixed window position option there’re no resize cursors available for the events window.
I’m using a Shadow4 skin with 4 windows: Event List, Todo List, Month View and Grid Calendar.
I get both H and V resize cursors at the edge of the Month View. I only get the H resize cursor for the Event List and Todo List. I don’t get any resize cursors for the Grid Calendar.
The ASSERT log messages don’t appear when I get a resize cursor or hover over any calendar buttons. In fact they generally only appear after Rainlendar has been running for several hours (usually about a day).
I’ve attached a screenshot showing all my skin settings.
I don’t think this has anything to do with any setting that you can set from the options. It could be some resource leak somewhere if the problem starts to happen only after a while. However I usually run Rainlendar continuously from several weeks to a month and haven’t noticed any such behaviour so I’m not really sure what the issue could be.
I too have been seeing this issue, but didn’t want to say anything until I was able to successfully gather a log file. It’s (unfortunately) quite large. From a cursory glance, it looks like (near the end), some content from an ICS was being applied as a component? Afterward, a large amount of debug statements about “The existing component was replaced with the new one.”
There were a handful of warning/asserts made about …\src\msw\bitmap.cpp:1943 wxInvertMask “hbmpMask”, though I don’t think they are a cause for concern.
Realistically though, the log, aside from being quite large, doesn’t seem to diagnostically pin point any particular thing at the end which might’ve caused a calamitous end of processing.
I am running Windows 10 Pro x64, Rainlendar v2.19.2 (b174 64-bit). Would it be at all useful to share my config (as opposed to the log file) via ermail? In case it’s relevant, I am using a dual monitor setup. 3440x1400 + 1920x1080.
I use DisplayFusion Pro to manage the desktops. One of its functions is to place a title bar button on each window, to enable moving the window to the other monitor. I’ve noticed it doesn’t display a button on either of the Rainlendar windows I use, calendar and events list. Maybe there’s an incompatibility.??
I’m running multiple monitors on one of my computers, but I am also running Rainlendar on my single monitor laptop and the same issue happens. So I don’t think that’s the reason I’m afraid.
Not working ! it s worse : Freeze and stop again and again
The last 2.20.1 is the more instable version
Each day i need to re-open rainlendar to use it
Also in the same network (lan)
One monitor and windows 10 pro
I suspect this won’t be too helpful, but since the debug logs don’t seem to catch anything at the time of crash… Now that I know Windows Error reporting is catching it, I can provide any crash dump files (if they’re at all helpful - I personally never learned how to read these).
