Status: Started
Owner: [hidden email] Labels: Milestone-1.4 Type-Bug Importance-High New issue 4914 by [hidden email]: #14196 VM crash on #cleanUpForRelease http://code.google.com/p/pharo/issues/detail?id=4914 When I do ScriptLoader new cleanUpForRelease The VM crashes. (needs to be analyzed: with the last VM?, what exactly in the cleanupScript...) _______________________________________________ Pharo-bugtracker mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker |
Comment #1 on issue 4914 by marianopeck: #14196 VM crash on #cleanUpForRelease http://code.google.com/p/pharo/issues/detail?id=4914 can it be related to the cleap of the the DebuggerMap ? _______________________________________________ Pharo-bugtracker mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker |
Updates:
Status: Workneeded Comment #2 on issue 4914 by [hidden email]: #14196 VM crash on #cleanUpForRelease http://code.google.com/p/pharo/issues/detail?id=4914 (No comment was entered for this change.) _______________________________________________ Pharo-bugtracker mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker |
Updates:
Status: FixToInclude Comment #3 on issue 4914 by [hidden email]: #14196 VM crash on #cleanUpForRelease http://code.google.com/p/pharo/issues/detail?id=4914 fix attached. We need the becomeForward: in rehash of MethodDictionary Attachments: MethodDictionary-rehash.st 431 bytes _______________________________________________ Pharo-bugtracker mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker |
Comment #4 on issue 4914 by marianopeck: #14196 VM crash on #cleanUpForRelease http://code.google.com/p/pharo/issues/detail?id=4914 No. Wait. That was changed on purpose. Let me see. _______________________________________________ Pharo-bugtracker mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker |
Comment #5 on issue 4914 by marianopeck: #14196 VM crash on #cleanUpForRelease http://code.google.com/p/pharo/issues/detail?id=4914 Why do you think we need the becomeForward? Why rehash | newInstance | newInstance := self species newForCapacity: self basicSize. 1 to: self basicSize do: [ :index | (self basicAt: index) ifNotNil: [ :key | newInstance at: key put: (array at: index) ] ]. self copyFrom: newInstance is incorrect? _______________________________________________ Pharo-bugtracker mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker |
Comment #6 on issue 4914 by [hidden email]: #14196 VM crash on #cleanUpForRelease http://code.google.com/p/pharo/issues/detail?id=4914 because it crashes the VM _______________________________________________ Pharo-bugtracker mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker |
Updates:
Status: Integrated Comment #7 on issue 4914 by [hidden email]: #14196 VM crash on #cleanUpForRelease http://code.google.com/p/pharo/issues/detail?id=4914 (No comment was entered for this change.) _______________________________________________ Pharo-bugtracker mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker |
Comment #8 on issue 4914 by marianopeck: #14196 VM crash on #cleanUpForRelease http://code.google.com/p/pharo/issues/detail?id=4914 MethodDictionary rehashAllInstances works like a charm, so I am not sure the crash is related to that. _______________________________________________ Pharo-bugtracker mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker |
Comment #9 on issue 4914 by [hidden email]: #14196 VM crash on #cleanUpForRelease http://code.google.com/p/pharo/issues/detail?id=4914 But ScriptLoader new cleanUpForRelease crashes the VM with that change and does not crash without. _______________________________________________ Pharo-bugtracker mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker |
Comment #10 on issue 4914 by marianopeck: #14196 VM crash on #cleanUpForRelease http://code.google.com/p/pharo/issues/detail?id=4914 With the latest VM of Eliot (which is the one I use) it doesn't crash either with or without the become. In both cases I have the same problem, which is the one I have reported in: http://code.google.com/p/pharo/issues/detail?id=5005 _______________________________________________ Pharo-bugtracker mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker |
Comment #11 on issue 4914 by [hidden email]: #14196 VM crash on #cleanUpForRelease http://code.google.com/p/pharo/issues/detail?id=4914 ok, so as soon as the VM is the one I can download from Jenkins, we can put the method back. _______________________________________________ Pharo-bugtracker mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker |
Free forum by Nabble | Edit this page |