A fork gives us a brand new process which is a copy of the current process with the same code segment. It looks exactly like the parent process with different process id having it's own memory. Parent process creates a separate address space for the child with same code segments but executes independently of each other. Because the system issues a new memory space and environment for the child process, it is knows as heavy-weight process.
While threads can execute in parallel with same context. Also, memory and other resources are shared between the threads causing less overhead. A thread process is considered a sibling while a forked process is considered a child. Also, threads are known as light-weight processes as they don't have any overhead as compared to processes (as it doesn't issue any separate command for creating completely new virtual address space). A single process can have multiple threads. For all threads of any process, communication between them is direct. While process needs some interprocess communication mechanism to talk to other processes. Thought, threads seem to be more useful for any reason, do note that changes in any thread may lead to changes in other threads of the same process. While, changes in child processes is independent as parent process has its own execution copy.
@ekta yep, weather they share same stack and heap memory is the key point
@WenhuiZhang Can you explain? How exactly are stack and heap memory related to threads and processes?
@mogili : I think what Weinhui meant is threads have their own stack space but different threads of the same process share the heap memory. That is no true for two different processes.
Then which one to be preferred in major aspect, i.e. in terms of memory, time consumption, communication, security, etc. ?
Looks like your connection to LeetCode Discuss was lost, please wait while we try to reconnect.