python deepcopy segmentation fault on version 4.24.0

[criver]

What version of protobuf and what language are you using? Version: main/v3.6.0/v3.5.0 etc. (NOTE: please try updating to the latest version of protoc/runtime possible beforehand to attempt to resolve your problem) Language: C++/Java/Python/C#/Ruby/PHP/Objective-C/Javascript

What operating system (Linux, Windows, ...) and version? Ubuntu 22, OSX14.5, It happens for probouf 24.0 and above

What runtime / compiler are you using (e.g., python version or gcc version) Clang 15, gcc

What did you do? This error is similar to https://github.com/protocolbuffers/protobuf/issues/13485 but it happens for deepcopy instead. @anandolee

message Child {
  string name = 1;
}
message Parent {
  Child child = 1;
}

p = Parent()
deepcopy(p.child)

What did you expect to see Expect it to run without error.

What did you see instead?

Fatal Python error: Segmentation fault

Make sure you include information that can help us debug (full error message, exception listing, stack trace, logs).

Anything else we should know about your project / environment

[zhangskz]

Can you confirm if you hit this even with latest 4.27.x release?

[criver]

There is no 4.27.x, only 5.27.x. I can't upgrade to 5 because other dependencies in my project.

[anandolee]

I believe it is the same issue with https://github.com/protocolbuffers/protobuf/issues/13485 which only happen for 4.24.

4.23 and below, 4.25 and above should work well

[criver]

4.24 and 4.25 are broken. 4.23 works.

On Fri, Jun 14, 2024, 6:26 PM Jie Luo @.***> wrote:

I believe it is the same issue with #13485 https://github.com/protocolbuffers/protobuf/issues/13485 which only happen for 4.24.

4.23 and below, 4.25 and above should work well

— Reply to this email directly, view it on GitHub https://github.com/protocolbuffers/protobuf/issues/17081#issuecomment-2169024448, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADDXFUG5ZWTYGCQ2VBUFDOLZHOJ6FAVCNFSM6AAAAABJAJGTGOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNRZGAZDINBUHA . You are receiving this because you authored the thread.Message ID: @.***>

[criver]

@anandolee What is the plan for fixing this?