I'm currently playing with NativeBoost �(a great thing to have) and pharo consistently crashes after running for a while. My impression is that crashes happen during GCs as if something moves under the installed callback. This may be also related to the libpcap itself, but how can I know for sure. I've tried everything newest (vm+image+libpcap) and I also migrated into a much more rigid scheme of storing and passing callback. Now I've run of ideas where to look further.

So, it is like this. NBPCapHandlerCallback �is a procedure which is called by libpcap for every packet it has in its internal buffer after the application calls pcap_dispatch(). pcap_dispatch receives the callback as a parameter. �I have to repeatedly call pcap_dispatch in so called nonblocking mode (and pass the callback each time) every 5 milliseconds to collect packets - we are single threaded. This amounts to awful whole 200 callback installations per second, may be libpcap was not well tested in this scenario (I suppose pcap_loop runs in separated thread in wireshark and callback installation happens several times per session at most) - hence my doubts. But also - could it be something with NB?

Any hints how to proceed with it are greatly appreciated. This is amazing how one can quickly assemble something that emulates thousands of dhcp-clients (this is what the app does) with current Pharo. �But the thing dies off after 10-15 minutes.