Skip to content
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

Crashed #292

Closed
Curculigo opened this issue Jul 23, 2024 · 7 comments
Closed

Crashed #292

Curculigo opened this issue Jul 23, 2024 · 7 comments
Assignees
Labels
bug Something isn't working ready for release

Comments

@Curculigo
Copy link

Curculigo commented Jul 23, 2024

I setup a C++ project to build with CMake and Ninja. Also tell CMake to generate compile commands. After completed the build to have my compile_commands.json generated, I clicked into main.cpp and it crashed.

dr.mingw report:

ecode.exe caused an Access Violation at location 0000000000000000 DEP violation at location 0000000000000000.

AddrPC           Params
0000000000000000 000000000000003F 0000006E3F6ED378 0000006E4870F160
00007FFEA45E4E57 FFFFD00000000103 00007FF7F949E000 0000006E3F6ED1F8  eepp.dll!EE::UI::CSS::StyleSheetPropertyAnimation::tweenProperty+0x637
00007FFEA45E8C81 0000006E414D7960 0000006E48E760A0 0000006E414D7960  eepp.dll!EE::UI::CSS::StyleSheetPropertyAnimation::onUpdate+0x211
00007FFEA45EA3C9 0002625A00000000 000F860400001000 0011FDFF00000001  eepp.dll!EE::UI::CSS::StyleSheetPropertyAnimation::update+0xd9
00007FFEA4353964 0000000000000001 000000000000000C 0000000000000000  eepp.dll!EE::Scene::ActionManager::update+0x234
00007FFEA45584BA 00007FFEA44E56D0 00007FFEA437F04B 0000000000000000  eepp.dll!EE::Scene::SceneNode::update+0x2a
00007FFEA477B52C 000000000000000F 00007FFEA4828D4F 000000000000000F  eepp.dll!EE::UI::UISceneNode::update+0x7c
00007FFEA4553833 0000000000004500 00007FFEA4828E60 0000006E4146FBB0  eepp.dll!EE::Scene::SceneManager::update+0x43
00007FF7FA0AF3F2 0000006E4146FBB0 0000006E3F6ED6B0 0000006E3F6ED630  ecode.exe!0x5f3f2
00007FFEA48294B3 0000006E3F6ED610 0000006E47BC9370 0000006E414700E4  eepp.dll!EE::Window::Window::runMainLoop+0xd3
00007FF7FA0C3E25 0000000000000000 0000006E3F6EEFF8 0000006E3F6EDAB0  ecode.exe!0x73e25
00007FF7FA480427 0000000000000001 0000006E414572F0 0000000000000000  ecode.exe!0x430427
00007FF7FA0512EE 0000000000000000 0000000000000000 0000000000000000  ecode.exe!0x12ee
00007FF7FA0513E6 0000000000000000 0000000000000000 0000000000000000  ecode.exe!0x13e6
00007FFECFA913D2 00007FFECFA913B0 0000000000000000 0000000000000000  KERNEL32.DLL!BaseThreadInitThunk+0x22
00007FFED03F03C4 0000000000000000 0000000000000000 0000000000000000  ntdll.dll!RtlUserThreadStart+0x34
@SpartanJ SpartanJ self-assigned this Jul 23, 2024
@SpartanJ SpartanJ added the bug Something isn't working label Jul 23, 2024
@SpartanJ
Copy link
Owner

Thanks for the report. Can you reproduce it intentionally if you try? This one looks odd, it crashed with a CSS animation, I've never seen this.

I setup a C++ project to build with CMake and Ninja.

You configured the project build settings in ecode or you just did a setup from other application? Anyway given that the error is with an animation it should matter.

Thanks

@Curculigo
Copy link
Author

I use the built-in build and run feature to call cmake and ninja (multi-steps). I actually use only the Build button since I don't want F5 = Build and Run. I don't want to run the program because I only need it to run cmake (to generate compile_commands.json). I found that if I switch between the build and run tabs and the files tab too quickly, the problem triggers.

@SpartanJ
Copy link
Owner

I wasn't able to reproduce it yet, I'll keep trying. If possible could you record a video crashing ecode? Thanks

@Curculigo
Copy link
Author

I have encountered this bug again today.

@Curculigo
Copy link
Author

I have a bunch of WARNING: Property "is" is not defined! and WARNING: applyProperty: Property "is" not defined! in ecode.log. They are not particularly useful, at least for me.

@SpartanJ
Copy link
Owner

SpartanJ commented Sep 6, 2024

Don't worry about that. It's just a typo on a property that it's not being used. I fixed a couple of crashes on the Build Settings panel since 0.6.0, this crash is probably related and already fixed but I can't confirm.

The crashes that I fixed were really easy to reproduce and very annoying. I'll to do a minor release in a few days.

SpartanJ added a commit to SpartanJ/eepp that referenced this issue Sep 14, 2024
@SpartanJ
Copy link
Owner

I finally was able to reproduce it. Thankfully Haiku memory allocator is quite different and reproduced the bug quite easily (it's an invalid memory access). But sadly this bug did not get into the 0.6.1, though since it's quite a bad bug I'll re-upload a patched 0.6.1 into the release packages (so if you already downloaded it, please download it again).

@Curculigo Curculigo mentioned this issue Sep 20, 2024
@SpartanJ SpartanJ closed this as completed Nov 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working ready for release
Projects
None yet
Development

No branches or pull requests

2 participants