-
-
Notifications
You must be signed in to change notification settings - Fork 715
Occasional crash on mouseover - double free or corruption #1117
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I've observed this too and seems to be caused only when cursor options are set. I could not reproduce it reliably either, so fixing it is currently at an impasse. If anyone can get this to reproduce reliably, please let us know. |
:( Is there any debug info I could provide that you haven't already seen for this? A trace? |
I actually don't have a backtrace with line numbers (must have deleted it by accident), and considering how hard it is to reproduce it, getting as much data as possible will be helpful. |
I'll generate a backtrace with numbers. From the output above it seems the issue is within this function: |
From a run with -log=trace. This one ended up with 'malloc(): memory corruption' interestingly enough.
|
Got a backtrace and gdb stack trace:
|
I noticed that the motion handler doesn't lock the mutex, which might be an issue if multiple mouse events occur rapidly. See if this prevents the error from occurring: |
Thanks! I will try this build for a few days and report if I see the issue. |
No crashes on this build so far \o/ |
I haven't experienced any crashes either, so that was probably the issue. I already made the PR, so this should be fixed in master pretty soon. |
Breaking Changes: * `0 < label-NAME-maxlen < 3` will now throw an exception and disable the containing module, if ellipsis is enabled for that label. (#1198) Changelog: Deprecations: * `internal/volume` is now called `internal/alsa` (#967) * temperature: The `%temperature%` is deprecated in favor of `%temperature-c%`(#897) * mpd: `icon-repeatone` is deprecated in favor of `icon-single` (#1295), see #1279 Features: * feat(mpd): Add support for icon-consume (#861) * feat(bspwm): Add workspace separator (#942) * feat(i3): Add workspace separator (#938), see #929 * feat(build): Make polybar build on FreeBSD (#931, polybar/xpp#8), see #239 * feat(volume): Add pulseaudio backend (#779) * feat(script): Add %pid% token for tail commands (#934) * feat(temp): Add temperature tokens without unit (#897) * feat(memory): Add memory used/free ramp (#1038), see #1037 * feat(memory): Add swap tokens (#1018) * feat(net): Add unknown-as-up option (#1077), see #457 * feat(config): Support fractional size and offset (#972), see #953 * feat(xwindow): Add label-empty (#1136) * feat(battery): Add animation-discharging (analog to animation-charging) (#1190) * feat(config): Support pixel offset for bar size and offset values (#1224) * feat(mpd): Add `%album-artist%` token (#1263) * feat(net): Add local_ip6 token (#1239), see #1234 * feat(net): Add nl80211 support (#1009), see #277 Fixes: * fix(mpd): Wrong elapsed time when after standby (#921), see #915 * fix(config): Wrong min, maxlen when using the same token multiple times (#974), see #971 * fix(battery): use power_now correctly (#958), see #928 * fix(mpd): Crash when mpd isn't running (#983), see #979 * fix(xworkspaces): Respect 'enable-scroll' (#1002) * fix(xbacklight): Respect 'enable-scroll' (#1014) * fix(build): support xcb-proto >=1.13 (polybar/xpp#11), see #973 * fix(mpd): Respect MPD_HOST env variable (#1025), see #1007 * fix(i3): Reconnect i3 IPC socket on restart/error (#1099), see #762 * fix(cursor): Occasional crash on mouseover (#1124), see #1117 * fix(net): Mark 'not connected' on querying failure (#1171), see #1163 * fix(gcc): Fix -Wstringop-truncation warning (#1216, polybar/i3ipcpp#7), see #1215 * fix(builder): Don't truncate colors with same channels (#1217), see #1183 * fix(bspwm): Consistent behavior when scrolling through multiple desktops (#986), see #981 * fix(builder): Respect label-ellipsis option (#1198), see #1194
Hello, I just got this issue after playing round by clicking multiple times on the two sound panels using the example polybar. I am using the basic config and running version 3.4.2. I can make a video if you want and give any required info. |
@Marti2203 When you click on which module does the crash occur? You are more likely suffering from #2129 than from this bug. |
Yeah, okay that is possible. Thank you! |
Uh oh!
There was an error while loading. Please reload this page.
Compiled at commit: 55331d1
My polybar regularly crashes on two of my machines with the following stack trace. It seems to be triggered when I mouse over the bar. I cannot reproduce this issue on demand but it happens at least twice a day.
The text was updated successfully, but these errors were encountered: