Skip to content

Threads need a wrapper for calling detach() #758

Closed

Description

@akshayaurora

Threads that don't exit cleanly can cause a Java Exception.

There should be a wrapper around threads that automatically detaches the thread before exit, avoiding this kind of error.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Activity

  1. ecdsa commented on Jun 4, 2016

    @ecdsa

    Here is the error I got.
    06-02 16:02:14.198 29619 29655 W art : Native thread exiting without having called DetachCurrentThread (maybe it's going to use a pthread_key_create destructor?): Thread[13,tid=29655,Native,Thread*=0xb984afd8,peer=0x12db40a0,"Thread-11803"]

    Note that the thread did not raise any python exception. As far as python is concerned, the thread exited cleanly.

  2. inclement commented on Jun 8, 2016

    @inclement
    Member

    @akshayaurora I'm not familiar with this, is it something that the old toolchain had but is now missing?

  3. akshayaurora commented on Jun 8, 2016

    @akshayaurora
    MemberAuthor

    No, old toolchain did not have this either.

  4. zwyuan commented on Jun 29, 2016

    @zwyuan

    I ran into the same issue too. Please help resolve this, thanks

  5. suriyan commented on Aug 15, 2016

    @suriyan

    Please look at :- kivy/pyjnius#107

  6. ecdsa commented on Oct 18, 2016

    @ecdsa

    any news on this?

  7. akshayaurora commented on Oct 27, 2016

    @akshayaurora
    MemberAuthor
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions