# How to debug a crash on popover button press **URL:** \ **Category:** Questions\ **Tags:** windows, popover, debug\ **Created:** [November 4, 2021, 1:13pm UTC](https://the.fmsoup.org/t/how-to-debug-a-crash-on-popover-button-press/2554 "2021-11-04T13:13:32Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![JasonMark](https://avatars.discourse-cdn.com/v4/letter/j/a9adbd/32.png) [@JasonMark](https://the.fmsoup.org/u/JasonMark)\ **Post date:** [November 4, 2021, 1:13pm UTC](https://the.fmsoup.org/t/how-to-debug-a-crash-on-popover-button-press/2554/1 "2021-11-04T13:13:32Z")
Looking for advice on next steps to debug this issue: Last week we had to restore our app from backups. We did and it appeared OK, but later in the week we discovered that _some_ popover buttons just shut down Filemaker on Windows only. I'm really stumped about what else I could do to debug this other than "remove all popovers from my app" or go back to a version from a couple of weeks ago. ![image](https://canada1.discourse-cdn.com/flex030/uploads/fmsoup/original/2X/4/4d136524c50b008f3255c4f041875e026d4cc2ca.png) **Things I've tried** - Restarted server - Restarted clients - Checked to ensure they're all up to date (they are) - Made new buttons - Copied working buttons - Downloaded the file from the server and restored it (no errors found, but it still quits on windows when clicked) **Technical details** Server: Windows 19.3.2.203 hosted with [fmphost.com](http://fmphost.com) Mac client (which has no problems): 19.3.2.206 Windows clients (which don't work): 19.3.2.206 ---
**Author:** ![JasonMark](https://avatars.discourse-cdn.com/v4/letter/j/a9adbd/32.png) [@JasonMark](https://the.fmsoup.org/u/JasonMark)\ **Post date:** [November 4, 2021, 1:22pm UTC](https://the.fmsoup.org/t/how-to-debug-a-crash-on-popover-button-press/2554/2 "2021-11-04T13:22:49Z")
OK I know I just posted but I just discovered that it's a layout problem. Popups work on _some_ layouts but not others. Copying the layout copies the error, but creating a brand new layout and copying over all the assets fixes the problem sometimes. Working through more details now... ---
**Author:** ![bdbd](https://yyz2.discourse-cdn.com/flex030/user_avatar/the.fmsoup.org/bdbd/32/620_2.png) [@bdbd](https://the.fmsoup.org/u/bdbd)\ **Post date:** [November 4, 2021, 3:30pm UTC](https://the.fmsoup.org/t/how-to-debug-a-crash-on-popover-button-press/2554/3 "2021-11-04T15:30:13Z")
This screams corruption… and you likely need to recreate then ditch the layout. Have you attempted a file recovery operation? ---
**Author:** ![JasonMark](https://avatars.discourse-cdn.com/v4/letter/j/a9adbd/32.png) [@JasonMark](https://the.fmsoup.org/u/JasonMark)\ **Post date:** [November 4, 2021, 4:01pm UTC](https://the.fmsoup.org/t/how-to-debug-a-crash-on-popover-button-press/2554/4 "2021-11-04T16:01:40Z")
It does seem like corruption of some sort. Recovery didn't find anything. It's inconsistent. One layout I made a new layout and copied everything "as is" and it worked fine. For a different layout I had to remove a web viewer from the screen and it started working. As soon as I put the web viewer back it came back. ---
**Author:** ![Malcolm](https://yyz2.discourse-cdn.com/flex030/user_avatar/the.fmsoup.org/malcolm/32/196_2.png) [@Malcolm](https://the.fmsoup.org/u/Malcolm)\ **Post date:** [November 4, 2021, 5:51pm UTC](https://the.fmsoup.org/t/how-to-debug-a-crash-on-popover-button-press/2554/5 "2021-11-04T17:51:20Z")
Are fonts involved? ---
**Author:** ![JasonMark](https://avatars.discourse-cdn.com/v4/letter/j/a9adbd/32.png) [@JasonMark](https://the.fmsoup.org/u/JasonMark)\ **Post date:** [November 4, 2021, 7:55pm UTC](https://the.fmsoup.org/t/how-to-debug-a-crash-on-popover-button-press/2554/6 "2021-11-04T19:55:34Z")
@Malcolm, thanks for the idea. I was wondering if it had to do with Emoji's in my scripts or something. None of these are using scripts with Emoji's and the fact that the same button works on some layouts and not others points to some type of corruption... It could be font related, but the fact that in one case I literally copied all the things on the screen from one layout to another and it worked makes me think it's _probably_ not fonts, but I'll check the screen to be sure everything's using the same font and see if that changes anything. ---
**Author:** ![Malcolm](https://yyz2.discourse-cdn.com/flex030/user_avatar/the.fmsoup.org/malcolm/32/196_2.png) [@Malcolm](https://the.fmsoup.org/u/Malcolm)\ **Post date:** [November 4, 2021, 9:00pm UTC](https://the.fmsoup.org/t/how-to-debug-a-crash-on-popover-button-press/2554/7 "2021-11-04T21:00:12Z")
If it is fonts, the issue can be on the user's machine. The font may need replacing. On the other hand, it can be because those objects require a font. That may affect a group of machines if they all share the same system configuration. It can be that the user inputs include styled text. If styled text is not required, it is worth while stripping styles to reduce issues. ---
**Author:** ![JasonMark](https://avatars.discourse-cdn.com/v4/letter/j/a9adbd/32.png) [@JasonMark](https://the.fmsoup.org/u/JasonMark)\ **Post date:** [November 4, 2021, 9:21pm UTC](https://the.fmsoup.org/t/how-to-debug-a-crash-on-popover-button-press/2554/8 "2021-11-04T21:21:58Z")
Oh, definitely not that. I'm running Windows 11 on Parallels and also a Remote Desktop of Windows 10, and they're all on Windows 10 patched by the school district, so unless Windows rolled out a bad font to multiple builds of Windows that's not likely.