#1880: Parrot_new should not need to be passed previously-created interps
----------------------+-----------------------------------------------------
Reporter: dukeleto | Owner: whiteknight
Type: RFC | Status: assigned
Priority: normal | Milestone:
Component: none | Version: master
Severity: medium | Keywords:
Lang: | Patch:
Platform: all |
----------------------+-----------------------------------------------------
Changes (by whiteknight):
* status: new => assigned
* platform: => all
* version: 2.10.0 => master
* milestone: 2.11 =>
Comment:
This problem is caused by the current threading system. The threading
system maintains a global array of created interpreter objects, and the
first thread (the only one without a parent interp) is supposed to create
that array. Creating a second interp without a parent enters into the same
logic path, tries to fiddle with the global array in ways that aren't
good, and we get errors.
The threading system is known to be broken in this and in other ways, and
is currently undergoing a redesign. I will keep this ticket open as a
reminder, but I am not certain if we are going to fix the bug as-is or if
we are going to want to punt and avoid it in a hypothetical future system.
--
Ticket URL: <https://trac.parrot.org/parrot/ticket/1880#comment:1>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets
